Re: DTS bug (?): Data Driven Query Task incorrectly replaces empty strings with NULL.

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: John Peterson (j0hnp_at_comcast.net)
Date: 06/22/04 

Date: Tue, 22 Jun 2004 05:38:53 -0700

Thanks Mark! But I *really* need to differentiate between NULLs and empty strings -- I
can't have them all be NULL or all be empty strings. I'm *very* surprised that the Data
Driven Query Task behaves this way. It seems to propagate *other* NULLs correctly,
including NULL strings.

"mark" <mark@remove.com> wrote in message
news:c6TBc.22$Nx2.9@newsfe3-win.server.ntli.net...
>
> "John Peterson" <j0hnp@comcast.net> wrote in message
> news:OvBMir9VEHA.1012@TK2MSFTNGP09.phx.gbl...
> > (SQL Server 2000, SP3a)
> >
> > Hello all!
> >
> > I have a DTS package that uses the Data Driven Query Task (DDQT) to invoke
> a stored
> > procedure on the Insert action (that's the only action that's defined).
> My source table
> > has a column that I'm using as the value to one of the parameters to the
> stored procedure.
> > Sometimes I have explicit NULLs in this column, sometimes I have an empty
> string ('').
> >
> > For some reason, going through DDQT is *always* converting my empty
> strings to NULLs when
> > passing the value into the stored procedure. Is there any way to retain
> the original
> > value (empty string)?
> >
> > Thanks!
> >
> > John Peterson
> >
> this happened to me - didnt fix it but i was advised to change nulls using
>
> UPDATE SomeTable SET col1 = COALESCE(col1, ''), coll2 = COALESCE(col2, ''),
> ... WHERE col1 IS NULL OR col2 IS NULL etc using query analyzer - not ideal
> but an option
>
>
> mark
>
>
>

Relevant Pages