If you have a server that has more than one CPU core, you may experience high values of CXPACKET wait types. This is typically due to queries that run in parallel and the real issue is to understand how different versions of a query can impact CXPACKET waits. In this tip we examine how changing a query can impact CXPACKET waits.
2010-07-13
4,058 reads
SQL Server 2005 includes a number of built-in reports to assist you in troubleshooting and measuring performance. In this tip I will cover the Built in SQL Server Performance Reports related to SQL Server Agent within SQL Server 2005.
2010-06-02
5,167 reads
Understanding how to analyze the characteristics of I/O patterns in the Microsoft® SQL Server® data management software and how they relate to a physical storage configuration is useful in determining deployment requirements for any given workload. A well-performing I/O subsystem is a critical component of any SQL Server application. I/O subsystems should be sized in the same manner as other hardware components such as memory and CPU. As workloads increase it is common to increase the number of CPUs and increase the amount of memory. Increasing disk resources is often necessary to achieve the right performance, even if there is already enough capacity to hold the data.
2010-05-24
2,944 reads
Fundamentally, database performance tuning is done for two basic reasons, to reduce response time and to reduce resource usage, both of which can apply for any given situation. Julian Stuhler looks at database performance tuning, and why it remains one of the most important topics for any DBA, developer or systems administrator.
2010-04-30
5,074 reads
2010-02-26
3,504 reads
Do your system contain a time bomb in the code? David Poole looks at some potential situations where you might be experiencing performance issues and delves into why.
2010-02-10
18,087 reads
Useful if you think a SQL statement, Function, or SPROC is taking too long to compile.
2010-02-23 (first published: 2010-02-04)
968 reads
It’s time for us to learn how to diagnose different performance and related problems in SQL Server database. Take a look at the following articles to learn the step by step process that we’ve already carried out so far.
2010-01-12
5,307 reads
Even after you have applied proper indexing along with re-factoring your TSQLs with best practices, some data access routines might still be there, which would be expensive, in terms of their execution time. There must have been some smart ways to deal with these. Yes there are. SQL server offers you some rich indexing techniques that you might have not used earlier. These could surprise you with the performance benefits they possibly offer. Let us start implementing those advanced indexing techniques:
2010-01-08
5,310 reads
In this article, we are going to focus on writing or refactoring the data access codes using the best practices. But, before we start playing the game, we need to prepare the ground first. So let’s do the groundwork at this very next step:
2010-01-04
7,082 reads
By Steve Jones
It’s that time of the month, and I’m late. My apologies. I had a...
By Chris Yates
For decades, enterprises have approached data management with the same mindset as someone stuffing...
Truncate Table Pitfalls Truncating a table can be gloriously fast—and spectacularly dangerous when used carelessly....
Comments posted to this topic are about the item Technological Dinosaurs or Social Dinosaurs?
Comments posted to this topic are about the item DBCC CHECKIDENT
Comments posted to this topic are about the item Distributed Availability Group Health: T-SQL...
What is returned as a result set when I run this command without a new seed value?
See possible answers