Printable View
Hi All,
I have a DTS package that is transfering data from SQL Server 2000 (SP3) to Sybase SQL Anywhere 5.0 database. The package fails saying that a field cannot be null. I preview the data from the query and the data is in the field and I check test the transformation and the data is there, the SQL Server data type is INT and the sybase data type is varchar(30). I'm stumped, any help would be appreciated.
Did you query the table to see if there is any null value, test transformation in dts designer does not retrieve all rows. If you execute the step then it will run for all rows.
Also convert int to varchar(30) when you query from the sql table.
I have tried actually changing the data type on the field in SQL Server to varchar(30) to no effect. Since this is in a development environment I only have one record in the table so the NULL value is not an issue. Any other suggestions??????
thanks
Check whether the columns are mapped correctly. What kind of transformation are you using?
I am using column copy, and I have a one to one transformation. I test each transformation and the data is written to a text file for each column. Something is getting screwed up on the Sybase end. Should I do all of the columns in a single transformation??????
What driver are you using for Sybase?. Sometime using different driver helps if you have a choice.
Do you have any fields where you are explicitly trying to insert Null during the transformation? Defaults and auto-increment (identity) fields get auto-populated if you fail to insert anything into the column. However, if you try to explicityly insert Null, auto-increments and defualts are triggered, and it tries to insert Null causing the error that you see.
At least, SQL Server works that way. Sybase might also.
Ah, a moment of inspiration. The column that was giving me the error message wasn't actually where the problem was. There is an activity code column that I was using a code that was not listed in the activity table so it that constraint was actually violated. It does seem weird that that wasn't the error message I received.
Thanks for the help