![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
I have a schedule DTS package that I want to track during execution. I've looked in the "sysdtdpackagelog" table and see an entry in the table about my package. When are entries place in the this table? i.e. when the package completes execution or when the package starts and then updated when the package completes? How can I track the execution of steps within a package while the package is running? I want to create an process/program that run outside of SQL 2000 to track packages that are schedule to during the night or early morning. We have had a couple of case the where it looks like the packages started on time but for some reason they seem to stalled during the night or early morning some times. I've been investigating why this stalling sometimes happens but I have no solution or reason yet. However, stopping and re-starting SQL server then running the package makes everything better. |
#3
| |||
| |||
|
|
Can you not have the package write out to a separate table whenever it reached certain junctures in the package? If you log to SQL Server then you will find entries in msdb.dbo.sysdtssteplog and they will be entered as the task executes. Allan "Larry Bird" <LarryBird (AT) discussions (DOT) microsoft.com> wrote in message news:B0DF86E6-1371-4790-87CE-AE42955843E7 (AT) microsoft (DOT) com: I have a schedule DTS package that I want to track during execution. I've looked in the "sysdtdpackagelog" table and see an entry in the table about my package. When are entries place in the this table? i.e. when the package completes execution or when the package starts and then updated when the package completes? How can I track the execution of steps within a package while the package is running? I want to create an process/program that run outside of SQL 2000 to track packages that are schedule to during the night or early morning. We have had a couple of case the where it looks like the packages started on time but for some reason they seem to stalled during the night or early morning some times. I've been investigating why this stalling sometimes happens but I have no solution or reason yet. However, stopping and re-starting SQL server then running the package makes everything better. |
#4
| |||
| |||
|
|
Is the table msdb.dbo.sysdtssteplog cleaned up once the package is complete? I've looked in this table and found it to be empty. Thanks "Allan Mitchell" wrote: Can you not have the package write out to a separate table whenever it reached certain junctures in the package? If you log to SQL Server then you will find entries in msdb.dbo.sysdtssteplog and they will be entered as the task executes. Allan "Larry Bird" <LarryBird (AT) discussions (DOT) microsoft.com> wrote in message news:B0DF86E6-1371-4790-87CE-AE42955843E7 (AT) microsoft (DOT) com: I have a schedule DTS package that I want to track during execution. I've looked in the "sysdtdpackagelog" table and see an entry in the table about my package. When are entries place in the this table? i.e. when the package completes execution or when the package starts and then updated when the package completes? How can I track the execution of steps within a package while the package is running? I want to create an process/program that run outside of SQL 2000 to track packages that are schedule to during the night or early morning. We have had a couple of case the where it looks like the packages started on time but for some reason they seem to stalled during the night or early morning some times. I've been investigating why this stalling sometimes happens but I have no solution or reason yet. However, stopping and re-starting SQL server then running the package makes everything better. |
![]() |
| Thread Tools | |
| Display Modes | |
| |