Hi,
I have built a server based on a db's collation that I want to load, however
I still receive the 'cannot resolve collation conflict for equal to
operation'.
I have checked the collations of the loaded against the tempdb.
loaded db:
SQL_Latin1_General_CP1_CI_AS
Latin1-General, case-insensitive, accent-sensitive, kanatype-insensitive,
width-insensitive
for Unicode Data, SQL Server Sort Order 52 on Code Page 1252 for non-Unicode
Data
tempdb:
Latin1_General_CI_AS
Latin1-General, case-insensitive, accent-sensitive, kanatype-insensitive,
width-insensitive
I would have thought the above would have been ok?
Does this mean a rebuild of master db to map collation to db?
Thanks.Hi sysbox27,
Definitly not the same! You can:
1. Rebuild you master database to have the same collation as your user
database.
OR
1.Change your user database collation to match the server collation by A)
Using DTS or Alter database, Alter table/alter column (the Alter table/alter
column has many restrictions). The following article describes how the above
can be done:
Article title: How to transfer a database from one collation to another
collation in SQL Server
Article Link:
http://support.microsoft.com/default.aspx?scid=kb;en-us;325335&Product=sql2k
Sasan Saidi
Senior DBA
"sysbox27" wrote:
> Hi,
> I have built a server based on a db's collation that I want to load, however
> I still receive the 'cannot resolve collation conflict for equal to
> operation'.
> I have checked the collations of the loaded against the tempdb.
> loaded db:
> SQL_Latin1_General_CP1_CI_AS
> Latin1-General, case-insensitive, accent-sensitive, kanatype-insensitive,
> width-insensitive
> for Unicode Data, SQL Server Sort Order 52 on Code Page 1252 for non-Unicode
> Data
> tempdb:
> Latin1_General_CI_AS
> Latin1-General, case-insensitive, accent-sensitive, kanatype-insensitive,
> width-insensitive
> I would have thought the above would have been ok?
> Does this mean a rebuild of master db to map collation to db?
> Thanks.|||Hi Sasan,
firstly let me say thanks for the assistance - much appreciated.
in my case I'm quite happy to rebuild server, but my problem is that I don't
see the collation below listed when it comes time to setup:
> > SQL_Latin1_General_CP1_CI_AS
> > Latin1-General, case-insensitive, accent-sensitive, kanatype-insensitive,
> > width-insensitive
> > for Unicode Data, SQL Server Sort Order 52 on Code Page 1252 for non-Unicode
> > Data
so how do I get this collation set?
thanks again.
"Sasan Saidi" wrote:
> Hi sysbox27,
> Definitly not the same! You can:
> 1. Rebuild you master database to have the same collation as your user
> database.
> OR
> 1.Change your user database collation to match the server collation by A)
> Using DTS or Alter database, Alter table/alter column (the Alter table/alter
> column has many restrictions). The following article describes how the above
> can be done:
> Article title: How to transfer a database from one collation to another
> collation in SQL Server
> Article Link:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;325335&Product=sql2k
> Sasan Saidi
> Senior DBA
> "sysbox27" wrote:
> > Hi,
> > I have built a server based on a db's collation that I want to load, however
> > I still receive the 'cannot resolve collation conflict for equal to
> > operation'.
> >
> > I have checked the collations of the loaded against the tempdb.
> > loaded db:
> > SQL_Latin1_General_CP1_CI_AS
> > Latin1-General, case-insensitive, accent-sensitive, kanatype-insensitive,
> > width-insensitive
> > for Unicode Data, SQL Server Sort Order 52 on Code Page 1252 for non-Unicode
> > Data
> >
> > tempdb:
> > Latin1_General_CI_AS
> > Latin1-General, case-insensitive, accent-sensitive, kanatype-insensitive,
> > width-insensitive
> >
> > I would have thought the above would have been ok?
> >
> > Does this mean a rebuild of master db to map collation to db?
> >
> > Thanks.|||If you run the following to see the list of all the collations supported by
Microsoft® SQL Server� 2000:
SELECT * FROM ::fn_helpcollations()
you will see "SQL_Latin1_General_CP1_CI_AS". On my server it is row 706!
Sasan
"sysbox27" wrote:
> Hi Sasan,
> firstly let me say thanks for the assistance - much appreciated.
> in my case I'm quite happy to rebuild server, but my problem is that I don't
> see the collation below listed when it comes time to setup:
> > > SQL_Latin1_General_CP1_CI_AS
> > > Latin1-General, case-insensitive, accent-sensitive, kanatype-insensitive,
> > > width-insensitive
> > > for Unicode Data, SQL Server Sort Order 52 on Code Page 1252 for non-Unicode
> > > Data
> so how do I get this collation set?
> thanks again.
>
>
>
> "Sasan Saidi" wrote:
> > Hi sysbox27,
> >
> > Definitly not the same! You can:
> > 1. Rebuild you master database to have the same collation as your user
> > database.
> > OR
> > 1.Change your user database collation to match the server collation by A)
> > Using DTS or Alter database, Alter table/alter column (the Alter table/alter
> > column has many restrictions). The following article describes how the above
> > can be done:
> >
> > Article title: How to transfer a database from one collation to another
> > collation in SQL Server
> > Article Link:
> > http://support.microsoft.com/default.aspx?scid=kb;en-us;325335&Product=sql2k
> >
> > Sasan Saidi
> > Senior DBA
> >
> > "sysbox27" wrote:
> >
> > > Hi,
> > > I have built a server based on a db's collation that I want to load, however
> > > I still receive the 'cannot resolve collation conflict for equal to
> > > operation'.
> > >
> > > I have checked the collations of the loaded against the tempdb.
> > > loaded db:
> > > SQL_Latin1_General_CP1_CI_AS
> > > Latin1-General, case-insensitive, accent-sensitive, kanatype-insensitive,
> > > width-insensitive
> > > for Unicode Data, SQL Server Sort Order 52 on Code Page 1252 for non-Unicode
> > > Data
> > >
> > > tempdb:
> > > Latin1_General_CI_AS
> > > Latin1-General, case-insensitive, accent-sensitive, kanatype-insensitive,
> > > width-insensitive
> > >
> > > I would have thought the above would have been ok?
> > >
> > > Does this mean a rebuild of master db to map collation to db?
> > >
> > > Thanks.|||Sasan,
right I see it in the list, but when I create a new server instance I don't
see that collation listed. how do I now go about changing the collation to
what I want or even building a new server with the collation mentioned below?
many thanks.
"Sasan Saidi" wrote:
> If you run the following to see the list of all the collations supported by
> Microsoft® SQL Server� 2000:
> SELECT * FROM ::fn_helpcollations()
> you will see "SQL_Latin1_General_CP1_CI_AS". On my server it is row 706!
> Sasan
> "sysbox27" wrote:
> > Hi Sasan,
> > firstly let me say thanks for the assistance - much appreciated.
> > in my case I'm quite happy to rebuild server, but my problem is that I don't
> > see the collation below listed when it comes time to setup:
> >
> > > > SQL_Latin1_General_CP1_CI_AS
> > > > Latin1-General, case-insensitive, accent-sensitive, kanatype-insensitive,
> > > > width-insensitive
> > > > for Unicode Data, SQL Server Sort Order 52 on Code Page 1252 for non-Unicode
> > > > Data
> >
> > so how do I get this collation set?
> >
> > thanks again.
> >
> >
> >
> >
> >
> >
> >
> > "Sasan Saidi" wrote:
> >
> > > Hi sysbox27,
> > >
> > > Definitly not the same! You can:
> > > 1. Rebuild you master database to have the same collation as your user
> > > database.
> > > OR
> > > 1.Change your user database collation to match the server collation by A)
> > > Using DTS or Alter database, Alter table/alter column (the Alter table/alter
> > > column has many restrictions). The following article describes how the above
> > > can be done:
> > >
> > > Article title: How to transfer a database from one collation to another
> > > collation in SQL Server
> > > Article Link:
> > > http://support.microsoft.com/default.aspx?scid=kb;en-us;325335&Product=sql2k
> > >
> > > Sasan Saidi
> > > Senior DBA
> > >
> > > "sysbox27" wrote:
> > >
> > > > Hi,
> > > > I have built a server based on a db's collation that I want to load, however
> > > > I still receive the 'cannot resolve collation conflict for equal to
> > > > operation'.
> > > >
> > > > I have checked the collations of the loaded against the tempdb.
> > > > loaded db:
> > > > SQL_Latin1_General_CP1_CI_AS
> > > > Latin1-General, case-insensitive, accent-sensitive, kanatype-insensitive,
> > > > width-insensitive
> > > > for Unicode Data, SQL Server Sort Order 52 on Code Page 1252 for non-Unicode
> > > > Data
> > > >
> > > > tempdb:
> > > > Latin1_General_CI_AS
> > > > Latin1-General, case-insensitive, accent-sensitive, kanatype-insensitive,
> > > > width-insensitive
> > > >
> > > > I would have thought the above would have been ok?
> > > >
> > > > Does this mean a rebuild of master db to map collation to db?
> > > >
> > > > Thanks.|||sysbox27,
Do a custom setup to see the collation dialog. On this dialog you'll want
to select the "SQL Collations" radio button (the other will be "Windows
Collations"). This will enable a drop down listbox at the bottom of the
form. In this listbox you should select "Dictionary order case insensitive
for use with the 1252 character set". On a U.S. English system this is the
default SQL collation, so you may not need to hunt for it in the list.
HTH,
Bart
--
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.
| Thread-Topic: collation
| thread-index: AcUYZ0SE2quK7560RG6lTeGqz6LsZg==| X-WBNR-Posting-Host: 82.35.233.73
| From: "=?Utf-8?B?c3lzYm94Mjc=?=" <sysbox27@.discussions.microsoft.com>
| References: <DBFB1E09-6BD0-4C1B-B012-1462AB8E7702@.microsoft.com>
<1A456C86-B4B3-49EC-9A51-6D92834B27FB@.microsoft.com>
<11CDF551-ED2B-436E-A3C2-29FCFC714607@.microsoft.com>
<BED1A525-DD68-4664-9504-9D0C1C2A6AB9@.microsoft.com>
| Subject: RE: collation
| Date: Mon, 21 Feb 2005 14:47:06 -0800
| Lines: 85
| Message-ID: <5A7D9817-DC47-4C23-B4AF-CADBA218F707@.microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 8bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.sqlserver.server
| NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
| Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
| Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sqlserver.server:378854
| X-Tomcat-NG: microsoft.public.sqlserver.server
|
| Sasan,
| right I see it in the list, but when I create a new server instance I
don't
| see that collation listed. how do I now go about changing the collation
to
| what I want or even building a new server with the collation mentioned
below?
| many thanks.
|
| "Sasan Saidi" wrote:
|
| > If you run the following to see the list of all the collations
supported by
| > Microsoft® SQL Server� 2000:
| >
| > SELECT * FROM ::fn_helpcollations()
| >
| > you will see "SQL_Latin1_General_CP1_CI_AS". On my server it is row 706!
| >
| > Sasan
| > "sysbox27" wrote:
| >
| > > Hi Sasan,
| > > firstly let me say thanks for the assistance - much appreciated.
| > > in my case I'm quite happy to rebuild server, but my problem is that
I don't
| > > see the collation below listed when it comes time to setup:
| > >
| > > > > SQL_Latin1_General_CP1_CI_AS
| > > > > Latin1-General, case-insensitive, accent-sensitive,
kanatype-insensitive,
| > > > > width-insensitive
| > > > > for Unicode Data, SQL Server Sort Order 52 on Code Page 1252 for
non-Unicode
| > > > > Data
| > >
| > > so how do I get this collation set?
| > >
| > > thanks again.
| > >
| > >
| > >
| > >
| > >
| > >
| > >
| > > "Sasan Saidi" wrote:
| > >
| > > > Hi sysbox27,
| > > >
| > > > Definitly not the same! You can:
| > > > 1. Rebuild you master database to have the same collation as your
user
| > > > database.
| > > > OR
| > > > 1.Change your user database collation to match the server collation
by A)
| > > > Using DTS or Alter database, Alter table/alter column (the Alter
table/alter
| > > > column has many restrictions). The following article describes how
the above
| > > > can be done:
| > > >
| > > > Article title: How to transfer a database from one collation to
another
| > > > collation in SQL Server
| > > > Article Link:
| > > >
http://support.microsoft.com/default.aspx?scid=kb;en-us;325335&Product=sql2k
| > > >
| > > > Sasan Saidi
| > > > Senior DBA
| > > >
| > > > "sysbox27" wrote:
| > > >
| > > > > Hi,
| > > > > I have built a server based on a db's collation that I want to
load, however
| > > > > I still receive the 'cannot resolve collation conflict for equal
to
| > > > > operation'.
| > > > >
| > > > > I have checked the collations of the loaded against the tempdb.
| > > > > loaded db:
| > > > > SQL_Latin1_General_CP1_CI_AS
| > > > > Latin1-General, case-insensitive, accent-sensitive,
kanatype-insensitive,
| > > > > width-insensitive
| > > > > for Unicode Data, SQL Server Sort Order 52 on Code Page 1252 for
non-Unicode
| > > > > Data
| > > > >
| > > > > tempdb:
| > > > > Latin1_General_CI_AS
| > > > > Latin1-General, case-insensitive, accent-sensitive,
kanatype-insensitive,
| > > > > width-insensitive
| > > > >
| > > > > I would have thought the above would have been ok?
| > > > >
| > > > > Does this mean a rebuild of master db to map collation to db?
| > > > >
| > > > > Thanks.
||||Thank you Bart & Sasan for your help.
Regards.
"Bart Duncan [MSFT]" wrote:
> sysbox27,
> Do a custom setup to see the collation dialog. On this dialog you'll want
> to select the "SQL Collations" radio button (the other will be "Windows
> Collations"). This will enable a drop down listbox at the bottom of the
> form. In this listbox you should select "Dictionary order case insensitive
> for use with the 1252 character set". On a U.S. English system this is the
> default SQL collation, so you may not need to hunt for it in the list.
> HTH,
> Bart
> --
> 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.
>
> --
> | Thread-Topic: collation
> | thread-index: AcUYZ0SE2quK7560RG6lTeGqz6LsZg==> | X-WBNR-Posting-Host: 82.35.233.73
> | From: "=?Utf-8?B?c3lzYm94Mjc=?=" <sysbox27@.discussions.microsoft.com>
> | References: <DBFB1E09-6BD0-4C1B-B012-1462AB8E7702@.microsoft.com>
> <1A456C86-B4B3-49EC-9A51-6D92834B27FB@.microsoft.com>
> <11CDF551-ED2B-436E-A3C2-29FCFC714607@.microsoft.com>
> <BED1A525-DD68-4664-9504-9D0C1C2A6AB9@.microsoft.com>
> | Subject: RE: collation
> | Date: Mon, 21 Feb 2005 14:47:06 -0800
> | Lines: 85
> | Message-ID: <5A7D9817-DC47-4C23-B4AF-CADBA218F707@.microsoft.com>
> | MIME-Version: 1.0
> | Content-Type: text/plain;
> | charset="Utf-8"
> | Content-Transfer-Encoding: 8bit
> | X-Newsreader: Microsoft CDO for Windows 2000
> | Content-Class: urn:content-classes:message
> | Importance: normal
> | Priority: normal
> | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> | Newsgroups: microsoft.public.sqlserver.server
> | NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
> | Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
> | Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sqlserver.server:378854
> | X-Tomcat-NG: microsoft.public.sqlserver.server
> |
> | Sasan,
> | right I see it in the list, but when I create a new server instance I
> don't
> | see that collation listed. how do I now go about changing the collation
> to
> | what I want or even building a new server with the collation mentioned
> below?
> | many thanks.
> |
> | "Sasan Saidi" wrote:
> |
> | > If you run the following to see the list of all the collations
> supported by
> | > MicrosoftÃ?® SQL Serverââ'¢ 2000:
> | >
> | > SELECT * FROM ::fn_helpcollations()
> | >
> | > you will see "SQL_Latin1_General_CP1_CI_AS". On my server it is row 706!
> | >
> | > Sasan
> | > "sysbox27" wrote:
> | >
> | > > Hi Sasan,
> | > > firstly let me say thanks for the assistance - much appreciated.
> | > > in my case I'm quite happy to rebuild server, but my problem is that
> I don't
> | > > see the collation below listed when it comes time to setup:
> | > >
> | > > > > SQL_Latin1_General_CP1_CI_AS
> | > > > > Latin1-General, case-insensitive, accent-sensitive,
> kanatype-insensitive,
> | > > > > width-insensitive
> | > > > > for Unicode Data, SQL Server Sort Order 52 on Code Page 1252 for
> non-Unicode
> | > > > > Data
> | > >
> | > > so how do I get this collation set?
> | > >
> | > > thanks again.
> | > >
> | > >
> | > >
> | > >
> | > >
> | > >
> | > >
> | > > "Sasan Saidi" wrote:
> | > >
> | > > > Hi sysbox27,
> | > > >
> | > > > Definitly not the same! You can:
> | > > > 1. Rebuild you master database to have the same collation as your
> user
> | > > > database.
> | > > > OR
> | > > > 1.Change your user database collation to match the server collation
> by A)
> | > > > Using DTS or Alter database, Alter table/alter column (the Alter
> table/alter
> | > > > column has many restrictions). The following article describes how
> the above
> | > > > can be done:
> | > > >
> | > > > Article title: How to transfer a database from one collation to
> another
> | > > > collation in SQL Server
> | > > > Article Link:
> | > > >
> http://support.microsoft.com/default.aspx?scid=kb;en-us;325335&Product=sql2k
> | > > >
> | > > > Sasan Saidi
> | > > > Senior DBA
> | > > >
> | > > > "sysbox27" wrote:
> | > > >
> | > > > > Hi,
> | > > > > I have built a server based on a db's collation that I want to
> load, however
> | > > > > I still receive the 'cannot resolve collation conflict for equal
> to
> | > > > > operation'.
> | > > > >
> | > > > > I have checked the collations of the loaded against the tempdb.
> | > > > > loaded db:
> | > > > > SQL_Latin1_General_CP1_CI_AS
> | > > > > Latin1-General, case-insensitive, accent-sensitive,
> kanatype-insensitive,
> | > > > > width-insensitive
> | > > > > for Unicode Data, SQL Server Sort Order 52 on Code Page 1252 for
> non-Unicode
> | > > > > Data
> | > > > >
> | > > > > tempdb:
> | > > > > Latin1_General_CI_AS
> | > > > > Latin1-General, case-insensitive, accent-sensitive,
> kanatype-insensitive,
> | > > > > width-insensitive
> | > > > >
> | > > > > I would have thought the above would have been ok?
> | > > > >
> | > > > > Does this mean a rebuild of master db to map collation to db?
> | > > > >
> | > > > > Thanks.
> |
>
Umachandar Jayachandran - MS wrote:
