Queueing Theory
There has been tons of work over the last few decades on queueing theory, mainly in regard to operating systems...
2007-08-11
1,675 reads
There has been tons of work over the last few decades on queueing theory, mainly in regard to operating systems...
2007-08-11
1,675 reads
2007-08-10
1,636 reads
I got a note from someone at Red Gate about disengagement with the newsletter and site. Actually it was my...
2007-08-09
1,410 reads
2007-08-09
1,638 reads
It's not directly SQL Server, but it does prevent me from working with SQL Server 🙂
So I'm in Virginia this...
2007-08-08
2,899 reads
2007-08-08
1,603 reads
Maybe not. This is a great post and cartoon from David Reed (a friend) mentioning me.
We've had some good arguements...
2007-08-07
1,587 reads
An interesting debate from one of my editorials on risk. Some great points raised by everyone, but I still think...
2007-08-07
602 reads
2007-08-07
1,690 reads
2007-08-06
1,703 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