>>

It always intriged me how MSSQL, Sysbase, Watcom, etc had a single
setting to determine case-insensitivity across the entire DB.
Whilst looking in this tonight I created a blank DB in MSSQL and
it turns out that it uses a default setting from the registry:

HKLM\software\microsoft\mssqlserver\mssqlserver\DefaultCollationName
is 'Latin1_General_CI_AS' and this is *case-insensitive* by default.
<<


--- In Firebird-Architect@yahoogroups.com, "Arno Brinkman"
<firebird@a...> wrote:

>
> Hi,
>
> > Perhaps a database administration tool could fix this "issue"?

Let's say

> > you set the default collation in it, and it add collation to each new
> > column automatically. Of course, you would have to use admin.

tools that

> > have such feature.
>
> This can already be done by setting the RDB$DEFAULT_COLUMN_NAME from

the default

> RDB$CHARACTER_SET_NAME. Though you must keep in mind that this

default value doesn't survive a

> backup/restore!
>
> Regards,
> Arno Brinkman
> ABVisie

Do we have Latin1_General_CI_AS (or an equivalent?)

Tom