It would be useful to know which version(s) of MSSQL you are using, as 2000
is quite flexible in how you can work with collations, compared to previous
versions.
If you're moving the database to a new server, you may be able to simply
backup/restore, provided that the collations are compatible.
If you're reinstalling the same server as CS, then you'll need to rebuild
the master DB with the new collation and then restore the databases, again
if the collations are compatible.
There are plenty of issues which may arise when you move from CI to CS. In
particular, code which was written on a CI system tends to be very
inconsistent about object and variable names (dbo.Table, dbo.table,
dbo.TAble...) - this will break code and views. Also, string operations will
behave very differently, which may change the functionality of your
applications in unexpected ways.
I investigated this once (moving SQL6.5 CI to SQL2000 CS), and we decided it
wasn't worth the effort. It was a lot less work to code for case-sensitivity
in the places where we really needed it than to go through every piece of
existing code to correct it. Your situation and priorities may be very
different, of course.
Simon
"Sue Swanson" <sw******@optimalinternet.com> wrote in message
news:c9**************************@posting.google.c om...
I have a client who was installed improperly on a Case Insensitive
Collation SQL system and have been working with this system for over a
year. For them to move forward in application software versions, they
will need to be reinstalled on a Case Sensitive SQL system. I was
wondering if anyone has tried this and was willing to provide
information that may be of assistance? I have tried various some
options within DTS but without success.
