Very Computer

I would greatly appreciate if anybody can give me an idea what are the
things I have to do or precautions I should undertake. This is the scenario:

Our current SQL Server 6.5 has a "binary" sort order, we have to change this
sort order to dictionary case-insensitive.

Thanks!

Luis,

 I'm afraid you have to re-install.  Transfer out the data first using bcp.

Quote:> I would greatly appreciate if anybody can give me an idea what are the
> things I have to do or precautions I should undertake. This is the scenario:

> Our current SQL Server 6.5 has a "binary" sort order, we have to change this
> sort order to dictionary case-insensitive.

 Neil Pike MVP/MCSE.  Protech Computing Ltd
 (Please post ALL replies to the newsgroup only unless indicated otherwise)
 For SQL FAQ entries see
 http://go.compuserve.com/sqlserver (library 1) - latest stuff is always here
 www.ntfaq.com/sql.html
 http://www.swynk.com/faq/sql/sqlserverfaq.asp

Thanks for your response Neil.

What I actually did was this:

I have a test SQL Server and I reinstalled SQL Server and this time I used
Dictionary case-insensitive sort order.  My Production SQl Server is still
in Binary Sort order. I used Transfer Manager to  transfer a couple of
databases from the Production to my test Server. The data was successfully
transferred, including all the stored procedures and view tables, EXCEPT
when I looked at my tables the columns don't have datatypes and Primary
keys, etc.. Any insight?

Thanks.
Maribel

Quote:> Luis,

>  I'm afraid you have to re-install.  Transfer out the data first using
bcp.

> > I would greatly appreciate if anybody can give me an idea what are the
> > things I have to do or precautions I should undertake. This is the
scenario:

> > Our current SQL Server 6.5 has a "binary" sort order, we have to change
this
> > sort order to dictionary case-insensitive.

>  Neil Pike MVP/MCSE.  Protech Computing Ltd
>  (Please post ALL replies to the newsgroup only unless indicated
otherwise)
>  For SQL FAQ entries see
>  http://go.compuserve.com/sqlserver (library 1) - latest stuff is always
here
>  www.ntfaq.com/sql.html
>  http://www.swynk.com/faq/sql/sqlserverfaq.asp

Maribel,

 Did you select to transfer all user defined datatypes and dependencies?

 Neil Pike MVP/MCSE.  Protech Computing Ltd
 (Please post ALL replies to the newsgroup only unless indicated otherwise)
 For SQL FAQ entries see
 http://go.compuserve.com/sqlserver (library 1) - latest stuff is always here
 www.ntfaq.com/sql.html
 http://www.swynk.com/faq/sql/sqlserverfaq.asp

Thanks again for your response.

Yes I did.  I somehow found the problem. I have to do some testing though to
make sure.
You might have encountered this problem or issue:

Production Server     -       SQL 6.5 SKP4
Test Server                -        SQL 6.5 SPK5

My frontend is Powerbuilder (I have two versions, PB5 and PB6.5) After
transfering the database to the Test Server (from Production) I looked at
the tables using PB5 and the datatypes are gone but when I view it again
using PB6.5, everything was okay.  I think it has to do with the Service
Pack 5.

Thanks,
Maribel.

Quote:> Maribel,

>  Did you select to transfer all user defined datatypes and dependencies?

>  Neil Pike MVP/MCSE.  Protech Computing Ltd
>  (Please post ALL replies to the newsgroup only unless indicated
otherwise)
>  For SQL FAQ entries see
>  http://go.compuserve.com/sqlserver (library 1) - latest stuff is always
here
>  www.ntfaq.com/sql.html
>  http://www.swynk.com/faq/sql/sqlserverfaq.asp

Luis,

 As part of the SP5 updates the system catalog procedures are updated.  Maybe
PB5 couldn't understand the output from these any longer...

 Neil Pike MVP/MCSE.  Protech Computing Ltd
 (Please post ALL replies to the newsgroup only unless indicated otherwise)
 For SQL FAQ entries see
 http://go.compuserve.com/sqlserver (library 1) - latest stuff is always here
 www.ntfaq.com/sql.html
 http://www.swynk.com/faq/sql/sqlserverfaq.asp