Source Control for MS SQL Server
-
as the title says, can anybody recommend a source control system for MS SQL server. I know I could just save the .sql files in something like subversion, however I would prefer something that tracks changes as they are made to the database. It would be very nice if it had the ability to create an SQL script of all changes from revision X to revision Y
-
as the title says, can anybody recommend a source control system for MS SQL server. I know I could just save the .sql files in something like subversion, however I would prefer something that tracks changes as they are made to the database. It would be very nice if it had the ability to create an SQL script of all changes from revision X to revision Y
SourceVault
-
SourceVault
Are you talking about SourceGear Vault[^]? Does it have specific support for SQL server databases? Or just for SQL scripts as text files? BTW, how has it been? ;)
Luis Alonso Ramos Intelectix Chihuahua, Mexico
Not much here: My CP Blog!
-
as the title says, can anybody recommend a source control system for MS SQL server. I know I could just save the .sql files in something like subversion, however I would prefer something that tracks changes as they are made to the database. It would be very nice if it had the ability to create an SQL script of all changes from revision X to revision Y
Just looking at CodeProject advertisments, I found these two links that might be of interest: Innovartis DB Ghost[^] Red-Gate Software[^] I hope they help! :)
Luis Alonso Ramos Intelectix Chihuahua, Mexico
Not much here: My CP Blog!
-
Are you talking about SourceGear Vault[^]? Does it have specific support for SQL server databases? Or just for SQL scripts as text files? BTW, how has it been? ;)
Luis Alonso Ramos Intelectix Chihuahua, Mexico
Not much here: My CP Blog!
I believe SourceGear can be running in SQL. Been great! Will install this weekend!!! Can't wait! Al
-
as the title says, can anybody recommend a source control system for MS SQL server. I know I could just save the .sql files in something like subversion, however I would prefer something that tracks changes as they are made to the database. It would be very nice if it had the ability to create an SQL script of all changes from revision X to revision Y
We use a product called Speed SQL IDE Pro now from Quest Software. They're doing away with this and replacing it with something called TOAD for SQL Server, currently I think it only version controls projects but I've been told the next version will control all database objects. I'm keeping my eye on it as I'm always using the version control integration. Failing that if you are looking to upgrade to MSSQL 2005 you could just use database triggers to track changes.
-
I believe SourceGear can be running in SQL. Been great! Will install this weekend!!! Can't wait! Al
Albert Pascual wrote:
I believe SourceGear can be running in SQL.
I think he means he wants his database in some sort of source control. Not that he wants his source control to use SQL Server as a backend.
They dress you up in white satin, And give you your very own pair of wings In August and Everything After
I'm after everything
-
I believe SourceGear can be running in SQL. Been great! Will install this weekend!!! Can't wait! Al
Albert Pascual wrote:
I believe SourceGear can be running in SQL.
Yes, Vault will run with a SQL Server backend, but it doesn't have special support to version-control SQL databases. Only if you always scripted your DB, you could put it in version control (that's what I do).
Albert Pascual wrote:
Been great! Will install this weekend!!! Can't wait!
Don't forget to tell us how it goes! :)
Luis Alonso Ramos Intelectix Chihuahua, Mexico
Not much here: My CP Blog!
-
We use a product called Speed SQL IDE Pro now from Quest Software. They're doing away with this and replacing it with something called TOAD for SQL Server, currently I think it only version controls projects but I've been told the next version will control all database objects. I'm keeping my eye on it as I'm always using the version control integration. Failing that if you are looking to upgrade to MSSQL 2005 you could just use database triggers to track changes.
Is MSSQL 2005 you can also save any changes made with the SQL Management Studio GUI to a .sql file. Makes it easy to keep track of changes and still use the GUI tools. 60% of statistics are made up on the spot