Offical team blog for SSDT, a tool for on and off-premise database development
SSDT for Visual Studio 2012: http://msdn.microsoft.com/en-us/jj650015
SSDT for Visual Studio 2010: http://msdn.microsoft.com/en-us/jj650014
We have received an overwhelming amount of feedback that database unit testing is a critical feature for customers, so SSDT- December 2012 adds support for this feature. Database Unit Testing in SSDT will look familiar to many of you as it is based on the equivalent capability in the Visual Studio 2010 DB Pro tools. Some highlights:
Stay tuned for a follow-up post on getting started with SQL Server database unit testing.
The SSDT team started releasing SSDT Power Tools last April as a mechanism to deliver new and experimental features with each release. Since then, the Power Tools have been downloaded over 24,500 times.
We received a great deal of positive feedback on the Power Tools and as a response, this release integrates the functionality previously delivered via Power Tools into the core SSDT product. The advantage of product inclusion is that a separate install will no longer be needed and that features are now fully supported and available to users in all languages. The following features are now included in SSDT's SQL Server Object Explorer:
Projects node adds the equivalent of Schema View to SSDT. You can use this node to browse the logical schema of your project and to edit, refactor, and add new objects.
Script As support in SSOX enables you to generate Create, Alter, Drop, and Drop and Create-To scripts for objects in your connected database.
DAC actions allow you to perform similar DAC-based tasks in SSDT to those available in SSMS. You can extract a dacpac from a live database, publish a dacpac to a database, register a database as a DAC, or remove the registration metadata for a database registered as a DAC. These actions are supported for both on-premises SQL Server databases as well as Windows Azure SQL Databases.
We recommend that you uninstall the SSDT Power Tools extension if you had it previously installed.
This release includes the November 2012 release of SQL Server Data-Tier Application Framework (DACFx), which contains several feature enhancements and bug fixes. You can learn more about the latest release of DACFx here.
SSDT - December 2012 contains over 50 bug fixes, including fixes for customer-reported issues from SSDT - November 2012 and SSDT Power Tools releases.
If you have any questions or feedback about SSDT, please visit our forum or Microsoft Connect page. We look forward to hearing from you.
SSDT Projects Fail to Build in Parallel. There are two errors: Store must be open for this operation or Version store out of memory.
Where is the real download? I don't want something that is going to slowly download something else while I'm forced to wait on it. I want a download I can download while connected to high speed internet, then install on both of my machines once I have the whole thing downloaded.
Do you plan to include BI project templates for VS2012 in the next release?
SSDT for Visual Studio 2012 doesn't work anymore after applying SQL Server 2012 SP1.
Is there a roadmap on when the Data Compare feature might be released?
I had to send this email to my boss:
>>The tools with Visual Studio do a fairly good job of the Schema compare. ...
>>The Visual Studio tools are reported to not work with SQL Server 2012 and there is no plan to release an update.
Why do you do upgrades that down grade the product?
Hi, I want to know how to use the sql server 2012 data base in visual studio 2010, please guide me through the procedure
I installed sql server data tools but not seen in VS 2012 Premium 2012 - project type Sql server data tools.. Is anything missing ?
I have installed SSDT for VS2012 -successfully but not shown in VS 2012 project list. Only Sql server DB project seen as like previous to installation. Any ideas?
What happened to the Schema view mode that the Project node was supposed to contain? We're being forced to move to VS 2012, and without this functionality the use of schemas very difficult.
I'm receiving Error# 40 : Network specific or instance specific error due to which not able to connect to the SQL server...How to resolve this ?.
I don't get why I have to install Visual Studio and these Visual Studio tools to import an Azure .bacpac foile into my local SQL Server 2012 instance.
It is supposed to be a SQL server environnment. Not a devl environment.
Where is the logic ?