query: Time-based workflows and triggered transactions
positive_passages.docid: 151529
positive_passages.text: Time Dependant Workflows and transactions
negative_passages.docid: 129641
negative_passages.text: Simple Mode - Is using checkpoints to truncate the transaction log a bad practice?
negative_passages.docid: 155978
negative_passages.text: SQL Server sys.dm_tran_active_transactions long running transaction worktable
negative_passages.docid: 44786
negative_passages.text: Primary key for link/junction table with time-dependent data
negative_passages.docid: 78332
negative_passages.text: Speed of curated data calls in Version 10
negative_passages.docid: 74650
negative_passages.text: Monitoring progress of long calculations
negative_passages.docid: 14069
negative_passages.text: Niceness and Priority of Processes
negative_passages.docid: 66981
negative_passages.text: Asynchronous Triggers in SQL Server 2005/2008
negative_passages.docid: 65413
negative_passages.text: Splitting a transaction difficulty
negative_passages.docid: 110633
negative_passages.text: When to use Windows Workflow Foundation?
negative_passages.docid: 97983
negative_passages.text: Implementing the "earn resource every N seconds" mechanism common to F2P games
negative_passages.docid: 31706
negative_passages.text: Should there be a Transaction for Read Queries?
negative_passages.docid: 146399
negative_passages.text: Database design for products with bundles of products
negative_passages.docid: 128421
negative_passages.text: How do distributed transactions work (eg. MSDTC)?
negative_passages.docid: 129822
negative_passages.text: Execution order of event receivers and workflow on a list
negative_passages.docid: 38070
negative_passages.text: Implementation of a "hits in last [second/minute/hour]" data structure
negative_passages.docid: 61941
negative_passages.text: PostgreSQL: Immutable, Volatile, Stable