2005-11-02
1,445 reads
2005-11-02
1,445 reads
2005-10-31
2,127 reads
I wrote the editorial today about this, but SQL Server 2005 RTM'd yesterday!!!
If you an on MSDN Subscriber, you can...
2005-10-28
1,389 reads
2005-10-28
2,986 reads
2005-10-26
1,993 reads
The fourth part of Steve Jones series looking at employee retention. In this article, he examines a few techniques that can help the employee ensure their own retention.
2005-10-25
12,683 reads
2005-10-25
1,309 reads
2005-10-24
1,202 reads
2005-10-21
1,320 reads
My editorial
this past week had to do with a great uproar on the interviewing piece
that ran Monday. I felt I...
2005-10-20
1,443 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