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
84 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
84 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,328 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
364 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,901 reads
2023-10-13
395 reads
By James Serra
Microsoft Purview can be the best data governance tool in the world, but it...
I’ve been working on a project that combines two things I spend a lot...
Running AI and data pipelines on the edge instead of the cloud has gone...
Unfortunately I'm using SSMS 22. It didn't come with maintenance plans by default. I...
Comments posted to this topic are about the item Secure Cached Plans
Comments posted to this topic are about the item Complex Data Processing with dbt...
The DMV, sys.dm_exec_cached_plans, contains rows for each cached plan on an instance. In Azure SQL Database, not every used has rights to every database, as there does exist an instance behind each database. How is security handled for this DMV in Azure?
See possible answers