Upsizing = Server Errors

[shivoshea]

Using the upsizing wizard to migrate an Access database to SQL Server has caused me some problems, I was wondering if any one could help me out with what these errors mean and how i could solve them..


Server Error 547: ALTER TABLE statement conflicted with COLUMN FOREIGN KEY constraint 'xxxJournal_FK0 0'.
The conflict occurred in database 'CashOfficeData SQL', table 'xxxBusiness Units', column 'Short Description'.

Server Error 1770: Foreign key 'xxxSaunders Jeffries EFTP_FK01' references invalid column 'Date' in referenced
table 'xxxCard Types'.
Server Error 1750: Could not create constraint. See previous errors.

Server Error 2714: There is already an object named 'xxxStore Entries- Account_FK00' in the database.
Server Error 1750: Could not create constraint. See previous errors.

Server Error 15135: Object is invalid. Extended properties are not permitted
on 'dbo.xxxSaunder s Jeffries EFTPOS.xxxSaund ers Jeffries EFTP_FK00', or the object does not exist.



I have looked through websites to get an understanding of what these errors mean but I dont understand or can't find them.

[Atli]

Hi, and welcome to TSDN!

Server Error 547: ALTER TABLE statement conflicted with COLUMN FOREIGN KEY constraint 'xxxJournal_FK0 0'.
The conflict occurred in database 'CashOfficeData SQL', table 'xxxBusiness Units', column 'Short Description'.

This error happens when you try to ALTER a column that has been referenced by another table. This is done so you can not delete data that will cause other tables to become damaged or useless.

To continue with this, you should examine the tables shown in the error message and remove any foreign key constraints.

Server Error 1770: Foreign key 'xxxSaunders Jeffries EFTP_FK01' references invalid column 'Date' in referenced
table 'xxxCard Types'.
Server Error 1750: Could not create constraint. See previous errors.

Here you are trying to create a foreign key constraint to an invalid column. It's likely that the column does not exist or that the two columns have different data types.

This error is most likely caused because of the first error.

Server Error 2714: There is already an object named 'xxxStore Entries- Account_FK00' in the database.
Server Error 1750: Could not create constraint. See previous errors.

Here you are trying to create an object that already exists. Check your table names. Note that MySQL table names are case-insesitive.

Server Error 15135: Object is invalid. Extended properties are not permitted
on 'dbo.xxxSaunder s Jeffries EFTPOS.xxxSaund ers Jeffries EFTP_FK00', or the object does not exist.

This is most likely a reference to a non-existing object. Most likely one of the objects the previous errors were supposed to create, and were unable to. Should be fixed if you fix the first error.