2006-04-05
1,383 reads
2006-04-05
1,383 reads
In writing for a tech book one of the things that happens is a copy editor looks over your work...
2006-04-04
1,446 reads
2006-04-04
1,208 reads
2006-04-03
1,188 reads
2006-03-31
1,260 reads
It is something you do rarely, but with SQL Server 2005 and ten services, there are more decisions to make. Steve Jones gives some advice on which service accounts to choose and some common problems with others.
2006-03-30
18,777 reads
2006-03-30
1,631 reads
2006-03-29
1,345 reads
2006-03-28
1,568 reads
2006-03-27
1,270 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...
By HeyMo0sh
In my experience, FinOps success has never been just about tools or dashboards. It...
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