Most people have heard the suggestion to monitor a SQL Server from another machine because Profiler and Sysmon consume a lot of resources. Monitoring a server locally also introduces a Heisenberg uncertainty principle type of problem where the act of measurement alters the state of what is attempting to be measured.
I heard a SQL Server MVP making a case for not monitoring remotely because of the network bandwidth demands. Are there situations where monitoring should be done locally Is there an exception to the rule of using another machine to monitor
SQL Server Profiler and Sysmon monitoring local vs. remote
Hot Topic
- Using Lookup task
- Stored Procedures and SSIS Web Service Task
- URGENT! - - Unable to connect to SQL 2005 Server
- Stored Procedure Wizard
- How can update specific column in existing table
- Using a Case to decide on the join statement?
- Report/query parameter default values
- Maximum Conversation timer interval
- automatically expand id spec node in diagram modeler
- Question about Hyperlink
SQL Server
- unable to send mails through sql server2000
- SQL Server 2005 SP1 Webchat: March 22nd 9:00 am PST
- Scripting: How to customize? And Why not Level 7.0
- Thread was being aborted
- Concatenate field based on unique id.
- Can't connect to data source
- SSIS in MSSQL 2005
- Can't Create New Database on Device via ActiveSync
- Is it possible to change the operator of an expression at run time?
- How to import files via HTTP in SSIS
SQL Server Profiler and Sysmon monitoring local vs. remote
DLdfrd
If network traffic becomes an issue then probably SQL Server is generating too many trace events. In such cases it is strongly recommended that you switch to server side file trace, instead of using rowset (Profiler) trace.
Performance counters should not generate too much traffic since usually we are collecting them on relatively large intervals. Using PerfLib (Perfmon, sysmon) is better than using sys.dm_os_performance_counters (sysperfinfo) since all related data structures in SQL Server process are optimized for PerfLib.
Thanks, Ivan