SQL Server Data Tools Team Blog

SQL Server Data-Tier Application Framework (May 2013) Available

Adam Mahood [MSFT] — Fri, 03 May 2013 14:37:00 GMT

What’s new?

This update to the Data-Tier Application Framework (DACFx) addresses a high-priority issue causing potential data corruption during DAC Package creation. The issue is described below:

Scenario/Issue

Extracting a DACPAC with data or Exporting a BACPAC from a database containing tables that have VARBINARY columns with data larger than or equal to 4,116,480 bytes may experience data corruption in the resulting package.
The resulting DAC package may have different data than that in the original source database.

Symptom

Deploying a DACPAC or Importing a BACPAC created from a database matching the above characteristics may result in the table data in the target database being different from that in the original source.

Resolution

Install the updated release of DACFx available here to fix this issue.
Once the new version is installed, re-create the DAC packages for the databases that may have experienced this issue.

How can I get it?

You can obtain this new version of DACFx and its dependencies from our Microsoft Download Center page here. This version of DACFx supersedes all previously available versions. This new version of DACFx supports in-place upgrade from previous versions, so it is not required to remove previous DACFx installations before upgrading to this new release.

If you are on an x64 machine, you will need to install both the x64 and x86 versions of the MSIs from the DACFx May download page linked above.

The version of this update is 11.1.2825.1. This supersedes the previously available March release (11.1.2824.1). You can determine which version of the Data-Tier Application Framework you currently have installed via Windows Add/Remove Programs.

Compatibility

This release of DACFx is fully compatible with the December 2012 release of SQL Server Data Tools released on 12/13, available here. This release is also compatible with SSMS of SQL Server 2012 and SQL Server 2012 SP1.

If you experience any issues or have any feedback, please let us know via the forum or Connect.

SQL Server Data-Tier Application Framework (March 2013) Available

Adam Mahood [MSFT] — Wed, 06 Mar 2013 19:13:01 GMT

What’s new?

This update to the Data-Tier Application Framework (DACFx) addresses several high-priority issues reported by DACFx and SQL Server Data Tools customers via the forum and Connect. The issues addressed include:

Database Project in Visual Studio hangs on “Analyzing Database Schema…”

This release addresses an issue that can occur when loading or building large Database Projects. In some cases, the operation would never finish.
This is a functional fix, not a performance enhancement - even with the fix, the time to complete this operation depends on the size and complexity of your project.

“System.ObjectDisposedException: Store must be open for this operation” failure in DACFx

This release addresses an issue that can occur when simultaneously working over multiple Database Projects or DACFx operations. In some case, an error would be encountered and the operation would not complete.

“Unexpected failure occurred: hexadecimal value 0xxx, is an invalid character” failure in DACFx

This update addresses an issue that can cause the above failure on Export BACPAC and Extract DACPAC operations for certain databases.

The team thanks you for your feedback in reporting these issues!

How can I get it?

If you are on an x64 machine, you will need to install both the x64 and x86 versions of the MSIs from the DACFx March download page linked above.

The version of this update is 11.1.2824.1. This supersedes the previously available November release (11.1.2820.0). You can determine which version of the Data-Tier Application Framework you currently have installed via Windows Add/Remove Programs.

Compatibility

If you experience any issues or have any feedback, please let us know via the forum or Connect.

SQL Server Unit Testing using Visual Studio 2010 and Visual Studio 2012 Side by Side

Bill Gibson MSFT — Thu, 03 Jan 2013 19:52:00 GMT

This post is important only if you need to open the same SQL Server unit test projects in both Visual Studio 2010 and Visual Studio 2012.

The SQL Server unit testing runtime components installed with SQL Server Data Tools (SSDT) are specific to Visual Studio 2010 and Visual Studio 2012. When working with only one version of Visual Studio the appropriate version of the runtime components is installed and there is no issue, but some care is needed when Visual Studio 2010 and Visual Studio 2012 are used side-by-side on the same project. Side-by-side use includes the following scenarios:

Using Visual Studio 2010 and Visual Studio 2012 on the same machine with SSDT installed in both.
Developers on a team who are collaborating on the same SQL Server unit test project but using different versions of Visual Studio.
Building test projects on a build machine that is at a different version level than Visual Studio, for example, using Team Foundation Build 2010 to build projects that were worked on by Visual Studio 2012 or vice versa.

Side-by-side use affects the following:

The app.config file in the test projects.
The database unit testing runtime which is Visual Studio version specific.
Custom test conditions, which extend the runtime above.

The impact on each is discussed further below.

Note: If you modify or extend your test code other than by using custom test conditions, you will need to consider the side-by-side implications of your extension if the test project will be used in both versions of Visual Studio.

SQL Server Test Configuration

To accommodate working with both Visual Studio 2010 and Visual Studio 2012, the app.config file in a test project supports two parallel sections, one for each version. The config sections are created and managed by the same SQL Server Test Configuration dialog in the two respective versions of Visual Studio (the dialog from Visual Studio 2010 is shown below). Example configuration sections are included at the end of this post.

When working in Visual Studio 2010 you should create and edit the configuration using the dialog from that version. If you open the same project in Visual Studio 2012 you should use the Visual Studio 2012 version of the dialog to ensure it is configured appropriately. The dialog can be opened by right-clicking on the test project in Solution explorer or from the SQL menu when the project is selected. The contents of the two sections are not synchronized automatically, so if you are using different Visual Studio versions you should ensure that both sets of configurations refer to the same project and database or your test results may differ when running the same tests from each version of Visual Studio.

SQL Server Database Unit Testing Runtimes

In addition to the MS Test infrastructure, which is installed with Visual Studio Professional and higher editions and with the Team Foundation Build service, the Server SQL Server database unit testing runtime must be installed on any computer on which SQL Server unit tests are to be developed, built or run. This runtime is included in the SSDT Build Utilities which are installed with SSDT. SSDT can be installed on Visual Studio 2010 and Visual 2012 side by side on the same computer allowing SQL Server unit tests to be developed, built and run from either version of Visual Studio.

If you need to build and run the tests on a computer that does not have Visual Studio and SSDT installed – for example, on a Team Foundation Build server – then you will need to install the SSDT Build Utilities manually. SSDT Build Utilities are installed using the SsdtBuildUtilities.msi file, which is provided as part of a version-specific administrative installation of SSDT. If you are using Team Foundation Build 2010 you should install the SSDT Build Utilities for Visual Studio 2010; if you are using Team Foundation Build 2012 you should install SSDT Build Utilities for Visual Studio 2012. The SsdtBuildUtilties.msi should be installed from the location (/location) used for the administrative installation point. Once installed, the app.config configuration section for the appropriate version Team Foundation Build version will be used, so ensure this has been created and is accurate. For more information on setting up a build server see, How to: Run SQL Server Unit Tests from Team Foundation Build. For more information on creating an administrative install point of SSDT, see, Install SQL Server Data Tools.

At build time, the $(VisualStudioVersion) MSBuild property is used to resolve the correct version of the SQL Server database unit testing runtime. When working in Visual Studio 2010, this property is automatically set to 10.0, while in Visual Studio 2012, it is set to 11.0. If you are building from the command line on a machine that has both VS 2010 and VS 2012, then you can explicitly set this property via the command line when you build the project. For example, for a Visual Studio 2012 project, you can run ‘msbuild.exe /p: VisualStudioVersion=11.0 <projectfile>’.

Using Custom Test Conditions in Side-by-Side Scenarios

If you are using a custom test condition in your test project then you must ensure that you either include the test condition source code in your solution that is shared between Visual Studio versions and build it with your test, or install the custom test condition assembly that was compiled with the version of Visual Studio that is being used to develop and run the tests.

If you plan to install the test condition assembly, then the following rules apply.

If you are running Visual Studio 2010 and Visual Studio 2012 side by side on a computer you will need to install both 2010 and 2012 versions of the test condition assembly. The test conditions should be installed in parallel version-specific folders as follows:

Visual Studio 2010:

C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\Extensions\Microsoft\SQLDB\TestConditions

Visual Studio 2012:

C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\Extensions\Microsoft\SQLDB\TestConditions

These locations are configurable by registry key if required.

Note: References to installed custom test condition assemblies are added to your test project during the test development process when you first add a SQL Server unit test to the project, regardless of whether you use any custom conditions in your tests.

If you have a build server that needs to build and run tests that use custom test conditions, then you must manually install the custom test condition assemblies on the server into the appropriate folder based on the server version. You only need to install one version of the test condition assembly, regardless of the Visual Studio version in which the projects are developed.

Again, at build time, Team Foundation Build will use the $(VisualStudioVersion) MSBuild property, if it has been defined, to determine the version-specific folder from which to load the test conditions. If this property is not set on your build server then install only the Visual Studio 2010 versions of any custom test conditions being used in the Visual Studio 2010 folder described above.

Appendix

Example Side-by-Side app.config Configuration Sections

Visual Studio 2010:

Visual Studio 2012:

Available Today: SSDT—December 2012

Janet Yeilding — Thu, 13 Dec 2012 17:00:00 GMT

The SSDT team is pleased to announce that SQL Server Data Tools - December 2012 is now available for download!

Get it here:

SSDT for Visual Studio 2012: http://msdn.microsoft.com/en-us/jj650015

SSDT for Visual Studio 2010: http://msdn.microsoft.com/en-us/jj650014

What’s New?

Database Unit Testing

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:

Installs in Visual Studio 2010 or Visual Studio 2012:
- Requires Visual Studio Professional or higher edition to support database unit testing functionality.
- Installs side-by-side with existing Visual Studio 2010 DB Pro tools in Visual Studio Premium and Ultimate editions.
Supports client-side testing based on MSTest with the same built-in test conditions as DB Pro.
Allows desktop development and execution of tests as well as execution from the command line or as part of a build on a build server.
Upgrades existing VS 2010 test projects without change to the database unit test scripts or code.
Integrates with SSDT SQL Server database projects:

Automates deployment of the database project on test initialization.
Generates skeleton test scripts for stored procedures, functions and triggers via SQL Server Object Explorer.
Applies changes to test scripts when refactoring objects in database projects.

Supports custom test conditions (existing custom test conditions need to be modified before they can be used).

Stay tuned for a follow-up post on getting started with SQL Server database unit testing.

Integration of SSDT Power Tools

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.

Updated Data-Tier Application Framework

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.

Bug fixes

SSDT - December 2012 contains over 50 bug fixes, including fixes for customer-reported issues from SSDT - November 2012 and SSDT Power Tools releases.

Contact Us

If you have any questions or feedback about SSDT, please visit our forum or Microsoft Connect page. We look forward to hearing from you.

Windows Azure Import/Export Service and External References

Adam Mahood [MSFT] — Thu, 13 Dec 2012 16:47:00 GMT

The Windows Azure Import/Export Service powered by the SQL Server 2012 Data-Tier Application Framework (DACFx V3) provides a cloud service for logical backup/restore and migration of Windows Azure SQL Databases. This functionality is available via an HTTP endpoint, as well as through the Windows Azure Management Portal.

We have recently released an update to the service that brings an enhancement to the level of validation carried out against a database during the Export operation. This improved level of validation ensures Exported BACPACs can be Imported (restored) to a new database in Azure. However, due to this improved validation, folks may see an increase in Export operation failures, particularly around invalid self-referencing external (three-part) names in object definitions. More details on the issue are below.

Scenario:

You attempt to Export a Windows Azure SQL Database using the Import/Export Service via the HTTP Endpoint, or through the Windows Azure Management Portal.

Symptom:

Export operation fails with error message similar to the following:

“Exception Microsoft.SqlServer.Management.Dac.Services.ServiceException: Error encountered during the service operation. Inner exception Microsoft.SqlServer.Dac.DacServicesException: Validation of the schema model for data package failed. Error SQL71562: Procedure: [dbo].[SampleProcedure] has an unresolved reference to object [MyDB].[dbo].[TestTable]. External references are not supported when creating a package from this platform.”

Issues:

1. Improved validation blocks Exports of databases containing fully qualified three-part names in object definitions.

Why:

DACFx must block Export when object definitions (views, procedures, etc.) contain external references, as Azure SQL Database does not allow cross-database external references. This includes blocking Export for databases with three-part references to themselves - if these references were successfully Exported, Importing the resulting BACPAC to a database with a different name will always fail, as the three-part name references would no longer be self-referencing.

Resolution:

1. Modify your database schema, removing all of the self-referencing three-part name references, reducing them to a 2 part name.

There are many tools/mechanisms by which you can accomplish fixing your schema to remove these external references. One option is to use SQL Server Data Tools (SSDT). In SSDT, you can create a database project from your Azure database, setting the target platform of the resulting project to “SQL Azure”. This will enable Azure-specific validation of your schema which will flag all three-part name/external references as errors. Once all of the external reference errors identified in the Error List have been remedied, you can publish your project back to your Azure database and resume usage of the Import/Export Service.

Getting Started with SQL Server Database Unit Testing in SSDT

Bill Gibson MSFT — Fri, 07 Dec 2012 08:20:00 GMT

SSDT now enables you to develop, debug and execute database unit tests interactively in Visual Studio, which can then be run from the command line or from a build machine, for example, a Team Foundation Build server configured for continuous integration. SSDT helps put database testing on an equal footing with other aspects of application testing, helping you raise and then maintain the quality of your SQL Server database applications. This post provides a quick introduction to SQL Server database unit testing with SSDT. For a more detailed information and a more comprehensive walkthrough available see Verifying Database Code by Using SQL Server Unit Tests in MSDN.

Unit testing SQL Server databases with SSDT is very straightforward, although there are a couple of things to look out for. First you must have Visual Studio 2010 or 2012 Professional edition or higher installed. If you have Visual Studio 2010 Premium or Ultimate edition installed then the new SQL Server database unit testing installs alongside the existing database unit testing from Visual Studio. You can continue to use the old tools but you cannot mix database unit tests created by both versions in the same test project - more on this below.

Test Projects and converting existing Test Projects

SQL Server unit tests are created in a normal VB or C# Test project. The MSTest infrastructure is used to run the tests and view the results. If you have existing test projects containing database unit tests created with Visual Studio 2010 then you must convert these projects before working on them with SSDT. To convert, simply right-click on the test project in Solution Explorer and select Convert to SQL Server Unit Testing project...

SSDT introduces a new SQL Server Unit Test template and type. There are two ways to create SQL Server unit tests in a test project: either by generating tests from a database project opened in SQL Server Object Explorer (SSOX), which creates unit tests with a skeleton T-SQL script for you to complete, or by manually adding unit tests into a test project using the template. If you create tests from SSOX you will have the option to create a new test project or add the tests into an existing project. In many cases you will find the generated skeleton scripts a great starting point so be sure to try these out.

Generating SQL Server Unit Tests from objects in SQL Server Object Explorer

If you have a SQL Server database project in your solution you can generate unit tests from any stored procedure, function or DML trigger defined in that project. To do this, locate the project beneath the new Projects node in SSOX, and then locate and right-click the object you want to test and select Create Unit Tests... (see below). You can generate tests for an individual object, or by selecting its parent node in SSOX, generate tests for all objects in that node. If for any reason you don't have access to a database project for the database that you want to test, you can connect to the database in SSOX, right-click it, and then select Create New Project to create a project for this purpose.

In the dialog that follows (see below) check all the object(s) for which you want tests generated and choose whether to create a new test project or have the test(s) added to an existing test project. This dialog shows you all the candidate objects in the project that you are working with. If the project has same-database references to other projects or dacpacs, then these references are resolved and the dialog will include candidate objects from the referenced projects and dacpac. Once you have selected all the source objects you want to use, click OK and the project and/or tests will be generated.

Manually Creating a SQL Server Unit Test

You can also add empty tests to a project manually and define them from scratch. To do this, create or open a test project, right click the project in Solution Explorer, and then use Add > New Item and locate the SQL Server Unit Test template under the SQL Server node.

In Visual Studio 2010 there is a streamlined Add > New Test option, although note that if you are have either the Premium or Ultimate edition installed, ensure that you use the new SQL Server Unit Test template provided by SSDT and NOT the 'old' Database Unit Test template that was originally installed with Visual Studio 2010 (see below). If you do add a Database Unit Test by mistake then you will need to convert the project as described above before it will build. (To remove temptation you might want to delete or rename the old template in Visual Studio once you have converted all your old-style DB Pro database unit test projects).

Configuring the Test Project

Whichever route you choose to create database unit tests, when you first add a SQL Server unit test to a test project you will be prompted to configure the project for SQL Server unit testing. In the configuration dialog (see below) choose the database you want to test, and, optionally, a SQL Server database project to deploy before your tests are run. The example below uses the default LocalDB debug database created by SSDT for a database project, but you can use any database, or create a new database from this dialog. The ability to specify or create a database during test configuration allows you to test different instances of the same database without disturbing the source project’s debug database. If you use a LocalDB database you will have to create a new connection from the configuration dialog, and specify (LocalDB)\Projects as the server name. If you choose to deploy a database project when you run your tests, it will deploy using the connection string you specify in this dialog, with the deployment properties specified in the Debug tab of the database project's Properties page. Note that you can change the test project's configuration at any time from the project's context menu or from the SQL menu with the test project selected.

Define your T-SQL Test Script

With test project configuration done, the database unit test designer will be open on the test you created allowing you to define the test script and set test conditions. If you chose to generate a skeleton test script you will now see that in the upper editor pane (below). You now need to either write you test script or tweak the generated skeleton. Your script should exercise the objects in the database that you wish to test. You can either use THROW or RAISERROR during execution to indicate a test has failed, or evaluate the results using test conditions.

Defining Test Conditions

When your test is executed the test script is submitted to the database and the results are passed back to the test to be evaluated using one or more test conditions. Once your T-SQL script is ready, you should remove the default Inconclusive test condition from the lower pane (which will always fail), and then add one or more appropriate test conditions from the drop-down list and configure them if required in the properties window (see above).

For more information about writing test scripts and using test conditions, including use of setup and cleanup scripts see Creating and Defining SQL Server Unit Tests in MSDN.

Running the Test

At this point you need to build the test project and run your test and examine the results. Before you build the project for the first time you should delete the default VB or C# test class file created by default in every new test project. You can run the test from the Test > Run menu. When you run your tests from this menu the project will build automatically if you have not built it before or have made changes to the tests.

In Visual Studio 2010 you can view all the tests in your test project and run them selectively from the Test > Windows > Test View window, and view the results in the separate Test Results window (see below).

In Visual Studio 2012, you can view your tests, run them, and check the results all in one place using the new Test > Windows > Test Explorer window (see below).

Note that you must build the test project after adding a test for the test to be visible in Test View or Test Explorer.

For more information about using database unit testing see, Verifying Database Code by Using SQL Server Unit Tests in MSDN.

Welcome to SQL Server database unit testing in SSDT !

SQL Server Data-Tier Application Framework (November 2012) Available

Adam Mahood [MSFT] — Fri, 16 Nov 2012 23:26:36 GMT

What’s new?

This release of the Data-Tier Application Framework (DACFx) brings fixes for several customer-reported and high-priority issues including:

SSDT crashes when opening a table that contains specific computed column definitions from SQL Server Object Explorer
Incorrect parsing errors when using system functions (@@) in specific scripts inside SSDT
Importing a BACPAC to Windows Azure SQL Database may experience data loss when connection to database is being throttled
Exporting a Windows Azure SQL Database to a BACPAC file may experience data loss when connection to database is being throttled

The team thanks you for your feedback in reporting these issues!

With this release, we’ve also made significant improvements in overall operation performance and stability when targeting Windows Azure SQL Database with DACFx.

How can I get it?

(Update 11/19) If you are on an x64 machine, you will need to install both the x64 and x86 versions of the MSIs from the DACFx November download page linked above.

Compatibility

This release of DACFx is fully compatible with the November 2012 release of SQL Server Data Tools released on 11/7, available here. This release is also compatible with SSMS of SQL Server 2012 and SQL Server 2012 SP1.

If you experience any issues or have any feedback, please let us know via the forum or Connect. We look forward to hearing from you!

SQL Server Data Tools - November 2012 is now available!

Janet Yeilding — Wed, 07 Nov 2012 18:22:00 GMT

We are pleased to announce that SSDT - November 2012 update is now available for download.

Get it here

SSDT for Visual Studio 2012: http://msdn.microsoft.com/en-us/jj650015

SSDT for Visual Studio 2010: http://msdn.microsoft.com/en-us/jj650014

What's new?

Selective XML Index support

We've added support for selective XML indexes, enabling users to import, edit, add, refactor, build, and publish selective XML indexes in SSDT.

Add new selective XML index in Table Designer

Check for SSDT Updates

This release adds support for automatic and manual checks for SSDT updates. You can view information about your current SSDT installation and verify that it's up to date by selecting "Check for Updates…" under the top-level SQL menu in Visual Studio.

Check for Updates dialog

This feature also notifies users when a newer version of SSDT is available for download.

SSDT update notification

Updated Data-Tier Application Framework (DACFx)

SSDT – November 2012 includes the October DACFx redist (11.1.2816.0). The October DACFx release contains several feature enhancements and bug fixes outlined in this post: http://blogs.msdn.com/b/ssdt/archive/2012/10/10/sql-server-data-tier-application-framework-october-2012-available.aspx

Updated SQL Server 2012 components

SSDT – November 2012 is coordinated with the release of SQL Server 2012 Service Pack 1 and it chains in the latest SQL Server components.

Bug fixes

This release contains over 30 bug fixes, including fixes for customer-reported issues from SSDT - September 2012.

Power Tools Compatibility

The November 2012 update of SSDT is only compatible with the latest SSDT Power Tools (v 1.4). Please note that if you have an existing version of SSDT Power Tools, it will need to be upgraded in order to work with SSDT – November 2012. Edit: SSDT Power Tools are no longer available via the links below, but have been integrated into the core SSDT product in the December 2012 release (http://blogs.msdn.com/b/ssdt/archive/2012/12/13/available-today-ssdt-december-2012.aspx)

SSDT Power Tools for Visual Studio 2012

SSDT Power Tools for Visual Studio 2010

Contact Us

If you have any questions or feedback, please visit our forum or Microsoft Connect page. We look forward to hearing from you.

SSDT Team at PASS Summit

Janet Yeilding — Thu, 01 Nov 2012 19:45:00 GMT

PASS Summit 2012 is just around the corner! If you’ll be at PASS next week, make sure to sync up with the SSDT team through one of the following avenues. We look forward to seeing you there.

Booth

SSDT members will be staffing the Optimization & Programmability booth in the Exhibit Hall, where we’ll be able to discuss SSDT and answer any questions you may have.

Breakout Session

Database Development with SSDT and Visual Studio 2012 (AD-321-M)

Friday, November 9 at 2:45 – 4:00 PM

Speakers: Barclay Hill, Adam Mahood, Gert Drapers

Tired of hand-coding change scripts to develop, deploy, upgrade, and migrate your databases? Come see the next generation of database development tools in Visual Studio 2012. SQL Server Data Tools (SSDT) transforms traditional database development by introducing a declarative, model-based experience that supports both online and offline (project-based) database development. Many of the development features enjoyed by application developers for years are now available to database developers to manage their databases. This session will introduce SSDT and dive into a series of demonstrations on how you can develop, debug, refactor, and maintain SQL Server and SQL Azure databases from within the Visual Studio 2012 integrated environment.

Chalk Talks

SQL Server 2012 LocalDB: Your New Friend

Wednesday, November 7^th at 1:30 – 2:00pm in Room RC-4

Speaker: Gert Drapers

Need a local database for your application? Want it to have the same programming model as SQL Server? Need it to be under full control of your application? SQL Server 2012 LocalDB will give you all this. Gert will discuss how to embed SQL Server LocalDB underneath your application.

Declarative Database Deployment, Tell me what you want, Not how you want to get there!

Wednesday, November 7^th at 3:30 – 4:00pm in Room 4C-4

Speaker: Gert Drapers

Wouldn’t be great if you can describe how you want your schema to look like, instead of writing down how to implement it? Declarative database deployment, the underpinning of SQL Server Database Tools – Database Projects gives you exactly that. Gert will discuss the fundamental behinds DAC and the database deployment engine.

Building & Deploying SSDT projects without Visual Studio

Thursday, November 8^th at 2:30 – 3:00 in Room 4C-4

Speakers: Patrick Sirr and Mike Kaufman

Speakers will give a review of how to use SQL Server Developer Tools (SSDT) projects outside of Visual Studio. Specifically, we’ll cover MSBuild integration, TFS integration & integrating deployment tasks into broader commandline and powershell scripts.

Hands on Lab

Getting Started with SQL Server Data Tools in SQL Server 2012 (SQL 161)

Daily in room 304 (3rd floor of TCC )

SQL Server Data-Tier Application Framework (October 2012) Available!

Adam Mahood [MSFT] — Wed, 10 Oct 2012 18:53:00 GMT

What’s new?

This release of the Data-Tier Application Framework (DACFx) brings fixes for issues in earlier releases and several major updates. Many scenarios have been improved including those in other DACFx client tools such as SQL Server Data Tools (SSDT) and SQL Server Management Studio (SSMS). Updates include:

Support for Native BCP data format

Previously the data format used to store table data inside DACPAC and BACPAC packages was JSON – with this October update, we have moved to Native BCP as the data persistence format.
This change brings improved SQL Server data type fidelity to DACFx including support for SQL_Variant types as well as enhanced data deployment performance for large scale databases

Support for Selective XML Index

The upcoming release of SQL Server 2012 SP1 will include support for a new T-SQL construct and SQL Server engine feature, Selective XML Index (SXI) – a new way of indexing XML column data with increased performance and efficiency.
DACFx now supports SXI indexes across all DAC scenarios and client tools.
You can try out this new SQL Server feature today by downloading the CTP of SQL Server 2012 SP1 available here.

Preservation of Check Constraint state across package creation/deployment

Previously, DACFx did not preserve the state (WITH CHECK/NOCHECK) of check constraints defined on tables in the database schema or store this information inside DACPACs – this could lead to potential issues on package deployment when there is existing table data that violates check constraints.
DACFx now stores the current state of check constraints within the DACPAC when extracted from a database and appropriately restores this state upon package deployment.

Package compatibility

This release introduces several forward compatibility scenarios for DAC packages.

All DAC packages created by this release that do not contain SXI elements or table data may be consumed by previous releases of DACFx (SQL Server 2012 RTM, SQL Server 2012 CU1, and DACFx September, 2012).

Additionally, all DAC packages created by previous versions of DACFx can be consumed by this release.

How can I get it?

Compatibility

This release of DACFx is compatible with the November 2012 release of SQL Server Data Tools released on 11/7, available here. This release is also compatible with SSMS of SQL Server 2012 and SQL Server 2012 SP1.

If you experience any issues or have any feedback, please let us know via the forum or Connect. We look forward to hearing from you!

SQL Server Data Tools Team Blog

SQL Server Data-Tier Application Framework (May 2013) Available

What’s new?

How can I get it?

Compatibility

SQL Server Data-Tier Application Framework (March 2013) Available

What’s new?

How can I get it?

Compatibility

SQL Server Unit Testing using Visual Studio 2010 and Visual Studio 2012 Side by Side

Available Today: SSDT—December 2012

The SSDT team is pleased to announce that SQL Server Data Tools - December 2012 is now available for download!

Get it here:

What’s New?

Database Unit Testing

Integration of SSDT Power Tools

Updated Data-Tier Application Framework

Bug fixes

Contact Us

Windows Azure Import/Export Service and External References

Scenario:

Symptom:

Issues:

Why:

Getting Started with SQL Server Database Unit Testing in SSDT

SQL Server Data-Tier Application Framework (November 2012) Available

What’s new?

How can I get it?

Compatibility

SQL Server Data Tools - November 2012 is now available!

Get it here

What's new?

Selective XML Index support

Check for SSDT Updates

Updated Data-Tier Application Framework (DACFx)

Updated SQL Server 2012 components

Bug fixes

Power Tools Compatibility

Contact Us

SSDT Team at PASS Summit

Booth

Breakout Session

Chalk Talks

Hands on Lab

SQL Server Data-Tier Application Framework (October 2012) Available!

What’s new?

Support for Selective XML Index

Preservation of Check Constraint state across package creation/deployment

Package compatibility

How can I get it?

Compatibility