Error when importing data

connelvalentine
connelvalentine used Ask the Experts™
on
Hi,

I have a database called SUNDB running in SQL Server 2005. I also have a job running (saved as a SSIS package) that imports data from a couple of tables into another database called SUNREP.

Recently, we had called in the vendor to change theSUNDB  database collation to Cyrillic_General (it was originally Latin General). He ended up creating a new database all together with the new collation.

The problem now is that my job is failing. I tried recreating the job but to no success. The error that I'm getting is:

The column ####### cannot be processed because more than one code page (1251 and 1252) are specified for it.

At first i thought it was a problem with the SSIS package, so then i just tried creating a a normal "Import Data" task using the wizard and that failed too.

I then tried changing the collation of the SUNREP database to match the same Cyrillic General collation of SUNDB, by just changing it in the options, but this didn't work either.

Any ideas on this? At this stage i don't really want to create a SSIS package, i just want the database import to work as getting the data from SUN to SUNREP is rather urgent.

I'm no expert at SQL, i just make sure the database is backedup and the jobs run, so please use layman terms if you don't mind :)

Best Regards,
CV
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Top Expert 2011
Commented:
I think there is a feature called AlwaysUseDefaultCodePage

Try turning that from false to True and try again. Please see link below

http://blog.techno-tricks.com/?p=28

Author

Commented:
But again, this seems to be a property that is set when creating SSIS packages. In my case, I'm just tring to accomplish a normal import data wizard task and it fails with this error.

Author

Commented:
i've also seem to have come across another discovery. I tried creating a new database, and started importing the data from scratch. When the tables in the destination database doesn't exist, and the import job requires to create the table and then transfer the data, all seems fine.

but if i run the import job AGAIN, when the table already exists in the destination database, the same error above occurs.
Why Diversity in Tech Matters

Kesha Williams, certified professional and software developer, explores the imbalance of diversity in the world of technology -- especially when it comes to hiring women. She showcases ways she's making a difference through the Colors of STEM program.

Pit Zmillionaire
Commented:
check all varchar column colation and set all to only one
well it turns out that i had to recreate the new database with the collation of the source database and redo the import jobs from scratch. thanks to. thanks to all for the help

Author

Commented:
answered partially

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial