Forum Discussion
Activity monitor - sql queryies behind
- Aug 27, 2021
acim9090 , that's easy, use SQL Server Profiler to trace all SQL statements send from SSMS to SQL Server.
But not all base on query result, e.g. CPU/MEM diagram uses WMI queries to get the values.
Olaf
acim9090 , that's easy, use SQL Server Profiler to trace all SQL statements send from SSMS to SQL Server.
But not all base on query result, e.g. CPU/MEM diagram uses WMI queries to get the values.
Olaf
- acim9090Aug 27, 2021Copper Contributorolafhelper, Any idea why I can't run the store proc?
USE tempdb;
GO
EXEC #am_generate_waitstats
go
Error:
Could not find stored procedure '#am_generate_waitstats'.
Context in ssms is tempdb, where I found this store proc.- olafhelperAug 27, 2021Bronze Contributor
Every object (table, SP) with a name starting with # is a local temporary object and can only be accessed with in the session where the temp object was created.
Example: In SSMS open 2 query windows, in one you create a temp table with
create table #test (id int null); insert into #test (id) values (1);
And now try to query the temp table in the second query window, like
select * from #test;
You get the same error message.
- acim9090Aug 27, 2021Copper Contributor
Thank you olafhelper . This is actually good idea, will try.
I