2005-10-20
2,449 reads
2005-10-20
2,449 reads
2005-10-18
991 reads
2005-10-17
2,116 reads
Why is that? My Database Daily editorial for this week focuses on that and I thought it would be interesting...
2005-10-14
1,385 reads
2005-10-14
1,384 reads
The MARS guy. That's where Steve Jones and Andy Warren first met Christian Kleinerman, group program manager with the SQL Server engine team. Learn a little bit about Christian and his views on SQL Server.
2005-10-13
4,928 reads
We typically have great weather in Colorado where I live, but we do get
snow. And occassionally it causes issues. Like...
2005-10-12
1,521 reads
2005-10-12
1,719 reads
2005-10-11
1,585 reads
I know, I need some stuff posted about PASS and I'll get to it. My wife
was injured (she's ok) while...
2005-10-09
1,412 reads
By HeyMo0sh
In my experience, FinOps success has never been just about tools or dashboards. It...
By HeyMo0sh
As a DevOps person, I know that to make FinOps successful, you need more...
By HeyMo0sh
As someone who works in DevOps, I’m always focused on creating systems that are...
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