2004-05-26
1,826 reads
2004-05-26
1,826 reads
2004-05-25
2,013 reads
2004-05-24
2,822 reads
2004-05-19
1,778 reads
2004-05-18
2,088 reads
Do you have to refresh a test or QA server from the production system? Do you have a good process or is it a spur of the moment, let's get it done thing? Here's a look at Steve Jones' process, which was used weekly for well over a year.
2004-05-17
7,766 reads
2004-05-17
1,828 reads
2004-05-14
1,888 reads
2004-05-13
1,661 reads
2004-05-12
1,452 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