Offical team blog for SSDT, a tool for on and off-premise database development
The SSDT team is pleased to announce that SQL Server Data Tools - August 2013 update is now available for download.
SSDT for Visual Studio 2012: http://msdn.microsoft.com/en-us/jj650015
SSDT for Visual Studio 2010: http://msdn.microsoft.com/en-us/jj650014
SSDT - August 2013 includes a new redist of SQL Server Data-Tier Application Framework (DACFx), which contains several new bug fixes to customer-reported issues:
· Upgrade with dacpac fails when it tries to drop system partitions
· Public Model has no mapping for ScalarFunction and TableValuedFunction "Type" relationship
· Error building Database project with UDF aggregate
The DACFx standalone install is available here: http://www.microsoft.com/en-us/download/details.aspx?id=39976
This release includes many bug fixes for issues reported by customers using SSDT. Here are some of the most impactful bugs that this release addresses:
· Static Code Analysis Task doesn't honor the CmdLineInMemoryStorage property
· StackOverflowException and crash when programmatically opening a .SQL file
· "Warning as error" setting in code analysis overrides build settings
· Deployment messages not tracked during Publish operation
If you have any questions or feedback, please visit our forum or Microsoft Connect page. We look forward to hearing from you.
Is there a full changelog somewhere?
Great news ... at this point, can I recommend that your team review the Data Developer Center's SQL Server Data Tools pages ... here:
The "Learn" is outdated now that you've added a lot of features back that were missing from "data dude" upon its first release.
Take a look at this FAQ:
There's some mis-information there now because, for example, Unit Testing **IS** in the product as of December 2012. Just trying to learn it all and fight through the versioning.
All links on the msdn.microsoft.com/.../jj650015 page return 404 errors - great work MS (as always).
@Mladen here is the changelog:
DacFx fixed defects:
Script to get version/edition fails against SQL 2005 RTM
Script execution error at Data Deploy against SQL 2005
Error building Database project with UDF aggregate
Number of trusted/disabled foreign keys before and after extract/publish round-trip are different
New validation error 71566 blocks setting filegroup on table and PK even when technically valid
LightSwitch: Default constraint not dropped when dropping column in composite project
Upgrade with dacpac fails when it tries to drop system partitions
Public Model has no mapping for ScalarFunction and TableValuedFunction "Type" relationship
"Compare using target collation" doesn't respect server's collation
SqlPackage and DacServices API do not update body of encrypted procedures (on incremental deployment)
SSDT fixed defects:
Not running public deployment plan executors when Publishing in VS
When Publishing messages created by public DeploymentPlanModifiers not shown to the user
StackOverflowException in Microsoft.VisualStudio.Data.Tools.SqlEditor when opening a .SQL file and a CodeFluent Entities type
SSDT Generated Script fails to connect to server if DB doesn't exist
Transact-SQL and code analysis "warning as error" are not managed separately
Cancellation might cause AzureDB forcibly close the existing connection if the data size is large
SqlStaticAnalysisTask does not honor the CmdLineInMemoryStorage property
@Bob Thanks for the heads up about the outdated info, I've just updated the FAQ page.
@Molly The links are working for me. Perhaps this was an intermittent issue? Are you still experiencing this problem?
I too struggle to find where the release notes / changelog are for SSDT releases, may I suggest this information gets linked to on the download page... very frustrating crawling the web to find out if it's worth updating or not.
My faith in SSDT was quite high initially back in VS2010, was lost when data compare was removed from 2012. I'm still waiting for the day when static data is included as part of an SSDT project, similar to the RedGate source control tooling, instead of having to manually maintain MERGE scripts and the post deploy script.
The SSDT defect "Transact-SQL and code analysis "warning as error" are not managed separately" is not fixed.
On my VS2012 Update3 and SSDT August 2013, I have all code analysis warnings which are displayed as errors.
is SSDT part of 2013 or still a separate download? If separate when will that be available or can I just use the 2012 version?
When can we expect to have SQL Server BI Projects (SSIS, SSAS, SSRS) support in VS2013?
This update fails to install and sends in return a Error Log. It won't play ball even by booting in Safe Mode (just in case an started service is making the update fail. I cleaned-up the registry and the Temp folders, and still it fails to install. The curious thing is that the update takes a rather long time (a couple of minutes) without doing anything (no progress bar) just to crash without advancing past 0% progress. Please help.
@Alejando please post the error log on the team forum (social.msdn.microsoft.com/.../threads) and we'll take a look
@Alejando - it looks like the DacFx ETW manifest didn't install on your machine for some reason. The error message recommends uninstalling the old one. Could you run the command below and reinstall SSDT?
wevtutil.exe um "%VSINSTALLDIR%\Common7\IDE\Extensions\Microsoft\SQLDB\Microsoft.Data.Tools.Utilities.EtwResource.man"
Has anybody experienced issues with foreign key constraints becoming untrusted after deploying a dacpac built using SSDT (versions between June-August 2013) using sqlpackage.exe? I'm using the query provided by brent ozar to detect untrusted keys (www.brentozar.com/.../foreign-key-trusted) and then fixing it after deployment. Is there something I should be looking for in the foreign key declarations within the table definition? As far as I can tell, the foreign keys are defined on the tables in canonical form. Thanks.