September 23, 2011 at 6:24 am
Hi Guys!
We have Integration server where all the Team members do the Testing of their Code. Its Ok with Code But unfortunately i am unable to track what is cooking on DB Side.
Its really pathetic for other if Application version is 2.0 while DB is 1.0 >> There must be coherance.
Kindly suggest some way to Track/Monitor such things.
PS: We are Using Tortoise SVN as version controlling tool. What if I let everyone Bound to not execute even a single statement unless you "commit" in TSVN with proper comments in Log messages. Is it possible?
Kindly provide some Open Source Solution.
Thanks in advance.
Waseem Shahzad Bukhari
September 23, 2011 at 8:15 am
Lets assume you are using SQL Server, I would start by securing your servers. That way you know only certain priviledged people can make changes. Introduce a release process with relevant sign off from business areas. Introduce some form of log of what scripts are run and when (even if it is just in excel to start with). You could look at SQL Server Auditing;
http://msdn.microsoft.com/en-us/library/cc280386.aspx
Or DDL Triggers;
http://msdn.microsoft.com/en-us/library/ms190989.aspx
Thanks
Chris
September 23, 2011 at 8:54 am
Chris is correct. First you need security and stopgap controls. After that, there are lots of ways to track things. Here is a series I wrote on what worked for me: http://www.sqlservercentral.com/articles/System+Development+Life+Cycle/vcspart1/523/
You could also use a tool like Red Gate's SQL Compare to track schema changes and then decide which ones will migrate for the next release. However I do also make sure that I'm branching the code that is in a release in SVN (or any VCS) so that I can track back what was released.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply