Dead LINQ - Database Weekly (Nov 3, 2008)
Steve Jones comments on a few pieces of interesting SQL Server news this week, including Service Pack 3.
2008-11-03
337 reads
Steve Jones comments on a few pieces of interesting SQL Server news this week, including Service Pack 3.
2008-11-03
337 reads
2008-11-03
73 reads
2008-11-03
100 reads
2008-11-03
81 reads
2008-11-03
3,384 reads
I got up this morning, wanting to go through the forums, check on Database Weekly, etc. as a Sunday morning...
2008-11-02
574 reads
Things on the ranch inspire Steve Jones in the rest of his life. He's one you might not have thought about.
2008-11-02
76 reads
Things on the ranch inspire Steve Jones in the rest of his life. He's one you might not have thought about.
2008-11-02
67 reads
Things on the ranch inspire Steve Jones in the rest of his life. He's one you might not have thought about.
2008-11-02
70 reads
Steve Jones comments on a few pieces of interesting SQL Server news this week, including Service Pack 3.
2008-11-01
524 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