I'm having the following predicament.
I recently installed SQL 2008 SP1 on 2 servers; in both installations I left the collation settings unchanged to their default values.
Server1 is on O/S: Windows Server 2008 R2 Enterprise
Server2 is on O/S: Windows Server 2008 Standard SP2
I just discovered that:
- on Server1 the Server collation for SQL is: SQL_Latin1_General_CP1_CI_AS
- on Server2 the Server collation for SQL is: Latin1_General_CI_AS
As a result, I'm getting server-collation conflict errors in multi-server queries between Server2 and other servers in my environment.
How could the default collation for SQL have changed?
I never had to worry about this while installing SQL before...
Anyone have any ideas?
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]