| Author |
 Topic  |
|
|
lubichjd
2 Posts |
 Posted - 12/15/2008 : 13:36:48
|
We have created an automated process which auotmatically builds our Check In database from VSS by calling the Change Manager from a command line. It executes every 5 minutes and emails our developement staff if it finds that anything has changed in our entire VSS project. It has been in place for a couple years and has worked wonderfully. Within 5 minutes of checking in a change everyone in our group is notified of what the change is and since DB Ghost runs all of the scripts in our entire repository when it create a temp DB, it ensure that there are no interdependent changes that are missed by the developer when they check their changes in.
Our script looks for the following keywords in the results.txt file that DB Ghost generates.
'...Added',
'...Modified',
'...Error',
'...Cannot insert the value NULL',
'...Dropped',
'...Inserted',
'...Updated'
2/11/2008 5:27:05 PM...Modified stored procedure dbo.opUpdatePackage
12/12/2008 1:50:59 PM...Modified column dbo.QuoteLines.GenerateSystemNumber
12/12/2008 1:51:00 PM...Modified column dbo.ImportConfigurationStyles.GenerateSystemNumber
12/12/2008 1:51:08 PM...Modified stored procedure dbo.opCreateOrderBuckets
12/12/2008 4:26:59 PM...Modified stored procedure dbo.opValidatePlacementInformation
12/12/2008 4:26:59 PM...Modified stored procedure dbo.opGetUpdatedPackage
12/12/2008 4:26:59 PM...Modified stored procedure dbo.opGetStyleToPackage
12/12/2008 4:27:00 PM...Modified stored procedure dbo.opGetQuoteLine
12/15/2008 5:51:32 PM...Modified stored procedure dbo.opCreateOrderBuckets
However the latest version of DB Ghost has changed some of the keyword values that we parse from the results file. For example if you modify a stored procedure we used to find the word 'Modified', however we now need to look for 'Altered'. Has anyone noticied that these keywords have changed??? Is there somewhere that these keywords are documented so we can make sure we include all of the possible values that our scripts should report on???
OLD VERSION WHEN A SPROC IS CHANGED
12/15/2008 5:51:32 PM...Modified stored procedure dbo.opCreateOrderBuckets
NEW VERSION WHEN A SPROC IS CHANGED
12/15/2008 1:25:31 PM...Altered stored procedure [dbo].[mfgMatchData]
|
|
|
Mark Baekdal
86 Posts |
Posted - 12/15/2008 : 13:43:21
|
ah yes, I guess we don't always realize how the text file is being used. I didn't imagine it used in this way. The new key words you should look for are created, altered, dropped, renamed for objects and inserted, deleted, and updated for data which is more in line with the SQL being used for the action. My apologies for your inconvienience.
regards,
Mark Baekdal
http://www.dbghost.com
http://www.innovartis.co.uk
Take control of your SQL Server code.
|
 |
|
|
lubichjd
2 Posts |
Posted - 12/15/2008 : 14:02:06
|
Mark,
Thanks for your reply. We'll change our scripts to look for those keywords. We also pickup the Error keywords and send out a slightly different email to our development staff when we pick them up. Also, the results file allows us to keep a great log of when changed are introduced into our environments. We have a text file shows every changed all the way back to 2006.
I can't imagine anyone not automating the DB Ghost build process that has a team of DB developers. DB Ghost's integration with VSS along with SSMS's integration with Solution\Project files in VSS creates the very best change management product I've ever seen for SQL Server. DB Ghost provides such a unique and valuable solution to the DB configuration management process that I convince every development team I know to use it. If there were a way to make commission off of soliciting this product I could probably quit my day job and setup development teams with our automated build process.
I truely hope that Innovartis realizes the full potential of the SSMS integration with DB Ghost. I really think they should work harder at using this as a selling point. With a few simple modifications to the Scripter the Solution\Project hierarchy could be auto-generated and simplify all the work of deploying an automated configuration maanagement / build solution.
Regards,
Jeremy
|
|
|
|
Mark Baekdal
86 Posts |
|
|
Mark Baekdal
86 Posts |
Posted - 12/16/2008 : 03:14:44
|
If you have any ideas/suggestions then we'd love to hear them. My idea at present is to expand the API giving access to the errors, warnings and information collections. From here we could also add collections that deal with the keywords - like created, inserted etc which could be drilled into to report on. Another useful aggregation could be by object type where the object type is the key to a collection of errors, warnings and information. What I am wondering about is what to introduce to the command line to give people what they want. My experience has been that mainly people are interested in the errors and warnings and if anything has changed. Perhaps we could introduce an option to the log along the lines of - only write out errors, warnings and information to show if things have/require change.
regards,
Mark Baekdal
http://www.dbghost.com
http://www.innovartis.co.uk
Take control of your SQL Server code.
|
|
|
| |
Topic |
|
|
|
Automated Reporting of Build Results
Posted - 12/15/2008 : 15:11:38
