<NEWBIE>Move database from case sensitive to case insensitive servers

I know there are several ways to copy information from one machine to another, and from my research in the archives every approach has its adherents. I'd just like a better idea of which is the best method for my particular case.
There is a database residing on a remote server that has been set up as case sensitive. I need to move the database to my own departmental server, which is case insensitive (and the app vendor prefers this). Which is the best method to move the system, where best means first, no errors and second, little effort on my part.
Right now I'm leaning toward detaching the database on the other machine and copying its mdf and ldf files to the local machine and reattaching it. Will the case sensitivity cause problems
Thanks
J"John" <anonymous@.discussions.microsoft.com> wrote in message
news:1C256B86-16BD-4933-B081-264AC510F814@.microsoft.com...
> I know there are several ways to copy information from one machine to
another, and from my research in the archives every approach has its
adherents. I'd just like a better idea of which is the best method for my
particular case.
> There is a database residing on a remote server that has been set up as
case sensitive. I need to move the database to my own departmental server,
which is case insensitive (and the app vendor prefers this). Which is the
best method to move the system, where best means first, no errors and
second, little effort on my part.
> Right now I'm leaning toward detaching the database on the other machine
and copying its mdf and ldf files to the local machine and reattaching it.
Will the case sensitivity cause problems?
>
Are you running SQL Server 2000? Then that should work for you. Another
option, create the database on the target with the collation you need, then
run a RESTORE. For more information, see BOL "SQL Server Collation
Fundamentals".
Steve|||Do you want the database to be case sensitive or case insensitive on the new
server?
Watch out having different collations for you system databases vs. your
application database(s). If the app wasn't tested for this, you might get
error messages from the queries it submits (collation conflict messages).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"John" <anonymous@.discussions.microsoft.com> wrote in message
news:1C256B86-16BD-4933-B081-264AC510F814@.microsoft.com...
> I know there are several ways to copy information from one machine to
another, and from my research in the archives every approach has its
adherents. I'd just like a better idea of which is the best method for my
particular case.
> There is a database residing on a remote server that has been set up as
case sensitive. I need to move the database to my own departmental server,
which is case insensitive (and the app vendor prefers this). Which is the
best method to move the system, where best means first, no errors and
second, little effort on my part.
> Right now I'm leaning toward detaching the database on the other machine
and copying its mdf and ldf files to the local machine and reattaching it.
Will the case sensitivity cause problems?
> Thanks,
> J