Comments

Want more?  Check out all the presentations, demos and labs at http://bit.ly/sql2012cookbook.

You can see part 4 of this demo in this post.

Want more?  Check out all the presentations, demos and labs at http://bit.ly/sql2012cookbook.

You can watch part III in this post.

Want more SQL Server 2012 content?  Check out all the presentations, demos and labs at http://bit.ly/sql2012cookbook.

Check out Part II of the keynote demo here.

Want more? Check out all the great SQL Server 2012 presentations, demos and labs at http://bit.ly/sql2012cookbook.

@services house:glad you like it!

@lsjames:I'd have to dig into your scenario a bit to answer this fully.  In general, DAC upgrade will try the most minimally invastive upgrade strategy possible.  I'm a bit suprised that it's messing with users, are you using DAC Fx 3.0 (that ships with RTM SQL 2012)?

@Borum.NET: thanks for the comments!  Here's some answers to your questions:

Q: Is there a managed API (like the SQL SMO) that allows us to include dacpac files in our own installer and subsequently deploy (clean install / upgrade) to on premise SQL Server or SQL Azure?

A: DAC Fx has an API surface, check out http://sqldacexamples.codeplex.com

Q: The scenario I'm thinking of is having a single SQL Server Data Tools project as part of our solution and using TFS builds output dacpac files for SQL Server or SQL Azure (i.e. targetting the two different environments via configuration and then build the dacpacs). Is that possible?

A: Absolutely.  Think of .dacpac and .bacpac as a single-file deployment capability for schema (.dacpac) and schema + data (.bacpac).

Check out all the related decks, demos and labs at http://bit.ly/sql2012cookbook.

Check out all the related decks, demos and labs at http://bit.ly/sql2012cookbook.

Check out all the related decks, demos and labs at http://bit.ly/sql2012cookbook.