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 your project. Start by choosing the Import Script option. Find your script

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 those changes. Other times you may just want to see what will

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 table, remove data that could cause a problem, or insert some data

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 from Adventureworks2008, you’ll need to add that as a database reference.  

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.   Project Settings Here you can set your normal target platform (SQL

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 -> Database option. Note that you can also import from SQL Scripts

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 start by creating a new Project or create a new project from

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 make changes directly to the database and if we’re good, we remember

Tales of a Lazy DBA–MySQL, SSIS, and “0” Dates

We’ve recently been tasked with converting a lot of MySQL Data into our system from a multi-tenant MySQL Database. We don’t have a fixed schedule to actually execute the imports because they’ll be on a “per customer”

Installing SQL Server, Sharepoint, PowerPivot on a single server

I’ve been trying to set up a single virtual machine for a proof of concept using SQL Server Denali CTP3, Sharepoint 2010, and PowerPivot. I want to get Project “Crescent” running through this as well to prove