June 10, 2008 at 9:39 am
Sometimes I really get fed-up with SSIS. OK, so here I am trying to copy a table from 1 server to another. Source & destination are exactly the same, with varchar attributes, not nvarchar. Building a simple thing like that from scratch gives me the dreaded 'cannot convert unicode to non-unicode string data type'. No matter what I do, changing the offending attributes with advance editor does not solve the problem, it replaces them with similar errors in other attributes.
So, I read somewhere to use the Import-Export Wizard because the conversions will be done automatically. I do that, save the SSIS-package as a file in order to look at it in VS. However, when opening this file the Debug button is greyed out! I cannot run this package I just created!!!
2 Questions:
Why can't I run this package I just created with Import-Export Wiz?
Why do I keep getting these conversion errors between 2 fields which are exactly the same?!
Greetz,
Hans Brouwer
June 10, 2008 at 9:43 am
It may have something to do with your database collation settings being different from source to destination
~PD
June 11, 2008 at 12:48 am
Nope, they're the same. As are the 2 tables, including collation order.
As an add-on: source is SQL2K, destination SQL2005. I really hope that's not a problem!
Greetz,
Hans Brouwer
June 12, 2008 at 12:27 am
This shouldnt be a problem, I export lots of tables between 2000 and 2005.
The only time I hit some issues is with collation
Good luck on this one
~PD
June 18, 2008 at 8:51 am
I am still curious why a file package made with the Import/Export wizard cannot be debugged in VS2003...
Greetz,
Hans Brouwer
Viewing 5 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply