2006-03-24
1,193 reads
2006-03-24
1,193 reads
2006-03-23
1,309 reads
2006-03-22
1,960 reads
2006-03-21
1,892 reads
2006-03-20
1,220 reads
2006-03-17
3,989 reads
Microsoft had their Blue Hat security conference recently, inviting hackers to take their shots at the Microsoft products. Mostly security...
2006-03-16
1,556 reads
2006-03-16
1,288 reads
2006-03-15
2,097 reads
Are you thinking about consolidating your SQL Servers on to fewer machines? It is an interesting idea and one that is definitely more possible with SQL Server 2005 and 64-bit servers. Steve Jones takes a look at some of the pros and cons of moving to fewer servers.
2006-03-15
7,488 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