Profile trace a SQL Job/DTS Package

Hey All,

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.

Thanks,

Pete J.



 
LVL 1
PJan8724Asked:
Who is Participating?
 
Anthony PerkinsCommented:
Your best bet is to add (if it does not have it already) logging to the DTS Package.  
1. Go to DTS Package Properties
2. Select the Logging tab
3. In the Error file enter a file name.
4. Run the package.
5. Take a look at the error log defined at step 3
0
 
CIC AdminCommented:
ac : I don't think he can get to (or knows) the original DTS package.

If that is the case, you may be able to get more info from the job itself.  Have you looked at the job history?  Right-click on the job and choose "View Job History".  When the dialog pops up, check "Show Step Detail" and view the info for step one.  If the job has been failing it should show Failure for the results, and you should be able to get more detailed information than what I assume you are getting, a pop up error when you run the job.

As for using Profiler, you are not going to be able to obtain the data that is being transferred by using this program, only the SQL steps that were used.  I don't know if that is enough for your needs.

Good luck,
Kent
0
 
Anthony PerkinsCommented:
>>I don't think he can get to (or knows) the original DTS package.<<
Good point.  I overlooked that.
0
 
PJan8724Author Commented:
Hey Guys,

Well not the answer I was looking for entirely but your did point me in the right direction.  I finally managed to figure out which DTS package was running, and enabled logging on it.  In the end it turned out that the test enviroment didn't match the production enviroment.  I made a change to the table in question and everything works fine.  Thanks for the help though guys.

Pete J.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.