July 29, 2013 at 2:46 pm
We are using SSIS, Transfer SQL Server Objects Task Editor to move data from one SQL Server system to another.
A few of the records on the source system have unprintable characters in them. Yes, it would be a goal to clean that up, but since that involves application changes, our current objective is to have the data transferred so it matches exactly between the systems.
It appears on these records that the unprintable characters are not transferring to the target system. Then when something like Data Dude (or whatever they call it now) is used to compare the systems, these records appear as mismatches.
Is there a way using SSIS, to get the data to copy from the source to the target exactly as the data exists?
TIA,
Doug
July 29, 2013 at 2:53 pm
...
Is there a way using SSIS, to get the data to copy from the source to the target exactly as the data exists?
...
In my opinion, this is not the question to ask. I suggest you first look at your SSIS package and see if you can find out where these characters are getting dropped.
For best practices on asking questions, please read the following article: Forum Etiquette: How to post data/code on a forum to get the best help[/url]
July 29, 2013 at 3:04 pm
It's a simple SSIS package with one, Transfer SQL Server Objects, for the tables in the database. We are copying all the tables in the given database.
I don't see anywhere where there are options/parameters we can use to control how the system handles this data.
I am wondering if anyone has had this issue and what they did to resolve it.
July 29, 2013 at 3:28 pm
Check what data types are used both for and input, output, and in betweeen.
For best practices on asking questions, please read the following article: Forum Etiquette: How to post data/code on a forum to get the best help[/url]
July 29, 2013 at 3:40 pm
Yes, I checked that before posting. Everything matches up. It is a varchar(10) column. We've not added any translation or other data manipulation on this column in the SSIS package.
I've seen this happen before, years ago on prior levels of SQL Server, with a SSIS package. We never had a solution.
Just hoping someone has had this situation trying to use a SSIS package and had a solution to get the data transferred exactly as it exists in the source.
July 30, 2013 at 12:47 am
How is the data transferred? Is a data flow involved?
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
July 30, 2013 at 6:01 am
I would transfer the data using the Unicode data type (NVARCHAR)
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply