The Backup Myth (MP3)
Running backups is enough for disaster recovery, right? That's a myth that could get you into trouble. Steve Jones explains there's more that's needed.
Running backups is enough for disaster recovery, right? That's a myth that could get you into trouble. Steve Jones explains there's more that's needed.
Running backups is enough for disaster recovery, right? That's a myth that could get you into trouble. Steve Jones explains there's more that's needed.
Tony Davis offers his congratulations on a new MVP at SQLServerCentral.com and DatabaseWeekly.com.
Every profession has its share of myths about how it works. IT might have more than its share and Steve Jones comments on a few of them.
As a SQL Server DBA you should know that your code is stored in syscomments by default. While most DBAs use version control systems, there are times you might want to look through the code on the server for comparison purposes. Robert Cary brings us an article on how you can do this in 2000 and 2005.
Learn how to use an Analysis Services cube as a data source by using parameterized MDX queries, as well as how to localize label strings in a report, in SQL Server 2005.
SQL Server 2005 provides four methods of encryption. Part one of this article covers encryption and decryption by passphrase.
Life at college is good. It's a time in many people's lives that they'll never forget. Steve Jones asks if you'd want to go back to your adult roots.
The I/O system is important to the performance of SQL Server. When configuring a new server for SQL Server or when adding or modifying the disk configuration of an existing system, it is good practice to determine the capacity of the I/O subsystem prior to deploying SQL Server. This white paper discusses validating and determining the capacity of an I/O subsystem. A number of tools are available for performing this type of testing. This white paper focuses on the SQLIO.exe tool, but also compares all available tools. It also covers basic I/O configuration best practices for SQL Server 2005.
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