Hello, I have problems with XP Sp2:

After Windows XP Sp2 was installed, no tested database
can successfully be transformed. If I deinstall SP2, the
databases can be transformed. The tables are transformed
with "Copy Columns" from a database into another empty
atabase on the same server. With some tables an unknown
error -2147467259 appear.

If the option "UseFastLoad" is False, then the tables can
be transformed. But some Tables need an Identity_Insert,
so this option cannot generally be set.

Does someone has the same problem and knows a solution?

YeeHa! join the club. I posted here a month ago and
didn't get much response. Looks like this problem has
caught up with a number of folks now. I REALLY wish MS
would address this!!!!
However, in the mean time, we have isolated the problem
to tables that have Text fields in them. Ergo, our
solution has been to remove the Text field from the
Source and transformation(s) of the DataPump task, and
then perform a DataDrivenQuery immediately afterwards to
update the offending Text (type) column. It ain't
pretty, and it sure doesn't do much for performance, but
it has been fairly effective. I'm in much the same boat
as you though, in that I need to do an Identity Insert.
Lets scream a little louder and see if we can get some
help.

I have the same problem. Thank you both for the information. I
thought I was going crazy! A customer upgraded to XP SP2 and my DTS
package stopped working. Have either of you officially reported
this to Microsoft yet? I am going to have a problem using the
workaround you are using Josh. This means I will need a fix from
Microsoft

Anyhow, let me know if this is reported already to MS. I could find
nothing on their website.

-Joey

"josh" <smith-josh (AT) aramark (DOT) com> wrote

I posted a solution to this problem which does not involve removing anything
a few weeks back.

The TEXT attribute has no value stored within so is failing on the insert.
UPDATE all, what appear to be empty, TEXT attribute values to either NULL or
''

This is maybe not a DTS issue rather an MDAC/ driver type issue.

I shall see if I can get an answer

--
--

Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.konesans.com - Consultancy from the people who know


"Joey E." <joeyebright (AT) decadesoftware (DOT) com> wrote