Migration Scripts errors: 2003->2007

[Guzun, Alex]

Hi,

just installed BCM2007 and wanted to migrate existing 2003 DB to 2007
Version of my existing DB is: 2.0.3606

db_V2toV3Migrate_script.sql

Gives me:

Caution: Changing any part of an object name could break scripts and stored
procedures.
Caution: Changing any part of an object name could break scripts and stored
procedures.
Msg 468, Level 16, State 9, Line 10
Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS"
and "Slovak_CI_AS" in the equal to operation.
Msg 468, Level 16, State 9, Line 4
Cannot resolve the collation conflict between "Slovak_CI_AS" and
"SQL_Latin1_General_CP1_CI_AS" in the equal to operation.
Msg 468, Level 16, State 9, Line 31
Cannot resolve the collation conflict between "Slovak_CI_AS" and
"SQL_Latin1_General_CP1_CI_AS" in the equal to operation.
Msg 15217, Level 16, State 1, Procedure sp_dropextendedproperty, Line 28
Property cannot be updated or deleted. Property 'MS_Description' does not
exist for 'dbo.ContactNamesTable.FirstName'.
Msg 468, Level 16, State 9, Procedure AccountsUnionView, Line 4
Cannot resolve the collation conflict between "Slovak_CI_AS" and
"SQL_Latin1_General_CP1_CI_AS" in the UNION operation.
Msg 208, Level 16, State 1, Procedure PublicAccountsView, Line 4
Invalid object name 'AccountsUnionView'.
Msg 468, Level 16, State 9, Procedure ContactsUnionView, Line 4
Cannot resolve the collation conflict between "Slovak_CI_AS" and
"SQL_Latin1_General_CP1_CI_AS" in the UNION operation.
Msg 208, Level 16, State 1, Procedure PublicContactsView, Line 4
Invalid object name 'ContactsUnionView'.
Msg 468, Level 16, State 9, Procedure PublicDeletedAccountsView, Line 6
Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS"
and "Slovak_CI_AS" in the UNION operation.
Msg 468, Level 16, State 9, Procedure PublicDeletedContactsView, Line 6
Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS"
and "Slovak_CI_AS" in the UNION operation.
Msg 8197, Level 16, State 4, Procedure trig_insertPublicAccountsView, Line 5
Object 'PublicAccountsView' does not exist or is invalid for this operation.
Msg 8197, Level 16, State 4, Procedure trig_updatePublicAccountsView, Line 2
Object 'PublicAccountsView' does not exist or is invalid for this operation.
Msg 8197, Level 16, State 4, Procedure trig_deletePublicAccountsView, Line 2
Object 'PublicAccountsView' does not exist or is invalid for this operation.
Msg 8197, Level 16, State 4, Procedure trig_insertPublicContactsView, Line 4
Object 'PublicContactsView' does not exist or is invalid for this operation.
Msg 8197, Level 16, State 4, Procedure trig_updatePublicContactsView, Line 2
Object 'PublicContactsView' does not exist or is invalid for this operation.
Msg 8197, Level 16, State 4, Procedure trig_deletePublicContactsView, Line 2
Object 'PublicContactsView' does not exist or is invalid for this operation.
....
....
...
..
and so one


db_V3Beta2ToV3Migrate_script.sql

(50 row(s) affected)

(198 row(s) affected)

(261 row(s) affected)
Msg 2705, Level 16, State 4, Line 11
Column names in each table must be unique. Column name 'GlobalObjectID' in
table 'dbo.ActivitiesTable' is specified more than once.
Msg 2705, Level 16, State 4, Line 2
Column names in each table must be unique. Column name 'DueDate' in table
'dbo.CampaignTable' is specified more than once.
Msg 2705, Level 16, State 4, Line 2
Column names in each table must be unique. Column name 'DisableBootCache' in
table 'dbo.OrgTable' is specified more than once.
Msg 2705, Level 16, State 4, Line 2
Column names in each table must be unique. Column name 'CompressedRichText'
in table 'dbo.ContactNotesTable' is specified more than once.
Msg 2705, Level 16, State 4, Line 2
Column names in each table must be unique. Column name 'CompressedRichText'
in table 'dbo.ActivityNotesTable' is specified more than once.
Msg 2714, Level 16, State 6, Line 2
There is already an object named 'UserPropertiesTable' in the database.
Msg 2714, Level 16, State 4, Line 2
There is already an object named 'FK_UserPropertiesTable_EntityTypesTable'
in the database.
Msg 1750, Level 16, State 0, Line 2
Could not create constraint. See previous errors.
....
....
...
..
and so one

 

[Luther]

It looks like you are upgrading from a Slovak version of BCM to BCM for
another locale, probably US English. I doubt that's supported, although
it would be helpful if BCM put up a message saying so and didn't
proceed with the migration.

 

[Guzun, Alex]

There is no Slovak version of BCM
And I know for 100% that I installed En version
BCM client wan't upgrade DB
SQL script got me errors
but after those errors I can connect to it using bcm2007

but I think it not so good to leave it in production

Also having troubles to export .bcm files from 2003 client Is says that
remote connection to sql is not allowed