|
database
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Service Broker Conversation TimerHow is Conversation Timer () Timeout = 60; handled internally? Does each
call start a new system timer? Or is one time used that always waits for the "least" time for all waiting conversations? TIA -- William Stacey [MVP] Conversation timers are implemented inside SQL based on internal worktables.
They do not use system resources (timers, handles, threads etc) and are designed to scale up (millions). Timers are persisted into the database and they will do fire after failover (clustering or mirroring), database restore/attach, server restart etc. They are not designed, however, for high accuracy. -- Show quoteThis posting is provided "AS IS" with no warranties, and confers no rights. HTH, ~ Remus Rusanu SQL Service Broker http://msdn2.microsoft.com/en-us/library/ms166043(en-US,SQL.90).aspx "William Stacey [MVP]" <william.sta***@gmail.com> wrote in message news:O5V1Rcx5FHA.268@TK2MSFTNGP10.phx.gbl... > How is Conversation Timer () Timeout = 60; handled internally? Does each > call start a new system timer? Or is one time used that always waits for > the "least" time for all waiting conversations? TIA > > -- > William Stacey [MVP] > > > Thanks Remus. I was hoping it was not system timers. Can you use a
datetime instead of seconds? Or you have to do the conversion to seconds manually. Cheers! -- Show quoteWilliam Stacey [MVP] "Remus Rusanu" <Remus.Rusanu.NoSpam@microsoft.com.nowhere.moon> wrote in message news:uhqdbFy5FHA.884@TK2MSFTNGP14.phx.gbl... > Conversation timers are implemented inside SQL based on internal > worktables. They do not use system resources (timers, handles, threads > etc) and are designed to scale up (millions). > Timers are persisted into the database and they will do fire after > failover (clustering or mirroring), database restore/attach, server > restart etc. They are not designed, however, for high accuracy. > > -- > This posting is provided "AS IS" with no warranties, and confers no > rights. > > HTH, > ~ Remus Rusanu > > SQL Service Broker > http://msdn2.microsoft.com/en-us/library/ms166043(en-US,SQL.90).aspx > > > "William Stacey [MVP]" <william.sta***@gmail.com> wrote in message > news:O5V1Rcx5FHA.268@TK2MSFTNGP10.phx.gbl... >> How is Conversation Timer () Timeout = 60; handled internally? Does each >> call start a new system timer? Or is one time used that always waits for >> the "least" time for all waiting conversations? TIA >> >> -- >> William Stacey [MVP] >> >> >> > > Seconds only, sorry. Of course you can always use DATEDIFF(second,
GETDATE(), @datetime) to obtain the seconds left until any datetime. -- Show quoteThis posting is provided "AS IS" with no warranties, and confers no rights. HTH, ~ Remus Rusanu SQL Service Broker http://msdn2.microsoft.com/en-us/library/ms166043(en-US,SQL.90).aspx "William Stacey [MVP]" <william.sta***@gmail.com> wrote in message news:%23OtKxf05FHA.1188@TK2MSFTNGP12.phx.gbl... > Thanks Remus. I was hoping it was not system timers. Can you use a > datetime instead of seconds? Or you have to do the conversion to seconds > manually. Cheers! > > -- > William Stacey [MVP] > > "Remus Rusanu" <Remus.Rusanu.NoSpam@microsoft.com.nowhere.moon> wrote in > message news:uhqdbFy5FHA.884@TK2MSFTNGP14.phx.gbl... >> Conversation timers are implemented inside SQL based on internal >> worktables. They do not use system resources (timers, handles, threads >> etc) and are designed to scale up (millions). >> Timers are persisted into the database and they will do fire after >> failover (clustering or mirroring), database restore/attach, server >> restart etc. They are not designed, however, for high accuracy. >> >> -- >> This posting is provided "AS IS" with no warranties, and confers no >> rights. >> >> HTH, >> ~ Remus Rusanu >> >> SQL Service Broker >> http://msdn2.microsoft.com/en-us/library/ms166043(en-US,SQL.90).aspx >> >> >> "William Stacey [MVP]" <william.sta***@gmail.com> wrote in message >> news:O5V1Rcx5FHA.268@TK2MSFTNGP10.phx.gbl... >>> How is Conversation Timer () Timeout = 60; handled internally? Does >>> each call start a new system timer? Or is one time used that always >>> waits for the "least" time for all waiting conversations? TIA >>> >>> -- >>> William Stacey [MVP] >>> >>> >>> >> >> > >  |
|||||||||||||||||||||||
Other interesting topics