2007-06-14
1,274 reads
2007-06-14
1,274 reads
2007-06-13
1,257 reads
2007-06-12
1,281 reads
2007-06-11
1,419 reads
2007-06-08
1,362 reads
2007-06-07
1,309 reads
The database manages itself. Not totally, but close to it. It was an
analogy made by Dan Jones with cars. Auto...
2007-06-06
1,350 reads
Last night I went out with Tony Davis of Simple Talk and Alan White, a
longtime author for both here and...
2007-06-06
1,391 reads
It's a similar theme, off by default if it makes sense, minimize surface area.
Recommendations: for new installs, leave stuff off...
2007-06-06
1,470 reads
2007-06-06
1,365 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