Using Mod to Generate Work Shifts

A short story on using the mod function to a shifting query.

Capacity Planning Using Performance Data

Erin Stellato discusses the types of performance data needed to help with capacity planning.

Byte Me: Christmas Contingency

Disconnecting SQL Server connections after query execution

One way to improve SQL Server performance is to use as few resources as possible. In this post Rahul Mehta demonstrates how you can do this by disconnecting queries post-execution with a simple change in SSMS.

What is Azure SQL Data Warehouse?

Azure SQL Data Warehouse is a cloud-based, scale-out database capable of processing massive volumes of data, both relational and non-relational. Built on our massively parallel processing (MPP) architecture, SQL Data Warehouse can handle your enterprise workload.

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.

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.

How to Capture Deleted Records

This article shows a few techniques that help in capturing deleted records.

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?