What do you all use? I have subversion (+ Tortoise) for my most of my code, just need to get something in place for my SQL code. I have money to spend if needed, but free is always good too!

1/30/2013 2:53:29 PM

git init
http://git-scm.com/

You can do it local.

1/30/2013 2:58:27 PM

hey Noen, source control for sql server should be part of sql management studio. get on it. also upgrade sql management studio from vs2010 to vs2012 while ur at it.

[Edited on January 30, 2013 at 3:28 PM. Reason : a]

1/30/2013 3:27:44 PM

Why don't you just version your SQL code the same way?

1/30/2013 3:28:09 PM

well you have to do a diff to get the actual sql and then save it as .sql and move it into subversion. it would be nice if there was a tool that did the diff and commit for you.

1/30/2013 3:29:32 PM

Wait, what?

If you have vs2010/2012, why the hell would you use SQL management studio instead?

Are you not using a db project? I is confused.

1/31/2013 3:07:03 AM

im on sql2000 so nothing in vs works.

also the vast majority of our database design is totally separate from specific projects in vs so it would never make sense to do the design in visual studio anyways.

what I want is something that can version schemas and also migrate schemas from dev -> accept -> prod. this would be nice if it was a feature of sql server/sql management studio.

[Edited on January 31, 2013 at 12:07 PM. Reason : s]

1/31/2013 12:04:57 PM

^ yes please.

[Edited on January 31, 2013 at 4:08 PM. Reason : ]

1/31/2013 4:03:54 PM

^^ dear god man, why? You can still use vs2008 against sql2000, but damn its worth the upgrade.

Unfortunately, SQL and VS (and TFS) pretty much stay in step. So you pretty much need 2005/2008 to be able to leverage VS. But I do exactly what your asking for right from VS with SQL server 08

2/1/2013 12:51:25 AM

we're moving to 2012 later this year. I guess maybe if I can write all the procs and shit in vs then it might be ok, but idk why this isn't a feature of sql server and its tools (management studio).

im talking about versioning of procs + views + table schemas on and individual level instead of as part of a visual studio project. I may have a set of procs + views that's used by 3 different projects and I don't want to have to have a separate visual studio project just for the data because the data project wont be a nice 1:1 relationship between code project + data project. I'd essentially need an entire project for the server, which would obviously make more sense in a tool designed for managing the server.

If I can right click and object in management studio and commit it to source control then the problem goes away and everything becomes so much nicer.

2/1/2013 9:19:16 AM

Management studio is VS, just a custom shell.

And maybe I'm not understanding, but what your saying doesnt make sense to me. Who said anything about having the code and db projects together? If your db is being shared by multiple projects, there are different options depending on how your org works.

Many shops use the single solution approach, where all groups work off the same master solution and you just have projects for each code project and db, etc. Generally this approach works really well, I've seen extremely large corporations use this for monstrously big products with hundreds of projects across dozens of dev teams.

You can also break up projects as you see fit, and isolate things like your db from the rest of the code. But in either case, there's an entire suite of tooling in VS specifically there to do what you are asking for. Schema diffs, mapping, versioning, etc.

Management studio is like the express edition of VS for databases.

2/2/2013 7:44:39 AM

I can't imagine using anything other than Visual Studio 2010/12 to manage Server/DB projects.

2/3/2013 8:23:55 AM