Hey, Tim -

I'm trying to migrate a Nexus 2 database to ElevateDB, using the ElevateDB manager,
and it routinely fails.

Here's the generated SQL:

MIGRATE DATABASE FROM "NexusDB"
USING
"BlankNullStrings" = FALSE,
"Collation" = 'ENU_CI',
"DatabasePath" = 'W:\Bmt\BmtServer\DB',
"TablePasswords" = ''
WITH DATA


And here's the error message:
ElevateDB Error #202 An error occurred with the module edbmigratendb (The collation ENU_CI is not valid)

I've tried all kinds of case variants on the collation name.   Any insights?

Thanks,
Curt

Curt,

<< And here's the error message:
ElevateDB Error #202 An error occurred with the module edbmigratendb (The
collation ENU_CI is not valid) >>

You can only use base collation names with the migrators - the case
sensitivity, etc. modifiers are gathered from the source database
definition.

--
Tim Young
Elevate Software
www.elevatesoft.com

Curt,

<< And here's the error message:
ElevateDB Error #202 An error occurred with the module edbmigratendb (The
collation ENU_CI is not valid) >>

You can only use base collation names with the migrators - the case
sensitivity, etc. modifiers are gathered from the source database
definition.
 

You flew right over my head there, Tim  (as you know, I'm new to ElevateDB).

So how do I make case insensitive collation the default for a database?    Do I have to redefine the collation for each individual column?

Curt,

<< You flew right over my head there, Tim  (as you know, I'm new to
ElevateDB). >>

The collation modifiers (case-sensitivity, etc.) are gleaned from the source
database in terms of how the source indexes are defined, specifically:

If any column is present in a primary or unique key constraint in the source
table, and the primary or unique key index marked as case-insensitive, then
the migrator will also mark the column as case-insensitive.

If you want to send me the source table CREATE TABLE DDL for NexusDB, I can
test it here and see if there are some improvements to be made.  There is
certainly the possibility that something was missed in this respect.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim -

I was asking--independent of migrator issues--whether it's possible to establish a database-wide (or table-wide) case-insensitive collation for all string-ish columns, or whether it must be defined on a column-by-column basis...

Thanks,
Curt

Curt,

<< I was asking--independent of migrator issues--whether it's possible to
establish a database-wide (or table-wide) case-insensitive collation for all
string-ish columns, or whether it must be defined on a column-by-column
basis... >>

Oh, sorry - no, it's column-by-column only.

--
Tim Young
Elevate Software
www.elevatesoft.com

Any chance in the future of supporting a "default collation" for a database, like the big guys do?

Curt,

<< Any chance in the future of supporting a "default collation" for a
database, like the big guys do? >>

Sure, I can add it as a enhancement request.

--
Tim Young
Elevate Software
www.elevatesoft.com