I have a question to ask about profile tracing. I'm not really good with tracing since I haven't done very much it. Anyway I have a SQL Job that imports data from a file that I run manually sicne it is for testing purposes only. I didn't create the DTS package (one of our developers or the app vendor did) that this Job was scheculded from so I'm not entirely sure what tables it is hitting but I do know the database that it is hitting. I'm getting an error message from SQL stating that the import is trying to insert NULL values into a colum that cannot except Null values but the column name is cut off (cust....) and no table is listed. I've told the developers that SQL doesn't like their file but they are telling me that there is nothing wrong with the file and there is something wrong with the JOB (although I've run this job several time without a problem).
So I need to know how I can create a trace that will show me all the data that is being imported from this file into the database so that I can find out where the problem exists/occurs and point out to them that their file is messed up. Does anyone know how I can create a trace that will allow me to trap all the information that is being imnported from this file.
I don't know if this will help, but the job name it testimportdailyfile(created from a DTS package, not sure which one though since there are several on this server), the database name is testc2cip, and the name of the file that I'm importing from the daily.dat. Is there a way that I can trap all the information coming from this file so that I can see it as is it being imported into the database and nothing else when I run the testc2cip job.