Multiple databases using different collations on same instance

Hi all,
I'm in need of some advice, I currently have a SQL 2005 64 bit instance
running SQL_Latin1_CP_CI_AS, which is the collation type for my databases and
suits me fine, however I now need to create and populate a new database which
requires Latin1_General_BIN
Is this possible, are there any pitfalls I should watch out for.
ThanksHi
The biggest problem with creating non-system collation columns is probably
the collation conflicts that you may get when doing out of database
operations, such as using temporary tables; but you can usually get around
this by always specifying a collation using the COLLATE clause.
If you are only looking at using this collation for binary comparisons, you
may want to look at using the same collation but using the COLLATE clause to
force a binary collation in your where clause. This may be a more risky
problem as it will not give you an error when you forget the clause.
Checkout books online for more about COLLATE.
John
"Padraig" wrote:
> Hi all,
> I'm in need of some advice, I currently have a SQL 2005 64 bit instance
> running SQL_Latin1_CP_CI_AS, which is the collation type for my databases and
> suits me fine, however I now need to create and populate a new database which
> requires Latin1_General_BIN
> Is this possible, are there any pitfalls I should watch out for.
> Thanks