Incoming SQL Server data all has nulls - how to handle that?

Incoming SQL Server data all has nulls - how to handle that?

Post by YmlsbEBzZW » Wed, 24 Aug 2005 14:31:07



I am trying to transfer one SQL Server database into a new one. The old one
supported nulls on every colum, and the new one, well, doesn't.

In order to use DTS, do I have to make every transformation a ActiveX script
that checks for nulls and uses the default value for the column if it finds
one in the sporce column? Or is there a global way to do that?

Thanks!
 
 
 

Incoming SQL Server data all has nulls - how to handle that?

Post by Allan Mitc » Wed, 24 Aug 2005 14:47:55

There is no Global way of doing this in DTS i.e. replacing all nulls in all
columns with a value as what would that value be? The same in every column
of every table?

Unfortunately you will have to do this the "Long Hand" way.




" XXXX@XXXXX.COM " < XXXX@XXXXX.COM > wrote

 
 
 

Incoming SQL Server data all has nulls - how to handle that?

Post by YmlsbEBzZW » Thu, 25 Aug 2005 04:35:12

Hi, Allan.

The value would be the default value for the column, just like if I inserted
a row any other way. If I use the longhand method (checking for nulls and
skipping the value if it is null) then that default value is what is
populated. It just makes sense that there should be a default mechanism for
handling that.

If there isn't ... well ... that's just silly!

S