New SSDT Power Tools! Now for both Visual Studio 2010 and Visual Studio 2012

re: New SSDT Power Tools! Now for both Visual Studio 2010 and Visual Studio 2012

Brian Baker — Thu, 08 Nov 2012 20:17:45 GMT

It would be helpful to tag this post with the 'SSDT Power Tools' tag.

re: New SSDT Power Tools! Now for both Visual Studio 2010 and Visual Studio 2012

psirr — Mon, 29 Oct 2012 18:20:28 GMT

I'd suggest altering your project (via the Debug property page) to point to a different database for each branch. Ideally don't do this in the project file because you'll get merge conflicts. Instead I'd create something to distinguish one branch from another and use that in a .targets file you import into your .sqlproj.

For instance, if you have an environmental variable called "Branch2" then use that to alter your TargetDatabase:

Contents of Branch.Targets:

<?xml version="1.0" encoding="utf-8"?>

<TargetDatabase>Branch2</TargetDatabase>

</PropertyGroup>

</Project>

Now place the import of Branch.Targets after the import of our targets file in the .sqlproj.

re: New SSDT Power Tools! Now for both Visual Studio 2010 and Visual Studio 2012

Alex Castillo Pacheco — Fri, 26 Oct 2012 18:19:37 GMT

Don't know if my problem is related with this update but after applying this update my localdb structure in SSOX got completely ruined!!

Let me try to explain myself: I work with SQL projects in VS2010 and TFS 2010, I have the same database projects branched for each of my clients, each client has mostly 3 branches each: Main, Dev and Release. Each solution/branch has 10 databases projects in them. The problem is that if I compile all the branches in the same machine the (localdb)\projects structure in SSOX shows something like this:

(localdb)\projects

MyDB

MyDB_1

MyDB_2

And so on. So I end up with about 30 databases for each of my clients not knowing which one corresponds to what branch:

TFS_Team SSOX

Clientbranch-Main (localdb)\projects

|-Clientbranch-Dev MyDB

|_Clientbranch-Release MyDB_1

Client2-Main MyDB_2

|-Client2-Dev MyDB_3

|_Client2-Release MyDB_4

Also there used to be a folder inside each of my SQL projects called Sanbox, now is no longer generated, and all the files are now stored in

C:\Users\myuser\AppData\Local\Microsoft\Microsoft SQL Server Local DB\Instances

I liked the old way of store because I downloaded my projects lets say to a D drive with more space in it, now everything is stored in C and again I don´t know which file corresponds to what project :(

Is there a way to consider this TFS scenario and branching model to group in SSOX the Databases depending in the TFS branch name? It doesn't work naming after the sln name because is the same in every branch.

re: New SSDT Power Tools! Now for both Visual Studio 2010 and Visual Studio 2012

msbigot Ah, Script action — Tue, 02 Oct 2012 18:47:56 GMT

If it would'a been a snake, it would'a bit me.

re: New SSDT Power Tools! Now for both Visual Studio 2010 and Visual Studio 2012

Mike B — Tue, 02 Oct 2012 18:45:49 GMT

I don't know if this is the appropriate place, but I've noticed a curious thing about Synonyms. I can't get my synonym bound to the right database (even when I use the $(DatabaseName). notation in the CREATE). Oh, I should mention this is via MSBuild and SqlPackage. Is this behavior, by design?? The database name I get is the one that I imported to create the sql project. Thanks.

re: New SSDT Power Tools! Now for both Visual Studio 2010 and Visual Studio 2012

Janet Yeilding — Tue, 02 Oct 2012 16:52:14 GMT

@Cyclon2005 Uninstall instructions are detailed here: msdn.microsoft.com/.../jj542427(v=vs.103).aspx

@msbigot Thanks for the positive feedback. sqlpackage's Script action handles the scenario you've described. Let me know if you have any questions about how to invoke it.

re: New SSDT Power Tools! Now for both Visual Studio 2010 and Visual Studio 2012

msbigot — Mon, 01 Oct 2012 16:03:48 GMT

I have a quick question re the new Sept release. It's my understanding that there is NOT a command-line way to generate the publish.sql script (i.e., script that is generated in the UI's 'generate script' button). Is that correct?? I've scoured sqlpackage documentation and haven't found a hit. Thanks for reading. BTW I love SSDT. Currently trying to get it adopted in my shop.

re: New SSDT Power Tools! Now for both Visual Studio 2010 and Visual Studio 2012

Cylon2005 — Thu, 20 Sep 2012 13:11:05 GMT

I can't uninstall SSDT from VS2010. When I try to build my solution, VS2010 says it cannot create an App Domain.

re: New SSDT Power Tools! Now for both Visual Studio 2010 and Visual Studio 2012

Andrei — Wed, 19 Sep 2012 09:53:43 GMT

Guys,

Data-tier Application/*.dacpac is a great feature, but when you select tables they are not sorted alphabetically. That is quite inconvenient.