Re: SSIS & Script Transformation (debug vs normal)
- From: awakin <awakin@xxxxxxxxx>
- Date: Wed, 12 Mar 2008 14:47:32 -0700 (PDT)
On Mar 12, 6:18 am, jhofm...@xxxxxxxxxxxxxx wrote:
Hi Anthony,
Can you give more details about what the "transformation script" is
doing?
Usually issues where something works in debug/dev mode but not post
deployment is due to SQL Agent account permissions.
Good luck!
J
The package is pretty simple. Our ERP stores dates in a numeric field,
and we are moving this into a true date field.
In the package
- I have one data-source collecting source data, connected to derived
column (building a placeholder for the new date fields)
- Going into a script transformation the date (output is a date or
null) works is debug mode, but not when ran by sql agent.
- Final output is a SQL table.
I am running SQL Server 2005, 64 bit . I have to use 32 bit drivers to
connect to my data-source. So in SQL Agent - I run my package from the
command line, to call out the 32 bit dts package. Also, I have a proxy
setup with every possible option. I use this proxy across my whole
integration process, without problems. For some reason, this package
has a problem - the main difference - Script Transformation.
Thanks for your response.
r/ Anthony
.
- Follow-Ups:
- Re: SSIS & Script Transformation (debug vs normal)
- From: jhofmeyr
- Re: SSIS & Script Transformation (debug vs normal)
- References:
- SSIS & Script Transformation (debug vs normal)
- From: awakin
- Re: SSIS & Script Transformation (debug vs normal)
- From: jhofmeyr
- SSIS & Script Transformation (debug vs normal)
- Prev by Date: RE: How to handle DTS package when upgrade from sql server 2000 to
- Next by Date: Membership download
- Previous by thread: Re: SSIS & Script Transformation (debug vs normal)
- Next by thread: Re: SSIS & Script Transformation (debug vs normal)
- Index(es):
Relevant Pages
|