Greetings!
I'm trying to install SQL Server 2000 (Standard edition) on a new server to
mirror the version on an older server. The trouble I'm having is with
identifying the settings I need in order to match collations.
The instance of SQL Server on the old server has a collation described as
'SQL_Latin1_General_CP1_CI_AS'. I realise that 'CI' and 'AS' refer to
case-insensitive and accent-sensitive respectively, but what does 'CP1'
relate to?
I've searched through various resources but they all seem to avoid
describing that one crucial bit of information! Can anyone help?
Code page 1
"Mario" <someone.else@.microsoft.com> wrote in message
news:O3bumugWEHA.1368@.TK2MSFTNGP10.phx.gbl...
> Greetings!
> I'm trying to install SQL Server 2000 (Standard edition) on a new server
to
> mirror the version on an older server. The trouble I'm having is with
> identifying the settings I need in order to match collations.
> The instance of SQL Server on the old server has a collation described as
> 'SQL_Latin1_General_CP1_CI_AS'. I realise that 'CI' and 'AS' refer to
> case-insensitive and accent-sensitive respectively, but what does 'CP1'
> relate to?
> I've searched through various resources but they all seem to avoid
> describing that one crucial bit of information! Can anyone help?
>
|||In setup you should select "Dictionary order, case-insensitive, for use
with 1252 character set" in the collation selection dialog. This is the
default collation for U.S. English SQL Servers.
Bart Duncan
Microsoft SQL Server Support
Please reply to the newsgroup only - thanks.
This posting is provided "AS IS" with no warranties, and confers no
rights.
From: "Adam Machanic" <amachanic@.hotmail._removetoemail_.com>
References: <O3bumugWEHA.1368@.TK2MSFTNGP10.phx.gbl>
Subject: Re: Collation Confusion
Date: Thu, 24 Jun 2004 13:08:24 -0400
Lines: 22
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1409
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Message-ID: <uAyDd3gWEHA.1468@.TK2MSFTNGP10.phx.gbl>
Newsgroups: microsoft.public.sqlserver.server
NNTP-Posting-Host: firewall.getconnected.com 207.31.238.50
Path:
cpmsftngxa10.phx.gbl!TK2MSFTNGXA06.phx.gbl!cpmsftn gxa06.phx.gbl!TK2MSFTNGX
A01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP10.phx. gbl
Xref: cpmsftngxa10.phx.gbl microsoft.public.sqlserver.server:347579
X-Tomcat-NG: microsoft.public.sqlserver.server
Code page 1
"Mario" <someone.else@.microsoft.com> wrote in message
news:O3bumugWEHA.1368@.TK2MSFTNGP10.phx.gbl...
> Greetings!
> I'm trying to install SQL Server 2000 (Standard edition) on a new server
to
> mirror the version on an older server. The trouble I'm having is with
> identifying the settings I need in order to match collations.
> The instance of SQL Server on the old server has a collation described
as
> 'SQL_Latin1_General_CP1_CI_AS'. I realise that 'CI' and 'AS' refer to
> case-insensitive and accent-sensitive respectively, but what does 'CP1'
> relate to?
> I've searched through various resources but they all seem to avoid
> describing that one crucial bit of information! Can anyone help?
>
sqlsql
Showing posts with label older. Show all posts
Showing posts with label older. Show all posts
Sunday, March 25, 2012
Thursday, March 22, 2012
Collation Confusion
Greetings!
I'm trying to install SQL Server 2000 (Standard edition) on a new server to
mirror the version on an older server. The trouble I'm having is with
identifying the settings I need in order to match collations.
The instance of SQL Server on the old server has a collation described as
'SQL_Latin1_General_CP1_CI_AS'. I realise that 'CI' and 'AS' refer to
case-insensitive and accent-sensitive respectively, but what does 'CP1'
relate to?
I've searched through various resources but they all seem to avoid
describing that one crucial bit of information! Can anyone help?Code page 1
"Mario" <someone.else@.microsoft.com> wrote in message
news:O3bumugWEHA.1368@.TK2MSFTNGP10.phx.gbl...
> Greetings!
> I'm trying to install SQL Server 2000 (Standard edition) on a new server
to
> mirror the version on an older server. The trouble I'm having is with
> identifying the settings I need in order to match collations.
> The instance of SQL Server on the old server has a collation described as
> 'SQL_Latin1_General_CP1_CI_AS'. I realise that 'CI' and 'AS' refer to
> case-insensitive and accent-sensitive respectively, but what does 'CP1'
> relate to?
> I've searched through various resources but they all seem to avoid
> describing that one crucial bit of information! Can anyone help?
>|||In setup you should select "Dictionary order, case-insensitive, for use
with 1252 character set" in the collation selection dialog. This is the
default collation for U.S. English SQL Servers.
--
Bart Duncan
Microsoft SQL Server Support
Please reply to the newsgroup only - thanks.
This posting is provided "AS IS" with no warranties, and confers no
rights.
From: "Adam Machanic" <amachanic@.hotmail._removetoemail_.com>
References: <O3bumugWEHA.1368@.TK2MSFTNGP10.phx.gbl>
Subject: Re: Collation Confusion
Date: Thu, 24 Jun 2004 13:08:24 -0400
Lines: 22
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1409
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Message-ID: <uAyDd3gWEHA.1468@.TK2MSFTNGP10.phx.gbl>
Newsgroups: microsoft.public.sqlserver.server
NNTP-Posting-Host: firewall.getconnected.com 207.31.238.50
Path:
cpmsftngxa10.phx.gbl!TK2MSFTNGXA06.phx.gbl!cpmsftngxa06.phx.gbl!TK2MSFTNGX
A01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP10.phx.gbl
Xref: cpmsftngxa10.phx.gbl microsoft.public.sqlserver.server:347579
X-Tomcat-NG: microsoft.public.sqlserver.server
Code page 1
"Mario" <someone.else@.microsoft.com> wrote in message
news:O3bumugWEHA.1368@.TK2MSFTNGP10.phx.gbl...
> Greetings!
> I'm trying to install SQL Server 2000 (Standard edition) on a new server
to
> mirror the version on an older server. The trouble I'm having is with
> identifying the settings I need in order to match collations.
> The instance of SQL Server on the old server has a collation described
as
> 'SQL_Latin1_General_CP1_CI_AS'. I realise that 'CI' and 'AS' refer to
> case-insensitive and accent-sensitive respectively, but what does 'CP1'
> relate to?
> I've searched through various resources but they all seem to avoid
> describing that one crucial bit of information! Can anyone help?
>
I'm trying to install SQL Server 2000 (Standard edition) on a new server to
mirror the version on an older server. The trouble I'm having is with
identifying the settings I need in order to match collations.
The instance of SQL Server on the old server has a collation described as
'SQL_Latin1_General_CP1_CI_AS'. I realise that 'CI' and 'AS' refer to
case-insensitive and accent-sensitive respectively, but what does 'CP1'
relate to?
I've searched through various resources but they all seem to avoid
describing that one crucial bit of information! Can anyone help?Code page 1
"Mario" <someone.else@.microsoft.com> wrote in message
news:O3bumugWEHA.1368@.TK2MSFTNGP10.phx.gbl...
> Greetings!
> I'm trying to install SQL Server 2000 (Standard edition) on a new server
to
> mirror the version on an older server. The trouble I'm having is with
> identifying the settings I need in order to match collations.
> The instance of SQL Server on the old server has a collation described as
> 'SQL_Latin1_General_CP1_CI_AS'. I realise that 'CI' and 'AS' refer to
> case-insensitive and accent-sensitive respectively, but what does 'CP1'
> relate to?
> I've searched through various resources but they all seem to avoid
> describing that one crucial bit of information! Can anyone help?
>|||In setup you should select "Dictionary order, case-insensitive, for use
with 1252 character set" in the collation selection dialog. This is the
default collation for U.S. English SQL Servers.
--
Bart Duncan
Microsoft SQL Server Support
Please reply to the newsgroup only - thanks.
This posting is provided "AS IS" with no warranties, and confers no
rights.
From: "Adam Machanic" <amachanic@.hotmail._removetoemail_.com>
References: <O3bumugWEHA.1368@.TK2MSFTNGP10.phx.gbl>
Subject: Re: Collation Confusion
Date: Thu, 24 Jun 2004 13:08:24 -0400
Lines: 22
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1409
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Message-ID: <uAyDd3gWEHA.1468@.TK2MSFTNGP10.phx.gbl>
Newsgroups: microsoft.public.sqlserver.server
NNTP-Posting-Host: firewall.getconnected.com 207.31.238.50
Path:
cpmsftngxa10.phx.gbl!TK2MSFTNGXA06.phx.gbl!cpmsftngxa06.phx.gbl!TK2MSFTNGX
A01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP10.phx.gbl
Xref: cpmsftngxa10.phx.gbl microsoft.public.sqlserver.server:347579
X-Tomcat-NG: microsoft.public.sqlserver.server
Code page 1
"Mario" <someone.else@.microsoft.com> wrote in message
news:O3bumugWEHA.1368@.TK2MSFTNGP10.phx.gbl...
> Greetings!
> I'm trying to install SQL Server 2000 (Standard edition) on a new server
to
> mirror the version on an older server. The trouble I'm having is with
> identifying the settings I need in order to match collations.
> The instance of SQL Server on the old server has a collation described
as
> 'SQL_Latin1_General_CP1_CI_AS'. I realise that 'CI' and 'AS' refer to
> case-insensitive and accent-sensitive respectively, but what does 'CP1'
> relate to?
> I've searched through various resources but they all seem to avoid
> describing that one crucial bit of information! Can anyone help?
>
Collation Confusion
Greetings!
I'm trying to install SQL Server 2000 (Standard edition) on a new server to
mirror the version on an older server. The trouble I'm having is with
identifying the settings I need in order to match collations.
The instance of SQL Server on the old server has a collation described as
'SQL_Latin1_General_CP1_CI_AS'. I realise that 'CI' and 'AS' refer to
case-insensitive and accent-sensitive respectively, but what does 'CP1'
relate to?
I've searched through various resources but they all seem to avoid
describing that one crucial bit of information! Can anyone help?Code page 1
"Mario" <someone.else@.microsoft.com> wrote in message
news:O3bumugWEHA.1368@.TK2MSFTNGP10.phx.gbl...
> Greetings!
> I'm trying to install SQL Server 2000 (Standard edition) on a new server
to
> mirror the version on an older server. The trouble I'm having is with
> identifying the settings I need in order to match collations.
> The instance of SQL Server on the old server has a collation described as
> 'SQL_Latin1_General_CP1_CI_AS'. I realise that 'CI' and 'AS' refer to
> case-insensitive and accent-sensitive respectively, but what does 'CP1'
> relate to?
> I've searched through various resources but they all seem to avoid
> describing that one crucial bit of information! Can anyone help?
>|||In setup you should select "Dictionary order, case-insensitive, for use
with 1252 character set" in the collation selection dialog. This is the
default collation for U.S. English SQL Servers.
Bart Duncan
Microsoft SQL Server Support
Please reply to the newsgroup only - thanks.
This posting is provided "AS IS" with no warranties, and confers no
rights.
From: "Adam Machanic" <amachanic@.hotmail._removetoemail_.com>
References: <O3bumugWEHA.1368@.TK2MSFTNGP10.phx.gbl>
Subject: Re: Collation Confusion
Date: Thu, 24 Jun 2004 13:08:24 -0400
Lines: 22
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1409
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Message-ID: <uAyDd3gWEHA.1468@.TK2MSFTNGP10.phx.gbl>
Newsgroups: microsoft.public.sqlserver.server
NNTP-Posting-Host: firewall.getconnected.com 207.31.238.50
Path:
cpmsftngxa10.phx.gbl!TK2MSFTNGXA06.phx.gbl!cpmsftngxa06.phx.gbl!TK2MSFTNGX
A01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP10.phx.gbl
Xref: cpmsftngxa10.phx.gbl microsoft.public.sqlserver.server:347579
X-Tomcat-NG: microsoft.public.sqlserver.server
Code page 1
"Mario" <someone.else@.microsoft.com> wrote in message
news:O3bumugWEHA.1368@.TK2MSFTNGP10.phx.gbl...
> Greetings!
> I'm trying to install SQL Server 2000 (Standard edition) on a new server
to
> mirror the version on an older server. The trouble I'm having is with
> identifying the settings I need in order to match collations.
> The instance of SQL Server on the old server has a collation described
as
> 'SQL_Latin1_General_CP1_CI_AS'. I realise that 'CI' and 'AS' refer to
> case-insensitive and accent-sensitive respectively, but what does 'CP1'
> relate to?
> I've searched through various resources but they all seem to avoid
> describing that one crucial bit of information! Can anyone help?
>
I'm trying to install SQL Server 2000 (Standard edition) on a new server to
mirror the version on an older server. The trouble I'm having is with
identifying the settings I need in order to match collations.
The instance of SQL Server on the old server has a collation described as
'SQL_Latin1_General_CP1_CI_AS'. I realise that 'CI' and 'AS' refer to
case-insensitive and accent-sensitive respectively, but what does 'CP1'
relate to?
I've searched through various resources but they all seem to avoid
describing that one crucial bit of information! Can anyone help?Code page 1
"Mario" <someone.else@.microsoft.com> wrote in message
news:O3bumugWEHA.1368@.TK2MSFTNGP10.phx.gbl...
> Greetings!
> I'm trying to install SQL Server 2000 (Standard edition) on a new server
to
> mirror the version on an older server. The trouble I'm having is with
> identifying the settings I need in order to match collations.
> The instance of SQL Server on the old server has a collation described as
> 'SQL_Latin1_General_CP1_CI_AS'. I realise that 'CI' and 'AS' refer to
> case-insensitive and accent-sensitive respectively, but what does 'CP1'
> relate to?
> I've searched through various resources but they all seem to avoid
> describing that one crucial bit of information! Can anyone help?
>|||In setup you should select "Dictionary order, case-insensitive, for use
with 1252 character set" in the collation selection dialog. This is the
default collation for U.S. English SQL Servers.
Bart Duncan
Microsoft SQL Server Support
Please reply to the newsgroup only - thanks.
This posting is provided "AS IS" with no warranties, and confers no
rights.
From: "Adam Machanic" <amachanic@.hotmail._removetoemail_.com>
References: <O3bumugWEHA.1368@.TK2MSFTNGP10.phx.gbl>
Subject: Re: Collation Confusion
Date: Thu, 24 Jun 2004 13:08:24 -0400
Lines: 22
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1409
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Message-ID: <uAyDd3gWEHA.1468@.TK2MSFTNGP10.phx.gbl>
Newsgroups: microsoft.public.sqlserver.server
NNTP-Posting-Host: firewall.getconnected.com 207.31.238.50
Path:
cpmsftngxa10.phx.gbl!TK2MSFTNGXA06.phx.gbl!cpmsftngxa06.phx.gbl!TK2MSFTNGX
A01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP10.phx.gbl
Xref: cpmsftngxa10.phx.gbl microsoft.public.sqlserver.server:347579
X-Tomcat-NG: microsoft.public.sqlserver.server
Code page 1
"Mario" <someone.else@.microsoft.com> wrote in message
news:O3bumugWEHA.1368@.TK2MSFTNGP10.phx.gbl...
> Greetings!
> I'm trying to install SQL Server 2000 (Standard edition) on a new server
to
> mirror the version on an older server. The trouble I'm having is with
> identifying the settings I need in order to match collations.
> The instance of SQL Server on the old server has a collation described
as
> 'SQL_Latin1_General_CP1_CI_AS'. I realise that 'CI' and 'AS' refer to
> case-insensitive and accent-sensitive respectively, but what does 'CP1'
> relate to?
> I've searched through various resources but they all seem to avoid
> describing that one crucial bit of information! Can anyone help?
>
Friday, February 10, 2012
cluster-compatible OS versions
I have an existing 2-node cluster on older hardware that is hosting 3
SQL2000 virtual server/named instances. The current OS version for both
nodes is Windows 2003 Ent SP1.
I intend on upgrading this to a 3-node cluster by adding two very new
host nodes followed by removal of one older node, giving me an
active/active/passive failover setup.
The question is: can I simply load Win2003 R2 Ent SP2 on the new host
nodes and join them to the cluster, or do I need to first upgrade the
existing nodes in some fashion?
> The question is: can I simply load Win2003 R2 Ent SP2 on the new host
> nodes and join them to the cluster, or do I need to first upgrade the
> existing nodes in some fashion?
I have not done this specific scenario, but I'd guess that it should work
because that's no different from an OS rolling upgrade. In any event, I'd
keep the OS versions on all nodes the same when all is said and done.
Linchi
"horseradish" wrote:
> I have an existing 2-node cluster on older hardware that is hosting 3
> SQL2000 virtual server/named instances. The current OS version for both
> nodes is Windows 2003 Ent SP1.
> I intend on upgrading this to a 3-node cluster by adding two very new
> host nodes followed by removal of one older node, giving me an
> active/active/passive failover setup.
> The question is: can I simply load Win2003 R2 Ent SP2 on the new host
> nodes and join them to the cluster, or do I need to first upgrade the
> existing nodes in some fashion?
>
|||I would upgrade to SP2 (if your vendors support it) on the existing node.
Make sure you have a valid, restorable backup first. Then add in the second
SP2 nodes.
Cheers,
Rodney R. Fournier
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
ClusterHelp.com is a Microsoft Certified Gold Partner
"horseradish" <millardjk@.gmail.com> wrote in message
news:%23ilR6MojHHA.4904@.TK2MSFTNGP05.phx.gbl...
>I have an existing 2-node cluster on older hardware that is hosting 3
>SQL2000 virtual server/named instances. The current OS version for both
>nodes is Windows 2003 Ent SP1.
> I intend on upgrading this to a 3-node cluster by adding two very new host
> nodes followed by removal of one older node, giving me an
> active/active/passive failover setup.
> The question is: can I simply load Win2003 R2 Ent SP2 on the new host
> nodes and join them to the cluster, or do I need to first upgrade the
> existing nodes in some fashion?
SQL2000 virtual server/named instances. The current OS version for both
nodes is Windows 2003 Ent SP1.
I intend on upgrading this to a 3-node cluster by adding two very new
host nodes followed by removal of one older node, giving me an
active/active/passive failover setup.
The question is: can I simply load Win2003 R2 Ent SP2 on the new host
nodes and join them to the cluster, or do I need to first upgrade the
existing nodes in some fashion?
> The question is: can I simply load Win2003 R2 Ent SP2 on the new host
> nodes and join them to the cluster, or do I need to first upgrade the
> existing nodes in some fashion?
I have not done this specific scenario, but I'd guess that it should work
because that's no different from an OS rolling upgrade. In any event, I'd
keep the OS versions on all nodes the same when all is said and done.
Linchi
"horseradish" wrote:
> I have an existing 2-node cluster on older hardware that is hosting 3
> SQL2000 virtual server/named instances. The current OS version for both
> nodes is Windows 2003 Ent SP1.
> I intend on upgrading this to a 3-node cluster by adding two very new
> host nodes followed by removal of one older node, giving me an
> active/active/passive failover setup.
> The question is: can I simply load Win2003 R2 Ent SP2 on the new host
> nodes and join them to the cluster, or do I need to first upgrade the
> existing nodes in some fashion?
>
|||I would upgrade to SP2 (if your vendors support it) on the existing node.
Make sure you have a valid, restorable backup first. Then add in the second
SP2 nodes.
Cheers,
Rodney R. Fournier
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
ClusterHelp.com is a Microsoft Certified Gold Partner
"horseradish" <millardjk@.gmail.com> wrote in message
news:%23ilR6MojHHA.4904@.TK2MSFTNGP05.phx.gbl...
>I have an existing 2-node cluster on older hardware that is hosting 3
>SQL2000 virtual server/named instances. The current OS version for both
>nodes is Windows 2003 Ent SP1.
> I intend on upgrading this to a 3-node cluster by adding two very new host
> nodes followed by removal of one older node, giving me an
> active/active/passive failover setup.
> The question is: can I simply load Win2003 R2 Ent SP2 on the new host
> nodes and join them to the cluster, or do I need to first upgrade the
> existing nodes in some fashion?
Subscribe to:
Posts (Atom)