|
|
|
Valued Member
 
Group: General Forum Members
Last Login: Monday, February 08, 2010 6:19 AM
Points: 59,
Visits: 87
|
|
| Are there any freeware tools that help to manage database version?
|
|
|
|
|
SSC Veteran
Group: General Forum Members
Last Login: Wednesday, November 18, 2009 8:08 AM
Points: 224,
Visits: 137
|
|
Hi John,
You have hit the nail on the head when you are discussing Visual SourceSafe and SSMS - if you are to use the default integration then you have to edit files within a project basically outside of the database (although within the SSMS editor).
You rightly say that there is no link or constraint between the actual object within the database and the files in the project, they are simply external scripts that affect database objects. This means that people can make modifications to the database objects without having to update the version of the file in Visual Sourcesafe. The database won't even complain that changes are being made outside of the version control.
We want to have a tool that will prevent people changing database objects without first updating the version control system. This projects feature within SSMS is an alternative to the technique we use of scripting the objects to a file in a folder and then adding them into sourcesafe. On the downside though as you mention the interchangability of 'CREATE PROCEDURE....' and 'ALTER PROCEDURE...' can give false changes within a module, whereas using the scripting tool within the database gives a more consistent script.
itamar has mentioned a tool I've never heard of before - I think we will be looking at that to see whether it does what we want - or at least does a better job than what we are managing with at the moment.
Tony
|
|
|
|
|
Valued Member
Group: General Forum Members
Last Login: Wednesday, February 24, 2010 11:45 AM
Points: 55,
Visits: 2,246
|
|
I've just read through this thread, hoping, hoping, that someone had found a 'great' (or workable) solution. Alas, it isn't so. I'll add, though, that in the VS6 days source control was integrated, truly integrated into the interface such that when opening up an SP, its contents were checked against the VSS version and the user was warned if different.
Now, I wonder if a solution for storing changes might lay with DDL triggers firing off a CLR assembly that interfaces the VSS API. Too bad my skill-level isn't good enough, and time is too short. But: maybe someone can make their million?
Cheers,
Mark
Mark
Just a cog in the wheel.
|
|
|
|
|
SSC Eights!
Group: General Forum Members
Last Login: 2 days ago @ 8:00 AM
Points: 903,
Visits: 1,503
|
|
Take a look at message 474053 which describes our method.
http://www.sqlservercentral.com/Forums/FindPost474053.aspx
I describe how we store each object as a separate file in the source code control system (currently Perforce, but Visual SourceSafe before), address the CREATE/ALTER/DROP issue with stored procedures, etc. and guarantee that the upgrade script is consistent.
Not all of the tools will generate a proper "upgrade" script.
Examples:
In our last upgrade we needed to change an XML schema collection. This required that we properly "unwind" any bindings, make the change, and then rebind the XML schema to the various objects. An interesting sequence of operations that I doubt any software tool will do.
Often, as part of a schema change we need to change some meta data values that are stored in tables.
So if the tool will not generate a complete upgrade script and you still have to make manual changes to the script, then the tool hasn't provided any benefit.
(PHB) I think we should build an SQL database. (Dilbert) What color do you want that database? (PHB) I think mauve has the most RAM.
|
|
|
|
|
SSC Journeyman
Group: General Forum Members
Last Login: Tuesday, August 25, 2009 12:25 PM
Points: 82,
Visits: 171
|
|
| May be you know this utility for your source control http://www.dynamsoft.com/Downloads/SAW_Download.aspx
|
|
|
|
|
SSCommitted
Group: General Forum Members
Last Login: Thursday, December 31, 2009 12:56 AM
Points: 1,859,
Visits: 4,533
|
|
How about Visual Studio Team Suite 2005 / 2008...?
I have tried Visual Studio Team Suite 2008, and it is very handy for the SQL developers.
BUT Its Not Free...
|
|
|
|
|
SSC-Addicted
Group: General Forum Members
Last Login: Thursday, March 11, 2010 4:54 AM
Points: 431,
Visits: 1,340
|
|
I use a poor (simple?) man's solution that runs a sweep of all data base objects nightly, and captures a copy of anything that has been modified in a table.
Works fine for me. I miss multiple changes made during the day, but those are only failed test attempts that are not worth saving anyway. Other than that, I have a complete history of all versions.
|
|
|
|
|
SSC Journeyman
Group: General Forum Members
Last Login: Tuesday, August 25, 2009 12:25 PM
Points: 82,
Visits: 171
|
|
| You can try VS TeamSystem with this VPC http://www.microsoft.com/visualstudio/en-us/products/teamsystem/default.mspx. Has a web interface very simple. It's looks like Share Point.
|
|
|
|
|
Grasshopper
Group: General Forum Members
Last Login: Tuesday, September 29, 2009 8:36 AM
Points: 13,
Visits: 84
|
|
tony.sawyer (4/21/2009)
Hi John,
....
itamar has mentioned a tool I've never heard of before - I think we will be looking at that to see whether it does what we want - or at least does a better job than what we are managing with at the moment.
Tony
I'll be happy to hear what you think of it.
--------
SQL Data compare , Synchronize data from diffrent surces, and many other SQL tools.
|
|
|
|
