The benefits and drawbacks of GUIDs as primary keys are generally known. Despite the drawbacks, some people use them to fulfill specific business requirements (the IDs are unique across multiple servers).
Over the last year we've taken a look at a number of people influential in the SQL Server community. This time Steve Jones spent a little time interviewing MVP and regular blogger Simon Sabin.
This article provides a guide for physical storage design and gives recommendations and trade-offs for physical hardware design and file architecture.
SQL Server guru Andy Warren has been working with all aspects of SQL Server for many years and is slowly upgrading his skills to SQL Server 2005. Here he takes a look at SMO basics, which is the replacement for DMO.
Use Linked Reports to provide multiple "versions" of a single source report, as a mechanism for restricting consumer groups to their respective data in accordance with a "need to know."
Have you ever used XP_RESULTSET in SQL Server? If you're like most DBAs, this procedure is rarely used and can be a little complicated to setup. New author J. T. Shyman brings us a look at just how useful this command can be in executing a command on every database.
If I had a penny for every person who said "usability is just common sense", I'd have a pretty reasonable stack of pennies – maybe 30 or so. Clearly I'm not going to be able to retire on this, but at least it demonstrates that many people have misconceptions about how usable interfaces are designed.
SQL Server 2005 has a new administrative tool called Management Studio, with many enhancements and changes from Enterprise Manager. But it's not just for SQL Server 2005 as new author Rob Farley shows us how to use this tool with SQL Server 2000.
This white paper describes how SQL Server 2005 uses tempdb. Many improvements in SQL Server 2005 optimize tempdb usage and make it easier to manage and to troubleshoot. A case study that uses a workload similar to TPC Benchmark H (TPC-H) shows new ways to manage and troubleshoot tempdb resources. This paper also includes items to consider when upgrading to SQL Server 2005 and configuring tempdb
Attaching and detaching databases is old hat these days right? Do you know how to reattach a database that has more than 16 files? Or do you know what happens if you try to reattach a database that had two log files but one is missing/deleted? And even if you know the answer to that - do you know how to fix it without restoring from backup? Maybe it's not ALL old hat just yet!
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