2011-05-04
2,687 reads
2011-05-04
2,687 reads
2011-04-27
3,103 reads
2011-04-20
2,449 reads
2010-09-24
3,853 reads
2010-02-17
3,579 reads
2009-10-13
3,029 reads
Part two of his series on table schema changes, this article examines those changes that affect the actual data. Read this great article from Alok Dwivedi.
2009-08-05
5,182 reads
What happens behind the scenes when you alter a table schema? New author Alok Dwivedi dives deep into SQL Server to show us how things are affected.
2009-08-03
7,971 reads
2009-04-07
3,332 reads
2009-02-24
4,133 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