Using the Import/Export Wizard, I ended up with an annoying problem:

Error 0xc02020f4: Data Flow Task 1: The column "pinNumber" cannot be processed because more than one code page (874 and 1252) are specified for it.

Looks like a different codepage (SQL_Latin1_General_CI_AS vs Latin1_General_CI_AS), so I changed those to match: Latin1_General_CI_AS for both.

However, the wizard still throws an error and detects two codepages - I even checked the tables and both source and destination show the same Latin1_General_CI_AS collation.

closed as off-topic by Paul White, Max Vernon, RLF, Mark Storey-Smith, Shawn Melton Jan 2 '15 at 16:51

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "Too localized - this could be because your code has a typo, basic error, or is not relevant to most of our audience. Consider revising your question so that it appeals to a broader audience. As it stands, the question is unlikely to help other users (regarding typo questions, see this meta question for background)." – Paul White, Max Vernon, RLF, Mark Storey-Smith, Shawn Melton
If this question can be reworded to fit the rules in the help center, please edit the question.

  • What database are you using? – Philᵀᴹ Aug 5 '12 at 2:16
  • 1
    Plus, why are you trying to steal "pinNumber" ? :) – Philᵀᴹ Aug 5 '12 at 2:17
  • Is this between two instances of SQL Server on different hosts, or between two instances of SQL Server on the same host, or two databases on the same instance? SQL Server sets the code page (based on the Windows code page) for an instance when you install it, and AFAIK that can't be changed. – Simon Righarts Aug 5 '12 at 10:37
  • one is MSSQL 2005 and other is 2008 instance installed on the same serverbox. Thing is i can import/export my other DB-s, only this one seems to have a problem. – Agony Aug 5 '12 at 12:22
  • 1
    Columns have collations associated with them -- changing the collation at a higher-up level only sets the default for new objects, it doesn't change existing objects. I'm pretty sure the columns still have different collations, and that's the problem. – Jon Seigel Aug 5 '12 at 15:25

Problem can be in field level as it was for me.

In a source database, a field in a table had a different collation in a varchar datatype.

If you choose < database default> for collation property of the fields, the problem may be solved.

Not the answer you're looking for? Browse other questions tagged or ask your own question.