NoSQL for the MSSQL Soul
The buzz around NoSQL solutions has reached stratospheric heights. This buzz has led many Microsoft SQL Server development shops to start looking at how and where a NoSQL solution can fit into their business.
Filtered Indexes - Simple Partitioning without Enterprise Edition?
This article discusses using Filtered Indexes as a simple partitioning strategy in SQL Server Standard Edition
Fix the Little Things
There are any number of small, annoying or tedious things in SQL Server and Steve Jones makes a case for getting them fixed. Today's editorial was originally published on Nov 11, 2008. It is being re-run as Steve is out of town.
Resource Governor in SQL Server 2012
SQL Server 2012 delivers enhancements to the Resource Governor that reflect a growing need for centrally managed database services to provide multitenancy to customers who require isolated workloads. This document describes the enhancements and why they were added. It includes a self-contained walk through that you can try in order to gain familiarity with the new features.
Life is Like a Manure Spreader
Things on the ranch inspire Steve Jones in the rest of his life. He's one you might not have thought about. Today's editorial was originally published on Nov 3, 2008. It is being re-run as Steve is out of town.
SQL Server Analysis Services-Lead, Lag, OpeningPeriod, ClosingPeriod Time Related Functions
Working with SSAS time related accounting functions can be tricky. SQL Server 2012 now offers Lag and Lead functions. Are these functions available in SSAS? What other related functions are available?
An in-depth look at change detection in SQL Server - Part 02
Auditing, conflict resolution, tamper & concurrency protection are some of the most common requirements for any enterprise system – this 2-part series presents an in-depth look at the various change detection mechanisms available within SQL Server.
Are Triggers a "Legacy" Feature?
It is late evening. Something is wrong with a database. You narrow down the possibilities, getting more frustrated and puzzled. Stay calm. Check the inputs systematically. No! The data going into that table is right, but when you then read it in the table, it's wrong. Why did I stop believing in the supernatural? Then it hits you. Every time it comes as a surprise. They're using triggers. (This editorial was originally published on Nov 10, 2008)
SSIS for Azure and Hybrid Data Movement
SQL Server Integration Services (SSIS) can be used effectively as a tool for moving data to and from Windows Azure SQL Database, as part of the total extract, transform, and load (ETL) solution and as part of the data movement solution. SSIS can be used effectively to move data between sources and destinations in the cloud, and in a hybrid scenario between the cloud and on-premise. This paper outlines best practices for using SSIS for cloud sources and destinations and for project planning for SSIS projects to be used with Azure or hybrid data moves, and gives an example of maximizing performance on a hybrid move by scaling out the data movement.
Big Data: Cash Cow or Horsemeat?
The big data revolution seems to have failed to materialise, and for good reason - it's really difficult.
Blogs
How to Find Expensive Queries in Amazon Redshift
Slow-running queries can degrade your Redshift cluster’s performance and lead to increased costs. Identifying...
The Notification Trap: How Input Fatigue Is Killing Deep Work in Tech
By gbargsley
If you've been here before, you know this blog is usually about SQL Server,...
Designing a Storage Load Test for SQL Server
I’ve been doing storage load tests for SQL Server for a long time, both...
Forums
Make your moments memorable with Fildena 200mg
Make your moments memorable with Fildena 200mg, a high-strength option designed to support men...
How Long is a Long I/O?
Comments posted to this topic are about the item How Long is a Long...
T-SQL Trigonometric Functions in SQL Server
Comments posted to this topic are about the item T-SQL Trigonometric Functions in SQL...
Question of the Day
How Long is a Long I/O?
In SQL Server 2025, a long I/O is recorded in the error log with message 833. How long much an I/O request be outstanding before this message is written to the log?
See possible answers