Offical team blog for SSDT, a tool for on and off-premise database development
We are pleased to announce that SQL Server Data Tools - June 2013 is now available for download. This release introduces several new features that we have consistently received requests for via MSDN forums and Connect. From the SSDT team, thank you for your valuable feedback and suggestions!
We received significant feedback that Data Compare is a critical feature for SSDT customers, so this release of SSDT enables the visual data comparison between a customizable list of tables/views in two databases. From this comparison, a script to update the table data in the target database can be generated. This is a new addition to SQL Server Data Tools and brings with it support for all SQL Server platforms supported by SSDT including SQL Server 2012 and Windows Azure SQL Database.
Entry point for Data Comparison from SQL Server Object Explorer
Data Comparison showing two different records in Source and Target
This release brings with it a significant payload of updates and additions to the extensibility scenarios supported in SSDT and DACFx.
This extensibility point allows hooking custom code up to the existing DACFx build or deployment pipeline. Similar to previous database project extensibility, this enables advanced build and deployment scenarios like auto-generating documentation, custom difference reports, or injecting custom data motion logic into the deployment plan. The three supported contributor types are:
· Build Contributors - Extension that runs when the database project is being built and allows read-only access to the schema model and all properties and arguments of the build task
· Deployment Plan Modifier – Extension that runs after the deployment plan has been generated allowing read/write access to the deployment plan, and read-only access to the model comparison results, and source/target schema models
· Deployment Plan Executor - Extension that runs during deployment allowing read-only access to the deployment plan
New Build Action in SSDT projects for deployment contributors
Another addition to this release is the exposure of an API allowing navigation of the schema model contained in a DACPAC or BACPAC. This API allows you to reason over the objects and relationships contained in the schema model generated by DACFx. In addition, this allows you to implement custom solutions on top of DAC package navigation like synchronization with a data access model, writing custom schema navigation and browsing tools, and perform additional schema validation.
Documentation of the key DACFx API namespaces involved in extensibility scenarios can be found on MSDN here. Additionally, walkthrough samples for the creation of build and deployment contributors can be found in the SSDT documentation here.
This release includes the June 2013 release of SQL Server Data-Tier Application Framework (DACFx), which contains several feature enhancements and bug fixes.
Visual Studio data tooling
Database Unit Testing was included in SSDT December 2012. With SSDT June 2013, Data Comparison was added along with several key extensibility scenarios. However, Data Generation is not included and is not planned to be released in the future. Third party tooling will have to be relied upon for that functionality.
SQL Server 2014 CTP1
Only SQL Server Management Studio that ships with SQL Server 2014 CTP1 should be used with SQL Server 2014 CTP1. No version of Visual Studio, SQL Server Data Tools, or Data-Tier Application Framework provides support for SQL Server 2014 CTP1. We will continue to invest in SQL Server Data Tools (SSDT) and Data-Tier Application Framework (DACFx) and the tooling will be updated to support future SQL Server and Windows Azure SQL Database releases.
SQL Server 2014 CTP1 - http://www.microsoft.com/en-us/sqlserver/sql-server-2014.aspx
Please provide your feedback and ask us questions on our forum or via Microsoft Connect. We look forward to hearing from you.
There's some interesting sounding stuff here. Is there any additional documentation available regarding the Deployment Plan Modifier? I'd like to know how and where to implement these things as I'm hoping they are a solution to many of the limitations of DAC deployments.
Fantastic! We've been anxiously awaiting the Data Compare tool. This should be super helpful in keeping all the workflow within Visual Studio.
Very Cool! The team is really pushing out updates quick! SSDT really helps me out a lot and is a great product. Thanks so much.
I just downloaded the new June 2013 update and noticed a couple new Build Actions on .sql files: "Build Extension Configuration" and "Deployment Extension Configuration"- what do these do?
Previously, I was having problems with SQL71502 errors on a stored procedure that referenced a linked server via a merge statement. The SQL71502 error prevented the projected from building, and removing the .sql file from the build prevented the schema compare tool from seeing that the file was already in the project. This was a problem that I could get around but was pretty annoying. NOW, with the new update, it changed the SQL71502 error to a warning so my project builds and the schema compare works too. Thanks a million!
Any Data Generation announcements here or plans for that in the near future or releases?
Visual studio, SSDt check for updates does not present the June 2013 release as an available update.
The DACFx direct download links go.microsoft.com/fwlink and go.microsoft.com/fwlink seems to still point to the Mar 2013 update.
@dirq - thanks for the positive feedback and we're happy about the value you're getting from SQL Server!
@Hassan - we've updated the blog post to be more clear about Data Generation, which is not included in the current or any future release. Bummer!
@Srinivasn Raju - we'll update our "check for updates" pipeline in the next few days to prompt existing users.
thanks - Erick
I'm happy this is finally here. I'll use the connect feature to request that the data compare add the "Use [database]" in the script it generates because I had a "DOH" moment when first trying to use the script and forgetting to change to the database after making the connection.
Thanks again as this was holding up the Visual Studio 2012 deployment.
Does anyone have an example of how to set up and use Deployment contributors along with the new Deployment Extension Configuration Build Action that has been mentioned above.
I tried going through this walk through msdn.microsoft.com/.../ee461507(v=vs.100).aspx but it does not work, when I run MSBuild on the VS2012 database .sqlproj file - it looks like the contributor is not running.
Any help on how to use new ' Deployment Extension Configuration' Build Action would be appreciated.
I am trying to install SSDT-BI for VS 2012 but it gets to the "Installation Configuration Rules" page and then fails the "Same architecture installation" test. When I click the link for more information, the dialog box says, "The CPU architecture of installing feature(s) is different than the instance specified. To continue, add features to this instance with the same architecture." The instance I am trying to install it to is SQL Server 2012 Developer Edition. Is there anything special I have to do?
I think I figured out the solution to my comment above -- when the installer prompts you to select "shared installation" vs "database instance-specific installation" make sure you select the shared installation option. Then it is able to continue the installation.
What third party tooling is recommended for data generation plans? Data Generation is not included and is not planned to be released in the future. Third party tooling will have to be relied upon for that functionality.
Very well done. SSDT is a fantastic tool bringing me huge value, and I am loving it since the first release! And now I cannot even think about my development experience without it...
Please keep up with this outstanding work an continue updating it: this update and hearing you will continue with this project makes me very happy.
I am also very interested in SSDT extensibility: could you point me to some docs about it?
Thank you very much
I can't install this update. Does anyone have any ideas? There's an error on installation: "Element not found". Looking at the log file shows these lines:
[169C:1688][2013-06-28T11:08:29]: Error 0x80070490: Failed to verify expected payload certificate with any certificate in the actual certificate chain.
[169C:1688][2013-06-28T11:08:29]: Error 0x80070490: Failed to verify signature of payload: DACFX11X86
[169C:1688][2013-06-28T11:08:29]: Failed to verify payload: DACFX11X86 at path: C:\ProgramData\Package Cache\.unverified\DACFX11X86, error: 0x80070490. Deleting file.
[169C:1688][2013-06-28T11:08:29]: Error 0x80070490: Failed to cache payload: DACFX11X86
Guys, you tire me with your idea that on-line installers rules the world. You made that thing for Visual Studio Updates, and now you made it for SSDT updates. Sadly.
SSDT December 2012 was distributed as ISO. VS Update 2 & 3 are available as ISO. Why don't you release SSDT June 2013 as ISO?
And don't suggest me using sluggish "SSDTSetup.exe /layout <destination>". Because SSDTSetup.exe requires Windows Vista (when I run it on Windows XP I've got an error... something like "entry point to FlsFree not found in kernel32.dll"; FlsFree is available on Vista and above).
My working PC has Windows 7 SP1 but it DOESN'T have Internet access. The only PC with Internet access I have is Windows XP PC. Where I CAN'T run your "downloader"! So tell me: why don't you share ISO or something like this so one can download that WITHOUT requiring for Windows Vista! Why I can't _download_ something from OS other than you dictate? Downloading an update on "PC 1" doesn't mean, dear MSFT, that I intend to install it there!
Yes, SSDT is great tool! I agree with comments above. But to distribute it in the way MSFT does -- is real bad idea. Sorry, but I'm fed up with you!