sponsored by Global Knowledge
Posted:  02 Jan 2008
Published:  01 Dec 2007
Format:  PDF
Length:  8  Page(s)
Type:  White Paper
Language:  English
ABSTRACT:
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.



Author

Jeff Peters
Instructor ,  Global Knowledge
Jeff Peters is a trainer, network admin, and consultant specializing in Microsoft products. He currently works for Azen Tech, LLC in Metuchen, NJ.



BROWSE RELATED RESOURCES
DBA | SQL Server | Troubleshooting

View All Resources sponsored by Global Knowledge

About TechTarget:

TechTarget provides enterprise IT professionals with the information they need to perform their jobs - from developing strategy, to making cost-effective IT purchase decisions and managing their organizations' IT projects - with its network of technology-specific Web sites, events and magazines

All Rights Reserved, Copyright 2000 - 2014, TechTarget | Read our Privacy Statement