This editorial was originally published on July 31, 2014. It is being re-published as Steve is out of the office.
I was catching up on work recently, reading the third installment of The 5 Worst Days in a DBA's life, starring The DBA Team. Someone had asked me if I enjoyed having Paul Randal (b | t) of SQLskills join them team. The piece had been edited and published while I was gone, and I hadn't had a chance to immerse myself in the adventure. I was anxious too read how Paul helped save the day.
It was a fun read, but one quote in the piece struck me. "A job that runs long or doesn't run at all can sting just as bad as one that fails." That's a quote from my character showcasing a situation that few people actually think about. However jobs that don't run or don't finish are situations that DBAs should be monitoring for.
So many of us adopt a set-it-and-forget-it mentality with our jobs. We assume that things will work, or fail, as we set them up. However it's easy to forget that there are other states we might find ourselves or our systems in that can cause issues.
Monitoring is critical to any well run system, but monitoring needs to be set up well. If we require that certain jobs run, we need to not only check for success or failure, but if the job has actually run and completed. It's easy to accidentally disable the wrong job and not notice. It's also entirely possible that a job gets stuck and doesn't complete.
If you're not watching for those other states, you might find yourself in a situation where you don't have backups and your job is on the line. However you probably won't have The DBA Team to call on.
The industry standard for comparing and deploying SQL Server database schemas
Trusted by 71% of Fortune 100 companies, SQL Compare is the fastest way to compare changes, and create and deploy error-free scripts in minutes. Plus you can easily find and fix errors caused by database differences. Download your free trial
The performance increase columnstore indexes grant when reading data from the index is offset by the expensive process required to build the index. In this Stairway level, Hugo Kornelis walks you through the steps SQL Server takes when building (or rebuilding) a columnstore index. More »
Three SQL Server MVPs (Jonathan Kehayias, Ted Krueger and Gail Shaw) provide fascinating insight into the most common SQL Server problems, why they occur, and how they can be diagnosed using tools such as Performance Monitor, Dynamic Management Views and server-side tracing. The focus is on practical solutions for removing root causes of these problems, rather than "papering over the cracks". More »
By default, SQL Server does not encrypt data in a SQL Server database in an encrypted format. When SQL Server 2008 was introduced, Microsoft implemented Transparent Data Encryption (TDE). When TDE is enabled on a database SQL Server will encrypt the database as data is written to the disk. More »
By harnessing the concept of agility to a methodology that enables constant software innovation, DevOps allows organizations to respond dynamically to changing market conditions and rising customer expectations. More »
The SQL Server 2005 and SQL Server 2008 provide a new feature for encrypting data to protect it from... More »
Question of the Day
Today's Question (by Steve Jones):
I want to use the mathematical function cosine function in a Python script inside of SQL Server. I know that this function isn't in the base Python interpreter, but is in the math module. What do I run to get access to this function in my script?
Think you know the answer? Click here, and find out if you are right.
We keep track of your score to give you bragging rights against your peers.
This question is worth
1 point in this category: Python.
We'd love to give you credit for your own question and answer.
To submit a QOTD, simply log in to the
Design and configure SQL Server instances and databases in support of high-throughput applications that are mission-critical and provide consistent response times in the face of variations in user numbers and query volumes. Learn to configure SQL Server and design your databases to support a given instance and workload.
Pick up your copy of this great book today at Amazon today.
Yesterday's Question of the Day
(by Steve Jones):
I run this code on SQL Server 2016:
SET CONTEXT_INFO 55
I then want to get that data later in my application. I run this:
I don't get 55 back. Why not?
Answer: The data in CONTEXT_INFO() is binary, so I need to cast this back to numeric.
Context_info take binary data in and returns binary data. The result needs to be converted back to integer (or numeric) data.
Looking to sort two queries by Date, Time
LTRIM(RIGHT(CONVERT(varchar(6), .,100),7)) AS
--, FORMAT(., 'MM-dd-yyyy') AS
, CONVERT(varchar(10),REPLACE(CONVERT(varchar(10), .,101),'/','-')) AS
This newsletter was sent to you because you signed up at SQLServerCentral.com.
Feel free to forward this to any colleagues that you think might be interested.
If you have received this email from a colleague, you can register to receive it here.