|
SQL Server
Frequently
Given Answers
These aren't FAQ answers, they are more like general
guidelines. "What" you should do, rather than "how."
I can't count the number of times I was looking all over for an answer that
turned out to be right in front of me.
1. Read the directions.
2. Check for errors or events that may lead you to the answer.
- Check the Event Viewer system and application logs for
errors or unusual activity.
- Check the SQL Server Error Log - there are some errors
that are written to this log but not the Event Viewer log.
- Check the application's error log if it was written to
have one.
- Turn on Performance Monitor (make sure you've run "diskperf
-y" so that the disk counters show up properly).
- Use SQL Profiler (SQL Trace for 6.5) and capture the troublesome
queries.
- Run DBCCs (when users aren't on) and look for errors.
- Run Update Statistics (when users aren't on) even if auto update stats is
on.
3. Check out the environment.
- Make note of what has changed since the last time
everything was working ok.
- Do you have any non-default SQL configuration options?
- Don't forget those hidden actions caused by triggers.
- What network protocol(s) is the server
"listening" on? What network protocol is the client (or IIS
server) configured to "talk" on? Check out BOL or TechNet for an
understanding of the difference between the types and levels of network
protocols.
- If any other applications are running on your SQL Server
machine, make sure they aren't "hogging" resources.
4. If the above ideas haven't led you to your answer, ask someone.
- When asking for help, be prepared to supply your exact query and exact error.
- Provide the basic information about your
installation. At least give the SQL Server version and service pack level.
- State in plain English what you are trying to accomplish.
- Mention what you've already tried, but don't be offended
when people ask you to check something again.
- Ask a colleague - either one you know directly or someone
in a discussion group or on a web site.
- Ask Microsoft - open a case. This might cost you
money if your company doesn't have a support agreement, but will it cost as much
as not calling?
Back to Top
SQL
Server Directory
How to Troubleshoot a Performance
Problem
Troubleshooting Blocking
How to Move a Database
Get the Latest Service Pack
Misc. Tips and Tools
SQL Server Knowledge Base Articles
Common
SQL Server Answers
SQL
Server and Related Links
Back to Top
Main SQL Server Page
|
