SQL Server Data Tools. Gavin Campbell

Transcription

1 SQL Server Data Tools Gavin Campbell

2 Why are we here

3 SOFTWARE Why do we have software? Image courtesy of Computer History Museum

4 CHANGE Image: public.resource.org

5 Image: canticle at en.wikipedia If it didn t change, it would be called HARDWARE

6 Software is easy to change

7 Deploying software changes Overwrite the old with the new Side-by-side installation Replace the whole VM None of these techniques will work for our database code. The database has memory or state The state is in the data Any changes we make need to preserve the data, and hence the state

8 Database Changes How can we make database changes without destroying our data?

9 DEMO MANAGING DATABASE CHANGE WITH SCHEMA MOVEMENT SCRIPTS

10 SCHEMA MOVEMENT SCRIPTS Need to be IDEMPOTENT A function f : D -> D is idempotent if f (f x) = f x for all x in D. i.e. repeated applications have the same effect as one Free Online Dictionary of Computing

11 SCHEMA MOVEMENT SCRIPTS Can grow to be very long Some changes can be complicated to implement Can lead to run-time (i.e deploy-time) errors Emphasise the non-functional over the functional Force us to use a declarative language in an imperative manner

12 Declarative vs Imperative Describe what we want Let me get an Upside down, Halfcaf, triple venti nonfat no whip peppermint white chocolate mocha Extra Hot Programming Describe how to do it Ask the customer their name Put two shots of peppermint syrup in the cup Msg 8623, Level 16, State 1, Line 3 Put three shots of half-caf espresso in the cup The query processor ran out of internal resources and could not. produce a query plan.

13 Declarative vs Imperative Programming

14 Look Familiar?

15 SSDT A better mousetrap? Development Experience Deployment Tools

16 WHAT S IN A NAME? Visual Studio 2005 Team Edition for Database Professionals (aka DataDude) Visual Studio Team System 2008 Database Edition Visual Studio Team System 2008 Database Edition GDR Visual Studio 2010 Database Projects (aka DBPro) Project Juneau SQL Server Data Tools

17 INSTALLING SSDT?

18 What does this button do?

19 Installing SSDT?

20 Installing SSDT?

21 FUN FACTS ABOUT SSDT Download from microsoft.com Updated several times per year Available for VS2010, VS2012 Installs Visual Studio shell if none available No separate download for VS2013, but available in express SKUs As of now, SQL Server 2014CTP2 only supported in the VS2012 version

22 SSDT A better mousetrap? Development Experience Deployment Tools

23 CONNECTED DEVELOPMENT Using the SQL Server Object Explorer in Visual Studio, developers can now create, edit and browse database objects located in either an onpremise database server, such as SQL Server 2008 or Microsoft SQL Server 2012, or offpremise in SQL Azure.

24 DEMO CONNECTED DEVELOPMENT

25 CONNECTED DEVELOPMENT Why not try it out back at the office?

26 Project based Development Brings Visual Studio features to T-SQL development Source Control Integration Refactoring Navigation Debugging Static Analysis Unit Testing*

27 Software Development Code Deploy Build Test

28 Database Development?

29 Project based Development For developers with limited or no access to a live (production) database, SSDT provides an improved development experience over the existing Visual Studio database projects.

30 DEMO PROJECT BASED DEVELOPMENT

31 SSDT A better mousetrap? Development Experience Deployment Tools

32 Data Tier Applications Introduced in SQL Server 2008 R2 Support added to SQL Server 2008 SP2 (but not in SSMS!) Special Visual Studio project type Original Version only supported side-by-side upgrades In place upgrade supported in SQL Server 2008 R2 SP1 and VS2010 SP1.dacpac file extension This is the build output from SSDT

33 Data Tier Applications Deploy from Visual Studio??? Deploy from SSMS using the Wizard Deploy from the command line using sqlpackage.exe All of these use the DacFX API

34 SQLPackage.exe Extract: Creates a database snapshot (.dacpac) file from a live SQL Server or Windows Azure SQL Database. Publish: Incrementally updates a database schema to match the schema of a source.dacpac file. If the database does not exist on the server, the publish operation will create it. Otherwise, an existing database will be updated. Script: Creates a Transact-SQL incremental update script that updates the schema of a target to match the schema of a source.

35 SQLPackage.exe Provides greater flexibility than the SSMS Wizard Can be automated using PowerShell,.bat files, Continuous Integration tools, etc.

36 SUMMARY Easier Development with SSDT Easier Deployment with DacFX

37 More information SSDT Team Blog Jamie Thomson hive/tags/ssdt/default.aspx Technitrain London 3-4 March 2014

38 THANK YOU