Category: SQL Project
SSDT: Updating a Project Manually
Sometimes it’s necessary to modify the project manually. The change might require specific tweaking to include just a couple of new lines in a stored…
SSDT: Updating a Project by Importing Scripts
Sometimes your developers will work on new SQL Objects and give you scripts to alter or create objects. SQL Projects support importing those scripts into…
SSDT: Updating by Using Schema Compare
Sometimes changes are made to a shared database that need to be brought into your SQL Project and there are no saved change scripts for…
SSDT: Pre and Post Deploy Scripts
At some point, you will likely need to release changes that contain more than just schema changes. You may need to update data in a…
SSDT: External Database References
If your database references other databases, you’ll need a *.dacpac file for each external database referenced in your code. For example, if you reference AdventureWorksDW2008…
SSDT: SQL Project Options
To set the properties for your SQL Project, right-click the Project and select Properties. You’ll see a window containing several tabs to define your project….
SSDT: Importing an Existing Database
To Import From an Existing Database Import Database into your project by right-clicking the project name or selecting the Project Menu and selecting the Import…
SSDT: Creating a New SQL Project
Download the latest SSDT package if you do not have the product installed already: http://msdn.microsoft.com/en-us/data/tools.aspx To create a new SQL Project, you can either…
SSDT: Why Use SQL Projects?
What Are SQL Projects and why use them? SQL Server has always been lacking in a good solution to control versions of your database. We…