[58519] in SAPr3-news
Re: Impact of changing MSSQL database collation.
daemon@ATHENA.MIT.EDU (=?ISO-8859-1?Q?Markus_D=F6hr?=)
Tue Nov 28 06:28:22 2006
To: sapr3-news@mit.edu
Date: Tue, 28 Nov 2006 12:27:37 +0100
From: =?ISO-8859-1?Q?Markus_D=F6hr?= <wantbottom@t-online.de>
Message-ID: <456C1D29.1000301@t-online.de>
Alan Pope wrote:
[...]
> Most importantly:-
>
> - We have a secondary server for log shipping which would also need to
> be migrated to BIN2 (assumption?).
> - Can we run instcoll.exe on the secondary database and be sure it will
> not start the database thus invalidating the database?
> Or
> - Do we need to re-create the standby database after we have changed
> the collation order on the primary?
Check note 960769, especially the section "Microsoft SQL Server":
[...]
b) Check before the migration from MS SQL Server 2000 to MS SQL Server
2005 that:
- The database collation to SQL_Latin1-General_CP850_BIN2 is converted.
For further information, see Note 600027.
- You have imported all Basis Support Packages that are required. For
information about the Support Package level each SAP release requires
for MS SQL Server 2005, see Note 905634.
[...]
In note 600027 there is a section "homogeneous system copy":
[...]
If the collations do not match, proceed as follows depending on
the case that applies for your system: :
o Case 1: Database collation: SQL_Latin1_General_CP850_BIN
Target Server collation: SQL_Latin1_General_CP850_BIN2
a) In this case, attach the database.
b) Make sure that no user connects and uses this database.
c) Re-run InstColl.exe with the following command line:
InstColl -S<server> -D<database>
The special -D option allows you to convert only one
database.
This should finish within a very short time (<3 minutes)
You can now use the SAP database in its new location.
[...]
So there is no impact on functionality because SAP assumes in newer
releases that you use BIN2 and not BIN.
--
Markus
