Skip to main content

Difference between SQL Handle and Plan Handle

When we execute query select * from sys.dm_exec_query_stats it will show aggregate performance statistics of cached query plans of SQL Server. The details including one row per query statement within the cached plan, and the lifetime of the rows are tied to the plan itself. Details have two column SQL Handle and Plan Handle.

sql_handle :- It  can be used to retrieve the SQL text of the query by calling the sys.dm_exec_sql_text dynamic management function.

select * from sys.dm_exec_sql_text(Sql_handle)

select * from sys.dm_exec_sql_text(0x01000100B73A5B34A021E8660100000000000000)


plan_handle : - This value can be passed to the sys.dm_exec_query_plan dynamic management function to obtain the query plan.

Select * from sys.dm_exec_query_plan ( plan_handle )

Select * from sys.dm_exec_query_plan (0x0500070001C1A15CC0DE4BEA0200000001000000000000000000000000000000000000000000000000000000)




Popular posts from this blog

mongoDB error : aborting after fassert() failure

What to do when facing errors on mongoDB “aborting after fassert() failure” I like errors, in mongoDB this is the first error I faced and luckily many times. This error i faced during restoring name-space on local and restarting db system. I am still searching the exact root cause of this issue but i am able to resolve the current problem through below steps. Remove all relevant namespace files from data-file route path.. Now repair mongo instance using mongod process. mongod --repair ////////// execute command from bin folder path  Then start server using mongd process, if started server successfully then .. mongod  ////////// execute command from bin folder path Restore last backups as normal process. Now check database by connecting mongo shell. Thanks for reading,  Please comment your experience if you faced and also share knowledge if you have better steps to resolve...  

SQL71562: external references are not supported when creating a package from this platform

Last week I got this error from one of developer who was trying to deploy his project from Testing server to SQL Azure QA server. He was using “Deploy Database to SQL Azure” option from SSMS Tool-Task option. After connecting to SQL Azure portal when operation started to deployment below errors occurs. Validation of the schema model for data package failed. Error SQL71562: Error validating element has an unresolved refrence to object xx.dbo.xxxx external refrences are not supported when creating a package from this platform . Reason: The reason of the this error was; some functions of project was dependent on master database and only single database was being deploy to SQL Azure. DACFx must block Export when object definitions (views, procedures, etc.) contain external references, as Azure SQL Database does not allow cross-database external references So, this error was coming. Solution : I suggested him to create those function to locally

How to recover msdb database from suspect mode

 It was Monday 9 th Jun 47 degr. temperature of Delhi-NCR. Temperature was like boiling me and database. When I reached my office( @ 8.45 am) got an alert from one of Server. “MSDB is in suspected mode” At the same time comes in my mind, this issue will boil me today.. I just tried to cool my self through cold drink then connected server from my local system using windows authentication mode..