I thought my database was collation agnostic
My struggles with a customer's database that used a different collation sequence. The easy way is never the right way, or is it?
2018-06-08 (first published: 2016-01-14)
4,552 reads
My struggles with a customer's database that used a different collation sequence. The easy way is never the right way, or is it?
2018-06-08 (first published: 2016-01-14)
4,552 reads
After having seen many systems that use GUIDs as the primary key for every table, it is time to say enough is enough.
2014-12-18
9,968 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