Home Dashboard Directory Help
Search

Visual Studio 11 - Data Comparison Feature Missing by AMDeveloper


Status: 

Closed
 as Duplicate Help for as Duplicate


54
0
Sign in
to vote
Type: Bug
ID: 729093
Opened: 3/6/2012 7:04:30 AM
Access Restriction: Public
Moderator Decision: Sent to Engineering Team for consideration
0
Workaround(s)
view
17
User(s) can reproduce this bug

Description

In Visual Studio 2010 "Schema Compare" and "Data Compare" features are available to compare schema and data between two databases. However in Visual Studio 11 only "Schema Compare" feature is available. "Data Compare" feature is missing.
Details
Sign in to post a comment.
Posted by Microsoft on 2/11/2013 at 12:29 PM
This was closed as a duplicate since the team has an active work item tracking the delivery of Data Compare- I apologize for the error in the Resolved Reason. I've updated it to reflect that this issue is a duplicate, not yet fixed.

Thanks,
Janet Yeilding
Posted by Korn1699 on 2/11/2013 at 6:29 AM
How is this "Closed as Fixed" when it has been 11 months since the official reply from Microsoft and there is STILL no data compare support for SQL Server 2012? We frequently use this feature and are being held back from upgrading right now because it still isn't there for 2012.
Posted by John Sun on 1/11/2013 at 9:29 PM
Does this tool available now?
Posted by Coach David on 11/14/2012 at 9:53 AM
What is the status of this issue?
Posted by Janet Yeilding on 5/21/2012 at 9:19 AM
You're correct that there is no workaround for SQL Server 2012 Data Compare, sorry for the inconvenience. As I said before, this feature is coming soon to SSDT.

Thanks,
Janet Yeilding
Posted by jeroen on 5/21/2012 at 2:42 AM
The suggested workaround does not work with SQL server 2012.
Posted by Microsoft on 3/13/2012 at 5:44 PM
SQL Server Data Tools (SSDT) is replacing the VSDB database tools in Visual Studio 11. SSDT has implemented a Schema Compare tool, which it looks like you've already discovered. We haven't yet created a Data Compare tool but it's in our plans for the near future. In the meantime, the workaround is the use the VSDB tools in the VS 2010 shell.

Please let me know if you have any follow up questions.
Thanks,
Janet Yeilding janety@microsoft.com
Posted by MS-Moderator07 [Feedback Moderator] on 3/6/2012 at 8:41 PM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue
Posted by MS-Moderator01 on 3/6/2012 at 5:54 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.