As you may already know, Windows Azure SQL Database doesn’t support the full range of features available in SQL Server 2012. Using the Microsoft SQL Server Data Tools will help you identify issues early by validating your schema against the target platform. The tools will provide IntelliSense and make it possible to manage database versions by storing scripts in TFS. Furthermore, they simplify deployments by comparing the new schema against the destination database in order to generate an update script.
From personal experience, using the Microsoft SQL Server Data Tools makes it possible for teams to collaborate on databases. By splitting objects like tables, views and stored procedures into their own files, it makes it possible to maintain and evolve the database as we progress in the application’s elaboration.
That being said, I urge you to get acquainted with the Microsoft SQL Server Data Tools using the links found below. Make a difference on your projects by using the right tools!
Developers will also appreciate the familiar VS tools we bring to database development, specifically; code navigation, IntelliSense, language support that parallels what is available for C# and VB, platform-specific validation, debugging and declarative editing in the TSQL Editor, as well as a visual Table Designer for both database projects and online database instances.
What’s new? This feature release of the Data-Tier Application Framework (DACFx) brings with it a significant payload of both new functionality as well as 100+ bug fixes since the last release. The features included in this update center around a new
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
The SSDT – June 2013 update contains several improvements:
- Data Compare
- Build and Deployment Contributors
- Extensibility API
- Updated Data-Tier Application Framework (DACFx)
This release is available for both Visual Studio 2012 and Visual Studio 2010