September 4, 2015 at 12:07 am
Comments posted to this topic are about the item Open Transactions
September 4, 2015 at 12:13 am
This was removed by the editor as SPAM
September 4, 2015 at 1:43 am
Nice question - BOL says that sysprocesses will be removed from future versions and to use sys.dm_exec_connections, sys.dm_exec_sessions, and sys.dm_exec_requests instead (https://msdn.microsoft.com/en-us/library/ms179881.aspx). That's what I love about QOTD - I now know, from looking for an answer, a new thing. Cheers 🙂
September 4, 2015 at 5:44 am
In SQL Server 2014, for finding number of opened transactions you can still use these two DMVs:
sys.dm_tran_session_transactions, see https://msdn.microsoft.com/en-us/library/ms188739.aspx
sys.dm_exec_sessions, see https://msdn.microsoft.com/en-US/library/ms176013.aspx
In DMV sys.dm_exec_connections is column with number of opened transactions not included, see:
September 4, 2015 at 8:24 am
PB_BI (9/4/2015)
Nice question - BOL says that sysprocesses will be removed from future versions and to use sys.dm_exec_connections, sys.dm_exec_sessions, and sys.dm_exec_requests instead (https://msdn.microsoft.com/en-us/library/ms179881.aspx). That's what I love about QOTD - I now know, from looking for an answer, a new thing. Cheers 🙂
For the most part those DMVs work in replacing sysprocesses. Part of the reason sysprocesses is still around is this connect item:
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
September 4, 2015 at 8:32 am
SQLRNNR (9/4/2015)
PB_BI (9/4/2015)
Nice question - BOL says that sysprocesses will be removed from future versions and to use sys.dm_exec_connections, sys.dm_exec_sessions, and sys.dm_exec_requests instead (https://msdn.microsoft.com/en-us/library/ms179881.aspx). That's what I love about QOTD - I now know, from looking for an answer, a new thing. Cheers 🙂For the most part those DMVs work in replacing sysprocesses. Part of the reason sysprocesses is still around is this connect item:
The plot thickens.....:-D
September 5, 2015 at 5:52 pm
Thanks for this question.
Only an easy one because I have had a problem of open transactions for a backup and I have found the answer in a MSDN forum ( Nothing in the SQL Server Central forums , but maybe my search was not done in the correct way ... )
September 6, 2015 at 1:12 am
Thanks for the question, I am using this sys table occassionally.
Thanks & Best Regards,
Hany Helmy
SQL Server Database Consultant
September 7, 2015 at 1:22 am
It's amazing how long it's been an issue and still hasn't been fixed
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
September 7, 2015 at 1:41 am
Thanks for the question.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
September 8, 2015 at 3:02 pm
PB_BI (9/4/2015)
Nice question - BOL says that sysprocesses will be removed from future versions and to use sys.dm_exec_connections, sys.dm_exec_sessions, and sys.dm_exec_requests instead (https://msdn.microsoft.com/en-us/library/ms179881.aspx). That's what I love about QOTD - I now know, from looking for an answer, a new thing. Cheers 🙂
Thanks for the heads up about future versions.
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply