2023-09-25
468 reads
2023-09-25
468 reads
Do you actively choose which compatibility level makes sense for your SQL Server databases? Or do you just take the defaults? Steve has a few thoughts today on actively managing your system.
2023-06-14
1,683 reads
The database compatibility level ought to provide some protection from database upgrade changes, but do you believe that?
2020-09-21
329 reads
2015-10-19
1,332 reads
Changes the database compatibility level of all databases to the given level.
2013-01-31 (first published: 2013-01-07)
928 reads
By Steve Jones
In a previous post, I deployed a model to a database using SQL Compare...
By SQLPals
Reality (And Limits) of Instant File Initialization for Transaction Logs in SQL Server 2022 ...
By Steve Jones
Last week I spent a few days in Cambridge, UK for the Redgate Company...
Comments posted to this topic are about the item Adding and Dropping Columns II
Comments posted to this topic are about the item Leveraging DuckDB for OLAP Workloads:...
Comments posted to this topic are about the item More Documentation is Needed
I have this table in my SQL Server 2022 database:
CREATE TABLE [dbo].[CityList] ( [CityNameID] [int] NOT NULL IDENTITY(1, 1), [CityName] [varchar] (30) , [Country2] [char] (3), [stateprovince2] [char] (2), [Country] [char] (3), [stateprovince] [char] ) ON [PRIMARY] GOI decide to drop the stateprovince2 and country2 columns. What code should I use? See possible answers