Tag Info

New answers tagged

1

On server side trace DURATION is the total execution time (in ms) of a query. CPU column will provide you time on CPU (total of one or multiple CPUs). While DURATION - CPU = IO Time So If RPC-Completed time for single procedure call or total time is according to benchmarks then problem could be on network side. Where is actual problem. To get this you must ...


0

I think during installation, you have missed to select the Management Tools-Complete from shared features list. You can open SQL Server Installation Center again New installation or add features to an existing installation After afew screens on "SQL Server Feature Installation" Check "Shared Features -> Management Tools-Complete" Follow the rest ...


0

Unfortunately, there are no settings in SQL Profiler that will display the values the way you want them displayed with your insert .. values statement or any other similar statements. But, by using SP:StmtCompleted and SQL:StmtCompleted you should be able to see when the values are being assigned to the parameters. So you'll have an entry something like ...


1

Pretty much a WAG because you haven't shown EXPLAIN (BUFFERS, OUTPUT) data, but: select id from demo_bbb b; -- database query time: ~26ms If you're on 9.2 or newer this probably did an index-only scan on the unique index used to implement the primary key constraint. Given the latter times that's the most likely case; if it'd done a seqscan (as it would on ...


1

Use a server-side trace, not Profiler. Both have an impact on throughput, Profiler much more so. ClearTrace is a great tool for offline analysis of the trace files. To answer question 1), you connect to the instance not the node. Question 2), you obviously need to gather data from the node the instance is currently running on.



Top 50 recent answers are included