2005 Collation Change

  • Howdy all...

    I performed the change to our development environment and had perfect results. Went to perform the same update to our production servers and bombed...

    Environment Description/Differences:

    -Development-

    SQL 2005 SP3

    -DEVSQL (local/default, DBA's play area)

    -DEVSQL\INST1

    -DEVSQL\INST2

    -DEVSQL\INST3

    -Production-

    SQL 2005 SP3

    2 x Node 2003 Clustered A/A

    - PSQLA\INST1

    - PSQLB\INST2

    I was able to detach development databases and run the command:

    start /wait setup.exe /qb INSTANCENAME=INST1 REINSTALL=SQL_Engine REBUILDDATABASE=1 SAPWD=password SQLCOLLATION=SQL_Latin1_General_CP1_CI_AI

    Did this on the local and all instances with no issues. Did it back-n-forth bunch of times just to P.O.C.

    Performing the exact same thing to the production environment and it bombed... with no error which upsets me the most. The setup gui started, was checking components then just disappeared. The only difference is that these are clustered nodes. Anyone see/know what I might be missing?

    Thanks,

    Paul

  • on a Clustered Environment, Did you detach the nodes and stop the cluster services before attempting this:

  • If I detatch the nodes or stop the cluster service I loose the resources, i.e. no disk access and will not be able to see the system databases.

  • check to see this post if it is useful:

    http://www.sqlservercentral.com/Forums/Topic610659-146-1.aspx

    BTW: if you want to change the collation of one database use ALTER database.

  • Thanks for the useful command...

    Would it be as simple as adding the VS= command since I have them setup as A/A... Virtual Server = PSQLA, Instance = INST1..

    So alter the command to add:

    start /wait setup.exe /qb VS=PSQLA INSTANCENAME=INST1 REINSTALL=SQL_Engine REBUILDDATABASE=1 SAPWD= SQLCOLLATION=SQL_Latin1_General_CP1_CI_AS

    ?

  • your command should work but before starting the install:

    some more info:

    http://www.mssqltips.com/tip.asp?tip=1528

  • Thanks for all the links for information. I reviewed them and found that the only thing I was missing was the VS= command... so far... HAHA

    We opened a ticket with M$ a couple hours ago, I will update when a solution is found...

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply