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 |
|
EWDBA
2 Posts |
 Posted - 2015-04-02 : 12:46:45
|
So granted I've see this every time my backups run and never really thought anything of it .. until now that I need to monitor the status of the back up ( ie percent complete and other session based metrics )
When a lite-speed backup is kicked off it calls the third party extended stored proc which then establishes a new session and continues to run the backup..
So here is the issue I need to tie the calling session to the extended stored proc session that's created that has the desired metrics
I'm sure this isn't specific to lite-speed but rather any extended proc that makes a separate call
note session 73 is the calling session ( ie SSMS or SQLCMD) and session 84 is the session that the extended proc makes ( which has the session metrics desired)
DatabaseNm SessionID StartDt LoginDt StatusCd LastCommandCd EstimatedCompletionPct EstimatedCompletionDuration
LiteSpeedLocal 73 2015-03-31 17:15:00.413 2015-03-31 17:15:00.413 running UPDATE 0.00 00:00:00:000
master 77 2015-04-01 09:47:03.130 2015-04-01 09:15:19.350 running EXECUTE 0.00 00:00:00:000
msdb 84 2015-04-01 09:47:04.750 2015-04-01 09:47:04.743 suspended BACKUP DATABASE 5.99 00:01:25:230
I've gone through most of all the system table to find someway to connect these two sessions but haven't been able to find a deterministic connection
Any thoughts?
Thanks
-Eric |
|
|
|
|
|
Extended Stored Procs