The Good Job
Today Steve Jones talks about jobs, and how life is too short to stick with a crappy job.
Today Steve Jones talks about jobs, and how life is too short to stick with a crappy job.
In SQL Server, replication is a widely adopted technology for the purpose of real-time data replication between SQL servers. It serves the purpose of keeping data consistent between multiple end points. So the last thing we want to hear from clients is that data is no longer in synch, and as DBA, we don't want to be the last person to realize replication is out of order or broken. Here are some steps you can take to monitor SQL Server replication.
SQLInspire, from SQL People, is coming to New York City on Nov. 12, 2011. Win a free admission from Red Gate software to this great event.
If you are looking to gain some BI experience or tackle a project that might help your company, Steve Jones suggests you consider doing something for HR.
This article covers the use of the TOP clause to select data from a table based on the TOP n columns in a table.
How can I use PowerShell to do a Transaction Log backup for SQL Server databases? In this tip we look at an alternative way of creating transaction log backups using a PowerShell script.
In this guest editorial, Glenn Berry argues that, when designing your servers, you need to budget for processing power as your primary concern.
What's the cost of those architectural decisions that you make? It can be substantial if they aren't good ones, but is that a problem? Steve Jones talks a little about the implications
Learn how you can update multiple servers in a single bound with this technique from Kimberly Killian.
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