Slowness with SQL Server after a hardrive array recovery

We are running SQL Server 2005 on a SERVER2008 HP box.  We had a hot swappable drive go bad and replaced it.  Using the HP array recovery process the drive was successfully recovered/rebuilt and the server itself is running problem free.  However, SQL Server has been running Extremely slow ever since the drive was recovered.

Does anyone know if we must do some sort of optimization of our SQL Databases or if we must do a SQL restore after the array rebuild to help with our slowness?

Help...Open to any and all suggestions...
VHM1Asked:
Who is Participating?
 
VHM1Connect With a Mentor Author Commented:
Thanks.  Issue was 2 fold...#1, when the array re-built itself, it set the array settings back to the default values (thus turning off write cacheing).  #2 was that the array software used to rebuild the drive was not set to handle open SQL files and as a result it fragmented things greatly.  Products like disk-keeper should be used to handle the rebuild.

THanks for everyones help.
0
 
Anthony PerkinsCommented:
Have you tried updating stats or rebuilding/reorganizing indexes?
0
 
Eugene ZCommented:
if HP array recovery is completed (how big\fast disks there? what Raid? did you add the same speed size disk as you had?)


... you can try to ran DB maintenance for the affected databases: integrity check; reindex; update stats for start.

also check if you have some slow running queries;
check sql server errors? Event viewer related errors?
check if your HP firmware is up to date

did you reboot the server ?

how is CPU \Memory utilization? any IO errors?
0
Firewall Management 201 with Professor Wool

In this whiteboard video, Professor Wool highlights the challenges, benefits and trade-offs of utilizing zero-touch automation for security policy change management. Watch and Learn!

 
VHM1Author Commented:
Yes, we have done both.  We do that regulary anyway.  They jobs to do these run almost 3-4 times longer since the drive was replaced.

All SQL interaction runs 2-4 times longer since the drive was replaced.
0
 
VHM1Author Commented:
server has been re-booted several times since the successfull rebuild.  Firmware is up to date.  Machine is working fine and showing no errors or SQL errors.
0
 
Eugene ZCommented:
how is antivirus doing? is set to exclude sq server files,etc?

what is CPU /memory utilization on this box ?
can you run sp_configure  to see max dop ?

can you give details "running Extremely "  what is running slow?
0
 
VHM1Author Commented:
Sql jobs that ran for seconds before are now running in 45 minutes to 2 hours.  Example, we do transaction logs each 30 minutes.  They ran for seconds before the drive was replaced, now they run 30+ minutes.

CPU and Memory is normal and good.

What is SP_configure?
0
 
Eugene ZConnect With a Mentor Commented:
are you sure that raid rebuild is complete?  what drive did you put : same as was?
what db (s) set on this drive?

also run xp_readerrorlog from ssms to get sql error log info

sp_configure
http://msdn.microsoft.com/en-us/library/ms188787.aspx
0
 
DBAduck - Ben MillerConnect With a Mentor Principal ConsultantCommented:
Have you stopped SQL Server and defragmented the hard drives that SQL data files are on?  You could have a great amount of fragmentation on the hard drives that could be causing this problem.  I would start there to ensure that the foundation is sound.

Then I would look to see if the Indexes are fragmented (sys.dm_db_index_physical_stats) and if they are I would defragment them.

Then I would chase other ghosts.
0
 
Eugene ZCommented:
cool
0
 
Anthony PerkinsCommented:
Thanks.  Issue was 2 fold...
Excellent!  Now please close the question.  This is how it is done:
Closing
http://www.experts-exchange.com/help/viewHelpPage.jsp?helpPageID=24
0
 
VHM1Author Commented:
My solution is what resolved our specific issue.
0
All Courses

From novice to tech pro — start learning today.