|
-
Jun 2nd, 2005, 11:38 AM
#1
Re: Monitoring SQL Server Connections
You can copy the sp_who and modify it to reduce the number of fields it returns or add a where clause so it will be only for a particular db or app.
Place the modified copy in the concerned db's sp folder and execute from there.
VB/Office Guru™ (AKA: Gangsta Yoda™  ®)
I dont answer coding questions via PM. Please post a thread in the appropriate forum. 
Microsoft MVP 2006-2011
Office Development FAQ (C#, VB.NET, VB 6, VBA)
Senior Jedi Software Engineer MCP (VB 6 & .NET), BSEE, CET
If a post has helped you then Please Rate it! 
• Reps & Rating Posts • VS.NET on Vista • Multiple .NET Framework Versions • Office Primary Interop Assemblies • VB/Office Guru™ Word SpellChecker™.NET • VB/Office Guru™ Word SpellChecker™ VB6 • VB.NET Attributes Ex. • Outlook Global Address List • API Viewer utility • .NET API Viewer Utility •
System: Intel i7 6850K, Geforce GTX1060, Samsung M.2 1 TB & SATA 500 GB, 32 GBs DDR4 3300 Quad Channel RAM, 2 Viewsonic 24" LCDs, Windows 10, Office 2016, VS 2019, VB6 SP6
-
Jun 2nd, 2005, 12:39 PM
#2
Re: Monitoring SQL Server Connections
 Originally Posted by RobDog888
You can copy the sp_who and modify it to reduce the number of fields it returns or add a where clause so it will be only for a particular db or app.
Place the modified copy in the concerned db's sp folder and execute from there.
Another sterling idea!
-
Jun 3rd, 2005, 05:50 AM
#3
Re: Monitoring SQL Server Connections
FYI to all database folks. These two SPROCS that RobDog888 mentioned are pretty neat. I made a couple of modifications to sp_who2, and it is returning the information that I/we need.
Thanks.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|
Reply With Quote