2006-05-19
1,171 reads
2006-05-19
1,171 reads
2006-05-18
1,380 reads
2006-05-17
1,346 reads
2006-05-16
1,537 reads
The list server here at SQLServerCentral.com has a few quirks, one of which is that it doesn't run as a...
2006-05-15
1,426 reads
2006-05-15
1,535 reads
It's funny, but most articles in magazines get lost on my desk. I get quite a few subscriptions and rarely...
2006-05-15
1,440 reads
An interesting post on Database Apprenticeships. I think this is probably something we need in software development more than as...
2006-05-12
1,428 reads
2006-05-12
1,659 reads
2006-05-11
1,369 reads
By Steve Jones
I come to Heathrow often. Today is likely somewhere close to 60 trips to...
By Brian Kelley
If your organization is spending money, then meaningful results are a must. Pen testing...
I’m starting a webinar series about SQL Server indexing with the fine folks of...
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