Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We have two SQL servers (source and destination). From what little information I've got, it seems to literally copy content from one server/database to another using a SSIS package (which I unfortunately am unable to find to open in BIDS)

I can't access the source server (please don't ask why!). The errors we're getting are against just one table (out of dozens)

Cannot convert between unicode and non-unicode string data types

The DBA on the source end can see the destination server and all the fields have exactly the same data types so I'm stuck as to why this is happening

Any help would be greatly appreciated



share|improve this question

closed as off-topic by billinkc, Paul White, RolandoMySQLDBA, Jon Seigel, Michael - sqlbot Nov 9 '13 at 21:12

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)." – billinkc, Paul White, RolandoMySQLDBA
If this question can be reworded to fit the rules in the help center, please edit the question.

Do you know if the package is doing anything beyond just pushing data from one server to the next? Is it doing any type of data transformation at all? Also can you post the structures of both tables here? – Kenneth Fisher Oct 22 '13 at 13:58
As far as I know, there is no data transformation. The structure is basically all nvarchar(4) – pee2pee Oct 22 '13 at 14:16
How are you executing the package? That implies some access, either to a file or within SQL Server; can you copy or export that? Also, I second Mr. Fisher's request to see the CREATE TABLE scripts. – Jon of All Trades Oct 22 '13 at 16:26
Can you view the properties of the job? If so there should be an SSIS step that will tell you where it is. Then using that location you can open it in BIDS. This may give you a lead to find the problem. Or at least more information to share. – Kenneth Fisher Oct 22 '13 at 16:27
Sometimes the Job Properties won't show the package location. If that's the case, you may be able to script the job (CREATE to new query window), which should show the location, even if you can't access it. – Jon Seigel Oct 22 '13 at 16:47