We have read that sp_getbindtoken will be removed in a future version of SQL Server, future as in after SQL Server 2008. What will be the alternative to getting a unique transaction ID?
The articles that we have read suggest to use MARS instead of sp_getbindtoken, but since our goal is to log the transaction ID for reporting purposes, we don't believe that MARS will solve my problem.
What we need, and have with sp_getbindtoken, is the ability to track changes to all tables and relate the changes using the current transaction ID. This allows us to run a report that shows all records that were changed for a specific operation, even if the change was made in a stored procedure or via a direct INSERT or direct UPDATE statement. This logic is used in our workflow engine.
We are hoping that when sp_getbindtoken is removed, an alternative will exist. We don't like the idea of having to preface all transactions with an update to an application global variable so that we can achive the same result. SQL Server will likely always have an internal method of tracking the current transaction ID, so it seems silly not to expose it when it can be so useful. Either that, or just keep sp_getbindtoken alive forever.
Paul Rony
SplendidCRM Software, Inc.