Hello, all. Just started using SQL 2005 this week, and am migrating some SQL
2000 DTS packages to our new server. These packages are simple flat file
comma delimited source file to SQL table destination packages. Surprisingly,
and sadly; I've noticed once migrated to SQL 2005, my column mappings aren't
retained in my packages. Some of these packages have over 60 column mappings
that must be remapped, and that's no simple task as my source/destination
don't match up 1 for 1 in order.

Microsoft couldn't have overlooked this small, but important detail. Please
tell me there's a way to retain column mappings.

Waiting in San Antonio,

Roz

Hello Roz,

Is there anything special about the transforms? Are they AX transforms or
straight Column --> Column mappings?

One of the things a lot of people including myself will have to "live " with
is that the upgrade will not be possible for some things in complex packages
and in a lot of cases it would be better to redesign from scratch anyway.

Can you tell us about the package that did not migrate and we can see if
we can replicate?

Allan

Hi Allen. The transformations are straight Column --> Column mappings. I'm
not doing anyway Ax transformations, or anything fancy. I have simply have a
flat file that is comma delimited, and an importing into a table. In the
original column mappings exist, of course, but when I migrate the package to
SQL 20005, everything comes over (source, destination connection info, etc)
EXCEPT the column mappings. I'm having to redo them one by one.

Roz


"Allan Mitchell" wrote:

Hello Roz,

I have just migrated a package from 2000 --> 2005 which was a single task
Flat File (Source) to SQL Server and everything including mappings came over.

Were there an errors in the report?

Allan

Allan,

I appreciate your continued assistance. The report and log file (created
during migration) showed no errors. None. The report at the end said
"Success".

I'm truly baffled here.


"Allan Mitchell" wrote:

Hello Roz,

DTS was more forgiving of datatype and sizing mismatches. SSIS screams at
you. Could it be that DTS massages the data in whereas SSIS will not and
therefore omits?

Allan

Made some success. I was at least able to open my SQL 2000 DTS package in
2005 Mgt Studio, under Management...Legacy tree. I know its still in 2000
format, and I haven't truly migrated it to 2005.

Were you able to "migrate" your package, or merely open it in 2005? Of
course, I installed the DTS components package, but it isn't a true migration.

Yeah, I've noticed SSIS thru a bunch of warnings about my data being
truncated upon import. Maybe these warning are what "unmapped" my columns.
Anyway to get around this?

Thanks again Allan.

"Allan Mitchell" wrote:

Hello Roz,

I migrated it using the Wizard. Keeping it as a 2000 package makes sense
in a lot of cases you know.

Did you install the 2000 components so you can edit the package in 2000?

Allan