Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
SamC
White Water Yakist
3467 Posts |
 Posted - 2003-01-22 : 08:48:09
|
| I've got a DTS script running to read email, another to send email.The scripts have a couple of error logging commands like:DTSPackageLog.WriteStringToLog "StorePOP3Email Err=" & err.descriptionI'm having some problems even opening the log file now - I presume it's the size of the "package" log file. I have no idea how to check the size of this file. It's not under "SQL Server Logs".Being unable to open the DTS Package Log, or know it's size, I'm ready to delete the DTS package(s) and re-create it (them) on the assumption that this will delete the old DTS log file and create one new.Before I do this, is there any comment on whether I've got this right or wrong ?Sam |
|
|
KnooKie
Aged Yak Warrior
623 Posts |
Posted - 2003-01-23 : 08:07:28
|
| Can't exactly help with your problem as is but is there some way you can write the errors to a table instead of a log file ?===========Paul |
 |
|
|
SamC
White Water Yakist
3467 Posts |
Posted - 2003-01-23 : 08:20:49
|
| Thanks, I'll consider that as an alternative. I suppose I could build a table to track DTS problems. At least I'd know where to look for the error and manage the size better.Is it common practice to log DTS messages in a table?Sam |
|
|
|
|
|
|
Right way to track DTS with Log file