Sorry if I am late with this but Brent Ozar has very good description of what to do if you nave ability and time for that: http://www.brentozar.com/archive/2009/05/san-multipathing-part-1-what-are-paths/

I would recommend to set up perfmon and profiler monitor for queries that run over 20 sec. (that was the time you’ve mentioned before). Then join results in the profiler...

Tim Walker (5/20/2009)

---

You didn't post your database size. But here are my comments.

Michael...

To be honest, I do not really understand what for you need that information. It is like a question: how many cars are on all highways of the state right...

Is AWE enabled? With 32-bit OS you need to enable usage of memory over 2Gb. Usually, if server has 8Gb doesn’t mean SQL Server is using it.

Also, check article:

VB6 is not the root of the problem. It might be anything from HBA card problem to a new job that runs every 5 sec.

From my personal experience: 20 sec....

Did you try to type "sql server memory counter" in any search engine? The result will give you excellent articles available on the internet:

http://www.sql-server-performance.com/tips/performance_monitor_memory_counter_p1.aspx

http://sqlserverpedia.com/wiki/Memory_-_Performance_Counters

etc….

These articles will...

Detail execution plan on that query will show that it would be better to re-write the query because:

- A.STATUS='A' or A.STATUS IS NULL clause makes impossible to use any index...

Basically, you need to find out WHAT cause the slow query response first. In order to do that you need:

- Run Profiler or manual trace so you could see execution...

I think these are results of precompiled queries that are coming from you front-end application that is written with object-mapping database querying tool like Hibernate. You’d better ask your developers...

No, you can't. I just wonder how you can use that backup even if you can? Tempdb has information that is necessary for current stage of the user’s and other...

Wow, you didn’t say anything about messed up installation and other stuff. Your assumption “Do not add anything to production that is not absolutely necessary” is correct. Thus you should...

There are many problems:

- Cursors;

- Dynamic insert and updates;

- sp_ in the name of the user’s store procedure.

Also, every temporary space, table, execution plan, etc. cleans out every time...

Gail is absolutely right: there are many ways to pull data and testing is the only way to see what is better for you. Also, never ever use SELECT DISTINCT...

Would you like to use command line or GUI? I prefer GUI however I know how to use command line. SSIS is very good tool. Why would not you use...