by Global Knowledge Network, Inc.
> View this now
Published on: January 2008
Type of content: WHITE PAPER
Adobe Acrobat (.pdf)
Enter There are many methods for troubleshooting databases. Many people jump straight to a Google search, or run to find the senior DBA who, most likely, has seen this problem before. While these may provide some results, there's no better solution than tracking down empirical evidence as to the cause of a bottleneck or to the identity of the troublesome transaction. In addition to getting real answers (as opposed to trying other people's solutions), you gain a much greater understanding of SQL's inner workings and of how to optimize your database.abstract here.
Upon first hearing the words "empirical evidence," many of you may be immediately dissuaded. Fear not! The tools are at hand, and they are relatively simple to use. A familiarity with logs, monitors, and other built-in programs will ensure that you have a number of research choices when trouble arises.
> View Company Report
> View all content by this company
> Return to Search Results