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,337 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,739 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,104 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,730 reads
By HeyMo0sh
As someone who works in DevOps, I’m always focused on creating systems that are...
By Brian Kelley
I am guilty as charged. The quote was in reference to how people argue...
By Steve Jones
Learn how to tie a bowline knot. Practice in the dark. With one hand....
Comments posted to this topic are about the item Restoring On Top II
Comments posted to this topic are about the item SQL Art 2: St Patrick’s...
Comments posted to this topic are about the item Breaking Down Your Work
I have a database, DNRTest, that has a number of tables and other objects in it. The other day, I was trying to mock up a test and ran this code on the same server:
-- run yesterday CREATE DATABASE DNRTest2 GO USE DNRTest2 GO CREATE TABLE NewTable (id INT) GOToday, I realize that I need a copy of DNRTest for another mockup, and I run this:
-- run today USE Master BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak' GO RESTORE DATABASE DNRTest2 FROM DISK = 'dnrtest.bak' WITH REPLACEWhat happens? See possible answers