The Last SQL Server Service Pack
SQL Server 2016 SP3, the last service pack ever is out. Steve comments on how the world of software patches has changed.
2021-10-08
528 reads
SQL Server 2016 SP3, the last service pack ever is out. Steve comments on how the world of software patches has changed.
2021-10-08
528 reads
A failed SQL Server Service Pack upgrade is fixed with a trace flag.
2020-07-27
5,604 reads
Learn a few possible solutions to a frustrating issue when you attempt to patch a SQL Server installation.
2018-12-07 (first published: 2016-01-11)
9,144 reads
Microsoft has continued to release Cumulative Updates, with each one specifying that customers should wait for the next service pack if they don't experience an issue. However, no Service Packs have been released for some time. Let Microsoft know we want Service Packs.
2014-03-06 (first published: 2014-02-28)
4,471 reads
2010-09-30
5,572 reads
2010-01-04 (first published: 2009-12-30)
1,695 reads
2010-01-15 (first published: 2009-12-28)
87 reads
2008-04-24 (first published: 2008-02-28)
1,851 reads
Service Pack 3 for SQL Server 2000 is huge. There are significant changes in it and they apply to all three products: the core SQL Server, MSDE, and Analysis Services. Because there are so many changes, this first article in the series will only focus on the security changes.
2007-09-22 (first published: 2003-06-05)
30,099 reads
There may be more ways than you realize to determine the version and service pack of SQL Server. This quick article by Dinesh Priyankara will show you 3 of those methods.
2003-02-28
22,084 reads
Here’s a way to centralize management, rotate secrets conveniently without downtime, automate synchronization and...
This may or may not be helpful in the long term, but since I’m...
By Steve Jones
“I’m sick of hearing about Red Gate.” The first article in the book has...
Comments posted to this topic are about the item Dynamic T-SQL Script Parameterization Using...
I have read that the collation at the instance level cannot be changed. I...
hi our on prem STD implementation of SSAS currently occupies about 3.6 gig of...
In SQL Server 2022, I run this code:
CREATE SEQUENCE myseqtest START WITH 1 INCREMENT BY 1; GO CREATE TABLE NewMonthSales (SaleID INT , SecondID int , saleyear INT , salemonth TINYINT , currSales NUMERIC(10, 2)); GO INSERT dbo.NewMonthSales (SaleID, SecondID, saleyear, salemonth, currSales) SELECT NEXT VALUE FOR myseqtest , NEXT VALUE FOR myseqtest , ms.saleyear , ms.salemonth , ms.currMonthSales FROM dbo.MonthSales AS ms; GO SELECT * FROM dbo.NewMonthSales AS nmsAssume the dbo.MonthSales table exists. If I run this, what happens? See possible answers