CPU Spikes Caused by Periodic Scheduled Jobs
This article shows how to reduce the periodic spikes in the CPU that are caused by the periodic-executing jobs. There is a good reason to make some changes for dismissing them.
Test Coverage
We don't test software well enough. Obviously we don't write high enough quality software, but testing should catch more issues. Steve Jones talks about how you can perform better T-SQL testing.
How to Fix Ten SSDT Deployment Snags, With or Without ReadyRoll
Even a database development framework like Sql Server Data Tools (SSDT) doesn't get it right all the time, and there are ten deployment 'gotchas' in particular that can cause some head-scratching amongst developers to get right. From his unique perspective of creating a tool to make such deployments in SSDT less stressful, Dan Nolan discusses each pitfall and how to avoid it, whether you have ReadyRoll or not.
Better Coding, More Savings
The way we write code impacts our users, but it can also impact our wallet, especially in cloud computing. Steve Jones wonders how many people bother to profile and test their code.
How to Capture Deleted Records
This article shows a few techniques that help in capturing deleted records.
The Toolchain for the Job?
Phil Factor ponders the use of toolchains in automation, and wonders if there might not be a better way.
Managing multiple database versions
Sometimes, it's necessary to have different versions of a database running in production. But how do you establish a single source of truth in source control? Alex Yates from DLM Consultants shows how to use object filters in SQL Compare to build multiple database versions from the same source.
Which Indexes are not Used?
During the development cycle, indexes will be placed on SQL Server tables to speed up performance when searching for records. Lots of thought probably has gone into creating just the right mix of indexes based on how developers think customers will use the system. But how do you tell if all the indexes are being used once your database has been implemented into production?
A Fun Distraction
With the holiday season here, Steve Jones wonders what you'll do for fun away from work.
Managing Log Files Sizes the Easy Way
Learn an easy, rough, and ready way to manage log files in this piece.
Blogs
From Planning to Practice: Setting Up Your FinOps Framework
By HeyMo0sh
As someone who works in DevOps, I’m always focused on creating systems that are...
“We love to debate minutiae”
By Brian Kelley
I am guilty as charged. The quote was in reference to how people argue...
Advice I Like: Knots
By Steve Jones
Learn how to tie a bowline knot. Practice in the dark. With one hand....
Forums
Restoring On Top II
Comments posted to this topic are about the item Restoring On Top II
SQL Art 2: St Patrick’s Day in SSMS (Shamrock + Pint + Pixel Text)
Comments posted to this topic are about the item SQL Art 2: St Patrick’s...
Breaking Down Your Work
Comments posted to this topic are about the item Breaking Down Your Work
Question of the Day
Restoring On Top II
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