Differing collations for database and server - How big a problem is it?

I am using 3 servers. They are SQL all Server Express. I just noticed
that they are all outof sync wrt. Versions and Collation. has there
been a SQL Server Express service pack released? I seem to remember one.
Live
====
Version:9.00.3042.00
Collation:Latin1_General_CI_AS
Development
===========
Version:9.00.3054.00
Collation:SQL_Latin1_General_CP1_CI_AS
Stage
=====
Version:9.00.2047.00
Collation:Latin1_General_CI_AS
1. What is the best solution to this collation problem? To alter the
Development server? - I guess so, but there's another related problem.
My main application database is using 'SQL_Latin1_General_CP1_CI_AS'!
[I have script to convert the collations so I don't need to
re-install]. Yep that's a database with SQL_Latin1_General_CP1_CI_AS
collation sitting on a server using Latin1_General_CI_AS collation.
Does it matter which of these 2 collations I use:Latin1_General_CI_AS
or SQL_Latin1_General_CP1_CI_AS?
2. Two of these servers (Live, Development) have had the SQL service
pack installed but why do those two have different version numbers? Is
it the case that some of the ordinary microsoft updates also update SQL
Server Express? I noticed that the provider who runs the Live site does
not add all the microsoft service packs and even when adding service
packs waits a while until they are 'proven in the field'. The Stage
server has probably not has the service pack - so I guess that explains
the version number.
Hi,
The collation is more important in database. Since sql 2000 I can have a
different server collation from database collation.
If you want link diferent servers, You must be in mind the collations of
databases.
The important is (again) that the databases in differents enviroments, have
the same collation.
Regards,
"mark4asp" wrote:

> I am using 3 servers. They are SQL all Server Express. I just noticed
> that they are all outof sync wrt. Versions and Collation. has there
> been a SQL Server Express service pack released? I seem to remember one.
> Live
> ====
> Version:9.00.3042.00
> Collation:Latin1_General_CI_AS
> Development
> ===========
> Version:9.00.3054.00
> Collation:SQL_Latin1_General_CP1_CI_AS
> Stage
> =====
> Version:9.00.2047.00
> Collation:Latin1_General_CI_AS
> 1. What is the best solution to this collation problem? To alter the
> Development server? - I guess so, but there's another related problem.
> My main application database is using 'SQL_Latin1_General_CP1_CI_AS'!
> [I have script to convert the collations so I don't need to
> re-install]. Yep that's a database with SQL_Latin1_General_CP1_CI_AS
> collation sitting on a server using Latin1_General_CI_AS collation.
> Does it matter which of these 2 collations I use:Latin1_General_CI_AS
> or SQL_Latin1_General_CP1_CI_AS?
> 2. Two of these servers (Live, Development) have had the SQL service
> pack installed but why do those two have different version numbers? Is
> it the case that some of the ordinary microsoft updates also update SQL
> Server Express? I noticed that the provider who runs the Live site does
> not add all the microsoft service packs and even when adding service
> packs waits a while until they are 'proven in the field'. The Stage
> server has probably not has the service pack - so I guess that explains
> the version number.
>
|||Another thing:
the version must be the same, is very important especially when you try to
do maintenance tasks. The results can be differents between servers.
Put Your servers in the same version
9.00.3054
Regards,
"Carlos A." wrote:
[vbcol=seagreen]
> Hi,
> The collation is more important in database. Since sql 2000 I can have a
> different server collation from database collation.
> If you want link diferent servers, You must be in mind the collations of
> databases.
> The important is (again) that the databases in differents enviroments, have
> the same collation.
>
> Regards,
>
> "mark4asp" wrote: