Is Documentation Dying?
The BOL for SQL Server 2005 has been interesting to read. On one hand there is a more comprehensive approach...
2006-03-24
1,513 reads
The BOL for SQL Server 2005 has been interesting to read. On one hand there is a more comprehensive approach...
2006-03-24
1,513 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
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