Ever wonder all the reasons that we use databases instead of file systems? While we don’t think of it too much anymore, the first reason that databases came into existence was to remove redundancies.
Using a CURSOR is not normally the best way to process through a set of records. Yet when a seasoned programmer moves to writing TSQL for the first time they frequently look for ways to process a sets of records one row at a time. They do this because they are not used to thinking about processing records as a set. In order to process through a TSQL record set a row at a time you can use a cursor. A cursor is a record set that is defined with the DECLARE CURSOR statement. Cursors can be defined as either read-only or updatable. In this article I will introduce you to using cursors to do record level processing one row at a time.
Today Steve discusses code freezes, those times when you don't allow changes to be made by developers.
Learn about the SQL Server plan cache and how SQL Server caches query plans, and the potential of plan cache bloat which could impact performance.
This article shows how you can use two Cosmos DB dataets in Azure Data Factory and join them on a common column.
Guy Glantser is an Israeli SQL Server guru with a ton of great presentations on YouTube. I’ve had the privilege of hanging out with him in person a bunch of times over the year, and I’ll always get excited to do it again. He’s not just smart, but he’s friendly and funny as hell.
I recently came back from a trip to Las Vegas. I was privileged to be able to take part in the very first Fabric Community Conference. It was a great event, well attended. BUT... It was in Las Vegas. I am not a fan. First of all, Vegas is just far too noisy for me. […]
In this article, learn how to use the PowerShell DSC to patch your SQL Server instances.
By ChrisJenkins
Have you been thinking about migrating your reporting to Microsoft Fabric or Snowflake but...
The Joyful Craftsmen has become the new owner of Revolt BI. The merger creates...
By Steve Jones
It’s Prime Day. A few of my recommendations, since I want to do some...
Comments posted to this topic are about the item SQL Art, Part 4: Happy...
Comments posted to this topic are about the item Concurrency and Baseline Control: Level...
Comments posted to this topic are about the item Spending Time in the Office
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