Re: Changing server collation

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Tibor Karaszi (tibor_please.no.email_karaszi_at_hotmail.nomail.com)
Date: 09/15/04


Date: Wed, 15 Sep 2004 18:56:08 +0200

If SERVEPROPERTY doesn't reflect the collation selected in REBUILDM.EXE, I can think of a few
reasons:

1. A terrible bug in REBUILDM.EXE. I have not heard about one that has this symptom.
2. REBUILM.EXE failed to execute properly and you didn't notice the errormessage.
3. You are looking at the wrong SQL Server instance.

-- 
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Jfhayes" <Jfhayes@discussions.microsoft.com> wrote in message 
news:C342001F-85F1-45A3-9A12-A87C4F9F1798@microsoft.com...
> That is exactly what I am saying.  The serverproperty shows the collation as
> Sql_ Latin1_General.  I tried an uninstall, since it is a brand new server.
> I could start from scratch, but now my curiosity is up on how to change it.
>
> Thanks for any assistance you can give.
>
> "Tibor Karaszi" wrote:
>
>> Are you saying that you did REBUILDM.EXE and after that you don't have the collation you 
>> specified
>> in REBUILDM.EXE? What does the SERVERPROPERTY() function say?
>>
>> -- 
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>>
>> "Jfhayes" <Jfhayes@discussions.microsoft.com> wrote in message
>> news:2381BB08-B280-41FE-A584-325616304C0C@microsoft.com...
>> >I just did a new MSSql 2000 Server install, unfortunately with the wrong
>> > Default Collation.  Since I have no user databases attached, I just ran the
>> > rebuildm.  When I look at rebuildM now, it shows Dictionary Order, Case
>> > Insensitive, for use with Code 1251.  However, the Sp_HelpSort still shows
>> > Latin1-General, and the Server Collation still shows Sql_Latin1_general.
>> > ...How can I change this to default Code Page 1252?
>> >
>> > Many Thanks
>>
>>
>> 


Relevant Pages

  • Re: Different Collation designator Settings
    ... You can have databases with different collations on SQL ... That wasn't possible on SQL Server 7. ... values in temporary tables while assuming that tempdb has the same collation ...
    (microsoft.public.sqlserver.connect)
  • Re: Different Collation designator Settings
    ... You can have databases with different collations on SQL ... That wasn't possible on SQL Server 7. ... values in temporary tables while assuming that tempdb has the same collation ...
    (microsoft.public.sqlserver.server)
  • Re: Different Collation designator Settings
    ... You can have databases with different collations on SQL ... That wasn't possible on SQL Server 7. ... values in temporary tables while assuming that tempdb has the same collation ...
    (microsoft.public.sqlserver.setup)
  • Re: Different Collation designator Settings
    ... You can have databases with different collations on SQL ... That wasn't possible on SQL Server 7. ... values in temporary tables while assuming that tempdb has the same collation ...
    (microsoft.public.sqlserver.odbc)
  • Re: Error for a job that uses a MSDASQL linked server
    ... the job is, i.e., on the server where you define the linked server. ... Tibor Karaszi, SQL Server MVP ... The related login has to be present in SQL1 and SQL2. ...
    (microsoft.public.sqlserver.server)