Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase ««123»»

Collation Error 468 Expand / Collapse
Author
Message
Posted Thursday, October 11, 2007 6:24 AM
UDP Broadcaster

UDP BroadcasterUDP BroadcasterUDP BroadcasterUDP BroadcasterUDP BroadcasterUDP BroadcasterUDP BroadcasterUDP Broadcaster

Group: General Forum Members
Last Login: 2 days ago @ 8:05 AM
Points: 1,451, Visits: 2,911
I most often come across the issue when the server install gets completed and the guys don't alter the regional settings to UK, then when SQL Server gets installed it takes the US settings from the server default, I think in 2000 even if you changed the collation on the install you still had the issue if I remember rightly its some time since I've looked into this.

Facts are stubborn things, but statistics are more pliable - Mark Twain
Carolyn
SQLServerSpecialists
Post #409468
Posted Thursday, October 11, 2007 6:55 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Yesterday @ 12:06 PM
Points: 10,910, Visits: 12,546
I had this issue pop up on my once and found the fix in BOL. I was under the impression that the 2 collations you encountered were the same. I would be interested to know what the differences are. I have not found a good resource on the differences in collations anywhere yet.



Jack Corbett

Applications Developer

Don't let the good be the enemy of the best. -- Paul Fleming

Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
How to Post Performance Problems
Crosstabs and Pivots or How to turn rows into columns Part 1
Crosstabs and Pivots or How to turn rows into columns Part 2
Post #409494
Posted Thursday, October 11, 2007 7:02 AM
UDP Broadcaster

UDP BroadcasterUDP BroadcasterUDP BroadcasterUDP BroadcasterUDP BroadcasterUDP BroadcasterUDP BroadcasterUDP Broadcaster

Group: General Forum Members
Last Login: 2 days ago @ 8:05 AM
Points: 1,451, Visits: 2,911
The same but not the same, SQL Server doesn't recognise them as the same.

Facts are stubborn things, but statistics are more pliable - Mark Twain
Carolyn
SQLServerSpecialists
Post #409500
Posted Thursday, October 11, 2007 7:51 AM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: Administrators
Last Login: Yesterday @ 4:31 PM
Points: 32,780, Visits: 14,941
I pinged a few language people to see if they knew, but no response.

I can't find a difference either. They should be the same, and could be, but I think SQL Server's response is the error if there's any naming difference.







Follow me on Twitter: @way0utwest

Forum Etiquette: How to post data/code on a forum to get the best help
Post #409531
Posted Thursday, October 11, 2007 7:54 AM
Mr or Mrs. 500

Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500

Group: General Forum Members
Last Login: Wednesday, March 19, 2014 7:54 AM
Points: 574, Visits: 319
All my research pointed to them being the same, SQL just can't get over the name difference.


Post #409534
Posted Thursday, October 11, 2007 1:12 PM
Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Friday, November 22, 2013 11:05 AM
Points: 3,108, Visits: 2,116
I've run into this error a number of times because I usually use a MSX server to keep track and schedule maintenance amongst multiple servers. The offending database(s) are always vendor supplied. PeopleSoft and their usage of 'binary' for 'performance' being the most frequent offender.



Regards
Rudy Komacsar
Senior Database Administrator

"Ave Caesar! - Morituri te salutamus."
Post #409708
Posted Saturday, October 13, 2007 8:46 AM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: Administrators
Last Login: Yesterday @ 4:31 PM
Points: 32,780, Visits: 14,941
Found an explanation here:
http://blogs.msdn.com/michkap/archive/2007/10/10/5391882.aspx

You have to dig through a few posts, but basically the SQL team chose this collation to make things run a little quicker from when the setting was server wide. I'm not sure I completely understand the differences though.







Follow me on Twitter: @way0utwest

Forum Etiquette: How to post data/code on a forum to get the best help
Post #410310
Posted Monday, October 15, 2007 10:35 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Wednesday, June 10, 2009 5:29 AM
Points: 22, Visits: 52
Personally I came across a similar issue when I was involved with the transfer of an application from a site in Holland to my office in the UK. It seems that the application had originally been developed in SQL Server v7 and over the years the instance had been upgraded to SQL Server 2000. I believe (I may be wrong here) the default collation settings had changed between versions, thus when I restored the database into a fresh instance of 2000 I started getting these odd collation errors.

What seemed to be happening was that the collation settings were different on the application database as opposed to the tempdb database, which we were using for temporary tables. I had to figure out what the necessary collation setting was for my tempdb, something that unfortunately can't be changed after SQL Server has been installed. Armed with this knowledge I had to reinstall my SQL Server instance with the correct collation settings set up at install time.
Post #410919
Posted Monday, February 18, 2008 7:59 AM
SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Monday, March 10, 2014 2:25 AM
Points: 1,614, Visits: 888
I've had occasion to use COLLATE when I needed an accent insensitive search (I needed to find é as well as e when the user typed e), when all of our data has accent sensitive collation. The collation name has _AI on the end instead of _AS.
Post #456909
Posted Thursday, May 01, 2008 3:18 PM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Monday, October 29, 2012 9:48 PM
Points: 57, Visits: 217
When installing SQL Server you have two options:

1) Collation designator and sort order (default is Latin1_General)
2) SQL Collations (default is Dictionary order, case-insensitive).

It looks like you are seeing the difference between the two. Did you by any chance install SQL using Windows Collation designator one system and checked off "Accent - sensitive", but used SQL Collations on the other system?
Post #493932
« Prev Topic | Next Topic »

Add to briefcase ««123»»

Permissions Expand / Collapse