As a DBA, you probably often find yourself striving or struggling to improve the performance of SQL Server instance queries (might be smaller or complex ones). By default in order to get further analysis on the system's performance you need to perform server side trace along with SYSMON (PERFMON...
Initially I preferred to put this blog post within Performance tuning blog section here, but as it relates to the TSQL script thought this is best place to go. Anyways, if you have a performance problem the foremost option is to find whether the server resources are utilized properly or not, this is...
Whenever a performance issue occurs on the SQL Server database best option for diagnosing and troubleshooting common problems by using publicly available tools such as Profiler, System Monitor (Perfmon), and Dynamic Management Views (DMVs) in SQL Server 2005 (onwards). What to detect? Use SYSMON to detect...
Recently I was involved in one of the Performance Audit exercise at a client's place where they complain about Server CPU is always HIGH and what they have observed is even the physical disk where TEMPDB is located has been used extensively, as they can see spikes from SYSMON counters. So whenever...
Posted to
SQLServer-QA.net - Knowledge Sharing Network (SSQA.net)
(Weblog)
by
Anonymous
on
03-14-2008
Filed under: sql server, perfmon, performance, dmv, cache, buffer, sysmon, tempdb, monitoring, temp tables, worktables, workfiles, ratio
Have you seen the above message within the SQL Server error logs? If not then no need to worry and make sure to continue your performance monitoring tasks. So when to be concerned! It is evident that SQL Server 2005 component handles memory differently as compared to SQL Server 2000 version. As one of...
Posted to
SQLServer-QA.net - Knowledge Sharing Network (SSQA.net)
(Weblog)
by
Anonymous
on
03-07-2008
Filed under: sql server, performance, memory, dmv, windows, 2000, 2005, awe, 64 bit, monitoring, worker threads, paging out, buffers, verison
When it comes to performance, for a DBA indexes are the first one to come to mind in order to fine tune the tasks on the database. In this series we have already covered this huge topic of indexing and how best you can make use of Dynamic Management Views within SQL Server 2005 version that was lacking...
It is an universal truth in the database field that due to the fragmentation and page split the performance will be affected even for a simple [ SELECT <ColumnName> from.... ] type of query. So what you need to check or take action in terms of DBA role, on the execution of queries ensure that columns...
As you are aware DMV - Dynamic management views are very good to provide server-level information and some of them with detailed information on the execution environment of the database engine. Just to introduce about DMVs, there are two types of dynamic management views and functions: Server-scoped...
Posted to
SQLServer-QA.net - Knowledge Sharing Network (SSQA.net)
(Weblog)
by
Anonymous
on
12-21-2007
Filed under: sql server, package, performance, security, dmv, users, view, best practice, public, monitoring, server state
Have you ever asked this question about how do I identify the queries that worth tuning? The simple answer it is neither easy or hard to obtain such information if you have managed your SQL Server by deploying industry best practices (wherever possible). Then it comes what kind of practice you should...
It is worth mentioning the valueable query I have been through when referring to Technet Magazine, the following query has given me useful information in finding out what are my top 20 most expensive queries that are consuming most of disk I/O (read & write). November2007 magazine refers as follows...
Posted to
SQLServer-QA.net - Knowledge Sharing Network (SSQA.net)
(Weblog)
by
Anonymous
on
11-15-2007
Filed under: sql server, performance, microsoft, technet, dmv, top, tsql, reads, system resources, expensive query, identity, writes