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
593 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
593 reads
A failed SQL Server Service Pack upgrade is fixed with a trace flag.
2020-07-27
5,923 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,724 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,713 reads
2010-01-15 (first published: 2009-12-28)
106 reads
2008-04-24 (first published: 2008-02-28)
1,886 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.
2005-12-09 (first published: 2003-06-05)
30,169 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,234 reads
By Steve Jones
I was experimenting with CHOOSE() recently after I was asked a question. In a...
By DesertDBA
I did not expect 27 responses to my T-SQL Tuesday #204 invitation, but it...
Should you adopt an off-the-shelf AI tool, partner with a specialist, build in-house, or...
Has anyone ever seen this before? I have sysadmin permission on a server. I...
Comments posted to this topic are about the item Switching Schema II
Comments posted to this topic are about the item A Practical Approach to Automating...
I run this query:
SELECT s.name AS schemaname , o.name AS objectname FROM sys.objects o INNER JOIN sys.schemas s ON s.schema_id = o.schema_id WHERE o.name = 'Beer'I get two rows back for the objects, named dbo.beer and etl.beer. Both the tables have identical schemas and are not partitioned. There are 25 rows in dbo.beer and 0 rows in etl.beer. I run this code:
ALTER TABLE dbo.beer switch TO etl.beerWhat happens? See possible answers