existing dts package no longer editable, new one based on it won't work either -
08-05-2005
, 11:32 AM
Hi,
On a system I work on we use DTS Packages to do some simple file exporting
of data.
I recently created a new one. All it does is set up a few global variables,
a db connection
and data transform task to output a text file.
The transform task executes an SP. However when I go to the transform tab I
get
an "invalid object name #Results" error. #Results is a temp table in the SP
used on the source tab.
However I can preview the source and it displays the data which is return
from a SELECT on the
temp #Results table.
We have an existing DTS Package which does virtually the same thing except
it calls a different
SP with different parameters and which works. The SP it uses also uses a
#temp table but when you go to the
transformations tab you get the same error and then a list of 3 options of
what action to take:
remove invalid transformations, change source/destination, remove all
transformation and redo auto-mapping.
So the existing one must of allowed the SP with the #temp table when it was
originally created, but
now, like with my new one it is not allowing it. This is really frustrating
as what should have a been
a couple of hours work has now taken all day.
The SQL machine had SP3a on it, so I tried SP4 since that had some DTS fixes
on it, but still the same
problem.
Any help would be much appreciated.
Regards,
Peter |