Why is Historical Oracle Performance Data Important?
DBAs are often blamed for problems unrelated to the database. This article makes the case that a DBA’s strongest defense is access to session-level historical performance data.
Read MoreMost Popular Databases
Understanding the Oracle Library Cache Pin Wait Event
The Oracle library cache pin wait event occurs when the session tries to pin an object in the library cache to modify or examine it. Learn what actions to take to tune for it.
Read MoreDevOps–Collaborating to Improve Application Performance
In DevOps, IT development and IT database production must work together to build and improve application and database performance.
Read MoreThe Great Oracle Trigger Escape
Triggers are an often forgotten, yet critical, piece of code that can end up skewing an otherwise excellent design. Learn how this impacted one company’s performance.
Read MoreToo Many Indexes in SQL Server?
Too many SQL Server indexes create additional overhead associated with the extra amount of data pages that the Query Optimizer needs to go through.
Read MoreHow SQL Server 2012 Uses Indexes
The execution plan selected by the Query Optimizer may or may not make efficient use of indexes, or it may not use indexes at all. The following sections describe how execution plans can use indexes.
Read MoreSide-by-side Upgrade to SQL Server 2012
In a side-by-side upgrade, SQL Server 2012 installs either along with SQL Server 2008 (or 2005) as a separate instance or on a different server. Learn what’s involved in performing this type of upgrade.
Read MoreIn-Place Upgrade to SQL Server 2012
After you start an in-place SQL Server 2012 upgrade there is no simple rollback procedure. Learn what’s involved in performing this type of upgrade.
Read MoreSQL Server Query Hint–USE PLAN N
Sometimes the USE PLAN N query hint is used to solve deadlock issues or other data-related problems. This can provide a quick workaround to keep the system running while the root cause of a problem is found and fixed.
Read MoreSQL Server Query Hint–RECOMPILE
The RECOMPILE query hint is a more granular way to force recompilation in a stored procedure to be at the statement level rather than using the WITH RECOMPILE option.
Read MoreSQL Server Query Hint–OPTMIZE FOR
The OPTIMIZE FOR hint enables you to specify which values you expect to see most commonly at runtime, and it can result in better performance for the majority of the queries.
Read MoreSQL Server Query Hint–MAXDOP
On systems where parallel plans are possible, and in the case of a query where a parallel plan is being generated, using MAXDOP (n) allows the Query Optimizer to use only n workers.
Read More