The final installment in Darren Fuller's series on change management in SQL Server. If you haven't read the others, be sure to go through them before reading this one to learn how automating your version control in SQL Server is needed for any development shop.
2004-08-18
7,328 reads
Part 3 of Darren Fuller's series on automating change management for SQL Server. A must read if you perform development and need a system to ensure that all changes are tracked.
2004-08-11
9,724 reads
The second part of the series by Darren Fuller on SQL Server change management, version control, and ways that you can automate this approach. If you do any type of SQL Server development, having a version control system is key to ensuring stability and keeping to your deadlines. Whether you agree with this approach or not, it's good information to have.
2004-08-04
10,103 reads
SQL Server change management is tough. The tools don't integrate with version control systems, there isn't good administrative controls to enforce control, and often you need to buy a third party tool to make this work. New Author Darren Fuller takes a look at the various ways in which you can implement version control in SQL Server. This is part one of a four part series on version control in SQL Server.
2004-07-28
13,719 reads
By Steve Jones
I hosted this month, but I decided to put my own entry in as...
By Chris Yates
I get asked a lot about why or how I began working with databases...
By Steve Jones
Earlier this year I visited a customer that was using the Redgate Monitor webhook...
Comments posted to this topic are about the item Implementing PostgreSQL with Python for...
Comments posted to this topic are about the item Identify a Slipstream Installation
Comments posted to this topic are about the item Internal Staff Growth, which is...
I get a new SQL Server instance from my build team. How can I tell if the instance was installed using a slipstream installation later?
See possible answers