Not Just an Upgrade
Choosing to upgrade isn't as simple as many of us would like. Steve has a few thoughts today on the decision to move to a new version of a database server.
2026-03-09
87 reads
Choosing to upgrade isn't as simple as many of us would like. Steve has a few thoughts today on the decision to move to a new version of a database server.
2026-03-09
87 reads
As a SQL Server DBA, the migration of SQL Server from an existing version to the latest version is a usual activity. In today’s cloud-oriented world, many organizations still prefer an on-prem environment; my organization is one of them. There are multiple reasons to keep your data on-prem, like having more privacy and control of the environment. Currently, our major project is to migrate our existing Microsoft SQL Server 2019 to SQL Server 2022. Recently, we completed the POC. Today, let’s discuss the steps of the SQL Server 2022 installation and migration of our databases.
2025-09-24
Steve has a few thoughts after the end of mainstream support for SQL Server 2019.
2025-03-26
1,385 reads
2024-09-09
399 reads
2024-08-26
387 reads
2024-08-12
556 reads
2024-07-10 (first published: 2024-07-08)
177 reads
2024-02-26
368 reads
Is there a reason to upgrade your SQL Server in place instead of building a new instance? Andy Warren has a few thoughts today on why this might be the right choice.
2023-12-20
5,963 reads
2023-10-13
395 reads
By Steve Jones
It’s Prime Day. A few of my recommendations, since I want to do some...
With Fabric Mirroring, Microsoft is promoting a nice and appealing story for operational reporting...
If you’ve been watching AI roll through the data community and thinking, “this seems...
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