Query-generated Column Expressions
A technique from Bill Nicolich that allows you to target columns by data type for the same custom expression and easily build complex queries.
The Death March
Are you working too hard? Is it worth it? Steve Jones says that it is not and that you should push back.
Showplan Operator of the Week – BookMark/Key Lookup
Fabiano continues in his mission to describe the major Showplan Operators used by SQL Server's Query Optimiser. This week he meets a star, the Key Lookup, a stalwart performer, but most famous for its role in ill-performing queries where an index does not 'cover' the data required to execute the query. If you understand why, and in what circumstances, key lookups are slow, it helps greatly with optimising query performance.
A Smarter Planet
IBM has this tagline about a smarter planet and has a great video about the Internet of Things. Steve Jones looks at some of the issues we might have in actually using all this data.
Clustered Indexes? Sedimentary, my dear Watson
There is much sound advice suggesting that every table should have a clustered index, and that narrow, integer, ever-increasing columns, such as afforded by an IDENTITY column are the best choice. But is the sedimentary approach really the natural order of the day?
Optimising Server-Side Paging - Part II
The second part of this series compares four methods of obtaining the total number of rows in a paged data set.
Analyzing I/O Characteristics and Sizing Storage Systems for SQL Server Database Applications
Understanding how to analyze the characteristics of I/O patterns in the Microsoft® SQL Server® data management software and how they relate to a physical storage configuration is useful in determining deployment requirements for any given workload. A well-performing I/O subsystem is a critical component of any SQL Server application. I/O subsystems should be sized in the same manner as other hardware components such as memory and CPU. As workloads increase it is common to increase the number of CPUs and increase the amount of memory. Increasing disk resources is often necessary to achieve the right performance, even if there is already enough capacity to hold the data.
Where a Rose is not a rose…
Just because mistakes have become entrenched in the computer languages that we use doesn't mean we have to tolerate them
The Rise of NoSQL Databases
The NoSQL concept has been attracting a lot of attention in recent years, primarily due to big-name production implementations.
Does the Job Matter To You?
How important is your job to you? Today's guest editorial from Andy Warren asks the question of the professionals out there, some of whom do great work, but don't care about their jobs.
Blogs
Prime Day Recommendations
By Steve Jones
It’s Prime Day. A few of my recommendations, since I want to do some...
Fabric for Operational Reporting & SQL Endpoint Trap
With Fabric Mirroring, Microsoft is promoting a nice and appealing story for operational reporting...
Crawl, Walk, Run with Agentic Development of Power BI Assets
If you’ve been watching AI roll through the data community and thinking, “this seems...
Forums
SQL Art, Part 4: Happy 4th of July — A British DBA's Guide to Celebrating a War We Don't Talk About
Comments posted to this topic are about the item SQL Art, Part 4: Happy...
Concurrency and Baseline Control: Level 5 of the Stairway to Reliable Database Deployments
Comments posted to this topic are about the item Concurrency and Baseline Control: Level...
Spending Time in the Office
Comments posted to this topic are about the item Spending Time in the Office
Question of the Day
Multiple Values Inserted
I have this code on SQL Server 2022. What happens when it runs all at once?
DROP TABLE IF EXISTS dbo.Commission GO CREATE TABLE dbo.Commission (id INT NOT NULL IDENTITY(1,1) CONSTRAINT CommissionPK PRIMARY KEY , salesperson VARCHAR(20) , commission VARCHAR(20) ) GO INSERT dbo.Commission ( salesperson, commission) VALUES ( 'Brian', 12 ), ( 'Brian', 'None' ) GOSee possible answers