May 6, 2014 at 4:08 am
Hi Experts,
We have a SQL Server 2008 Standard edition, 8 CPU & 24 GB RAM.
Yesterday I created a maintenance job to rebuild index on 1 table which is 400 GB in size (The indexes on this table are 150 GB in size) . The job ran for an hour and after that the DB server hanged and finally crashed ( I guess).
We had to manually restart the DB server and then restore from backups to bring it to the original state.
Any idea why would the server crash ? The log file on SQL Server and the logs in event viewer have absolutely no errors on them. This is so confusing because I don't understand how to investigate this issue.
The servers data/log (ldf/mdf/ndf) files are stored in a SAN storage but the storage had only 50GB of free space when we ran the rebuild job. Would this have been an issue?
I also got info from SAN team that the SQL server was writing a lot into the SAN drive due which SAN disk ran out of space.
Or could this issue be due to a communication problem between processer and hard disk controller? like the link below (I am pretty sure this is not the case because we never had such problems in the past)
http://www.sqlservercentral.com/Forums/Topic698098-146-1.aspx
Thanks for all your help.
May 6, 2014 at 4:45 am
My first thought was you need to check the max memory setting, make sure it is NOT the default. However the limited SAN space may be the problem.
May 6, 2014 at 5:07 am
Limited SAN space could be culprit. However let us know the detail error message for further investigation.
---------------------------------------------------
"Thare are only 10 types of people in the world:
Those who understand binary, and those who don't."
May 6, 2014 at 5:15 am
Thaks djj and free_mascot for your replies. yes I will try to figure this out by noon.
Any idea how do I go about rebuilding the index on this table ? Do we have to add additional space on the SAN drive? if yes how much space is required? the table is 400 GB so how much space would be required by the rebuild job? any way to calculate this?
May 9, 2014 at 4:10 am
thanks a lot guys problem was confirmed due to SAN running out of disk
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply