In this article, I will talk about how to display long query lines in SQL Server to fit the Query screen.

For this process. in SQL Server

1. Tools
2. Options
3. Text Editor
4. All Languages
5. We put a tick on Settings -> Word Wrap.

When you perform the operations in the above number in order, you will see the following result.

Good luck to everyone in business and life.

The post Fitting Unfit Codes to the Query Screen in SQL Server first appeared on MSSQL Query.

In this article, I will try to give information about finding the queries that consume the most CPU and Disk IO in SQL Server.

It is very important to find queries that consume CPU, Disk IO in SQL Server.

You can find these queries using the code below.

SELECT @@SERVERNAME AS ServerName,
       @@servicename AS ServiceName,
       DB_NAME(st.dbid) AS [Database Name],
       st.[text] AS [Query Text],
       wt.last_execution_time AS [Last Execution Time],
       wt.execution_count AS [Execution Count],
       wt.total_worker_time / 1000000 AS [Total CPU Time(second)],
       wt.total_worker_time / wt.execution_count / 1000 AS [Average CPU Time(milisecond)],
       qp.query_plan
FROM
(
    SELECT TOP 50
           qs.last_execution_time,
           qs.execution_count,
           qs.plan_handle,
           qs.total_worker_time
    FROM sys.dm_exec_query_stats qs
    ORDER BY qs.total_worker_time DESC
) wt
    CROSS APPLY sys.dm_exec_sql_text(plan_handle) st
    CROSS APPLY sys.dm_exec_query_plan(plan_handle) qp
WHERE DB_NAME(st.dbid) IS NOT NULL
      AND NOT DB_NAME(st.dbid) = 'master'
-- and DB_NAME(st.dbid) = 'msdb'
--or not DB_NAME(st.dbid) = 'msdb' or not DB_NAME(st.dbid) = 'master' and or DB_NAME(st.dbid) = 'model' and or DB_NAME(st.dbid) = 'tempdb'
ORDER BY wt.total_worker_time DESC;

When you run the above code, you will see a result similar to the one below.

As can be seen, the queries that consume the most CPU and Disk IO are shown.

Good luck to everyone in business and life.

The post Finding Queries Consuming the Most CPU and Disk IO in SQL Server first appeared on MSSQL Query.