2019-01-18
678 reads
Collation
2018-06-26
874 reads
2018-01-18
827 reads
Questions About SQL Server Collations You Were Too Shy to Ask
Of course we all like our colleagues to think that we know everything there is to know about SQL Server Collations. However, the truth is that it is a rather complicated topic to fully understand and the cost of getting collation wrong can be great. If only one could ask certain questions on forums or at conferences without blushing. Help is at hand, because Robert Sheldon once again makes the complicated seem simple by answering those questions that you were too shy to ask.
2017-06-15
3,969 reads
Changing SQL Server Collation After Installation
In some scenarios we can find different SQL Server collations between the server instance and its databases. Douglas P. Castilho explains a simple way to correct the collations in a few steps.
2017-04-11
3,262 reads
How to generate T-SQL scripts in SQL Server Management Studio with the collation settings
SQL Server collation is an important setting when creating database objects. One of the best ways to ensure that collation issues do not happen is to ensure that the collation settings are properly specified in the script that generates the database objects - Siddharth Mehta demonstrates how to do this.
2016-10-07
4,085 reads
Deep Dive into Changing Database Collation
Changing Database Collation Through Primary keys, Foreign Keys, Default and Check Constraints and more.
2016-03-07
4,128 reads
2014-11-11 (first published: 2014-07-25)
2,607 reads
How column COLLATION can affect SQL Server query performance
Most DBAs, myself included, install SQL Server with the default server collation SQL_Latin1_General_CP1_CI_AS and all of our table columns get created using this default setting. This tip will look at the performance impacts of querying data with this setting as it compares to querying columns with the collation set to SQL_Latin1_General_CP1_CS_AS.
2014-05-06
4,752 reads
2014-01-17
1,934 reads
Blogs
Advice I Like: Fear and Imagination
By Steve Jones
Fear is fueled by a lack of imagination. The antidote to fear is not...
Cloud Data Driven User Group 2025 – Slides & Scripts
The slidedeck and the SQL scripts for the session Indexing for Dummies can be...
Leading Through Change: Guiding Teams in Times of Uncertainty
By Chris Yates
Change is not a disruption in technology; it is the rhythm. New frameworks appear,...
Forums
Building AI Governance and Policies- First Steps
Comments posted to this topic are about the item Building AI Governance and Policies-...
Simple delete causes table scan on other tables with foreign key
Why is sql doing a full scan VS seeking on the index? I've included...
Show/Hide number of rows in table
We have a report that has multiple tables that list the top 15 performers...
Question of the Day
Checking Identities
The DBCC CHECKIDENT command is used when working with identity values. I have a table with 10 rows in it that looks like this:
TravelLogID CityID StartDate EndDate 1 1 2025-01-11 2025-01-16 2 2 2025-01-11 2025-01-16 3 3 2025-01-11 2025-01-16 4 4 2025-01-11 2025-01-16 5 5 2025-01-11 2025-01-16 6 6 2025-01-11 2025-01-16 7 7 2025-01-11 2025-01-16 8 8 2025-01-11 2025-01-16 9 9 2025-01-11 2025-01-16 10 10 2025-01-11 2025-01-16The docs for DBCC CHECKIDENT say this if I run with only the table parameter: "If the current identity value for a table is less than the maximum identity value stored in the identity column, it is reset using the maximum value in the identity column. " I run this code:
DELETE dbo.TravelLog WHERE TravelLogID >= 9
GO
DBCC CHECKIDENT(TravelLog, RESEED)
GO
INSERT dbo.TravelLog
(
CityID,
StartDate,
EndDate
)
VALUES
(4, '2025-09-14', '2025-09-17')
GO
What is the identity value for the new row inserted by the insert statement above? See possible answers