My Thoughts on the Intel Sandy Bridge Chipset Recall
I awoke this morning to see a number of stories breaking about the Intel Sandy Bridge H67/P67 Chipset Recall. I...
2011-02-03
1,661 reads
I awoke this morning to see a number of stories breaking about the Intel Sandy Bridge H67/P67 Chipset Recall. I...
2011-02-03
1,661 reads
Here is another example CPU throttling from someone who had a server running with the default “Balanced” Power Plan in...
2011-01-24
2,725 reads
One of the most important things to measure, monitor, and “get right” for good overall SQL Server OLTP performance is...
2011-01-11
2,969 reads
There are two primary relational workload types that SQL Server commonly has to deal with, the first being Online Transaction...
2011-01-03
2,280 reads
Here is a small selection of useful tools for getting some specific hardware information from any Windows based system you...
2010-11-17
4,097 reads
Apparently, when I posted this a few days ago, the Windows Live Writer plug-in that I used mangled the T-SQL...
2010-11-11
2,035 reads
Unlike fine wine, database statistics do not improve with age. I recently helped out with a client who was having...
2010-09-02
3,375 reads
I had a question today about why it was “bad” to use a UniqueIdentifier as the data type for a...
2010-03-30
3,661 reads
Data compression is an Enterprise Edition only feature that was added in SQL Server 2008. It allows you to use...
2010-02-26
2,250 reads
If so why? Honestly, I am curious why people may still be running 32-bit versions of SQL Server 2005, 2008,...
2010-02-03
3,616 reads
By HeyMo0sh
As someone who works in DevOps, I’m always focused on creating systems that are...
By Brian Kelley
I am guilty as charged. The quote was in reference to how people argue...
By Steve Jones
Learn how to tie a bowline knot. Practice in the dark. With one hand....
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