Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


SQL Server crashes when data drive full?


SQL Server crashes when data drive full?

Author
Message
ken.trock
ken.trock
Old Hand
Old Hand (394 reputation)Old Hand (394 reputation)Old Hand (394 reputation)Old Hand (394 reputation)Old Hand (394 reputation)Old Hand (394 reputation)Old Hand (394 reputation)Old Hand (394 reputation)

Group: General Forum Members
Points: 394 Visits: 1713
Hi. Has anyone experienced this in SQL 2005; that SQL Server goes down when the data or log drive drives are full? I haven't but a couple people in the company have. We're on 9.0.4053 (SP3) which I think is still a supported version.

This doesn't make sense to me. An autogrowth should fail and that be the end of it.

Thanks,
Ken
GilaMonster
GilaMonster
SSC-Forever
SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)

Group: General Forum Members
Points: 47388 Visits: 44399
A full drive shouldn't cause SQL to crash. It'll cause transactions to fail, that's about all.

Check the SQL error log, see what's the last few entries in the log


Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass


ken.trock
ken.trock
Old Hand
Old Hand (394 reputation)Old Hand (394 reputation)Old Hand (394 reputation)Old Hand (394 reputation)Old Hand (394 reputation)Old Hand (394 reputation)Old Hand (394 reputation)Old Hand (394 reputation)

Group: General Forum Members
Points: 394 Visits: 1713
Thanks, not seeing much in the logs. I'm tempted to let the data drive fill up just to see what happens :-D. But our end user folks would be going crazy with alerts, not to mention it's a production DB.
Scott D. Jacobson
Scott D. Jacobson
Old Hand
Old Hand (390 reputation)Old Hand (390 reputation)Old Hand (390 reputation)Old Hand (390 reputation)Old Hand (390 reputation)Old Hand (390 reputation)Old Hand (390 reputation)Old Hand (390 reputation)

Group: General Forum Members
Points: 390 Visits: 1000
So take a full backup of your production database and restore it to a test server. Then let the drives on that machine fill and see if you can recreate the behavior. Good research, maybe you'll find a solution and production isn't harmed by the testing.
durai nagarajan
durai nagarajan
Ten Centuries
Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)

Group: General Forum Members
Points: 1107 Visits: 2771
Scott D. Jacobson (10/23/2012)
So take a full backup of your production database and restore it to a test server. Then let the drives on that machine fill and see if you can recreate the behavior. Good research, maybe you'll find a solution and production isn't harmed by the testing.


Scott,

Hope server crash is something related to a sql service or setting nothing related to DB.

Regards
Durai Nagarajan
Markus
Markus
SSCommitted
SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)

Group: General Forum Members
Points: 1587 Visits: 3680
GilaMonster (10/23/2012)
A full drive shouldn't cause SQL to crash. It'll cause transactions to fail, that's about all.

Check the SQL error log, see what's the last few entries in the log


I agree with Gail, it shouldn't cause it to crash, just won't be able to add new data if trans log or mdf file try to expand. You need to look at the SQL Server log and the Windows event logs to see why SQL Server crashes. There should be details in there.



TheSQLGuru
TheSQLGuru
SSCertifiable
SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)

Group: General Forum Members
Points: 6004 Visits: 8314
1) I suppose the failure of some system action could cause SQL to barf (just a supposition here)

2) SQL 2005 SP3 is unsupported by Microsoft

Best,

Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru at GMail
Meet George Jetson
Meet George Jetson
SSCrazy
SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)

Group: General Forum Members
Points: 2638 Visits: 1393
Gail - what if it were a system database, in particular the master database?

Chris Powell

George: You're kidding.
Elroy: Nope.
George: Then lie to me and say you're kidding.
Markus
Markus
SSCommitted
SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)

Group: General Forum Members
Points: 1587 Visits: 3680
Meet George Jetson (10/26/2012)
Gail - what if it were a system database, in particular the master database?


THe master database will probably never grow. All it holds is logins and records of the application databases. Typically it is under 10mb.



ken.trock
ken.trock
Old Hand
Old Hand (394 reputation)Old Hand (394 reputation)Old Hand (394 reputation)Old Hand (394 reputation)Old Hand (394 reputation)Old Hand (394 reputation)Old Hand (394 reputation)Old Hand (394 reputation)

Group: General Forum Members
Points: 394 Visits: 1713
Truth is, this machine is flakey. Maybe it's tempdb. It was setup by another group with way too many files, 16 on an 8 core box. We've been trying to take it down to 8 files. That may be neither here nor there but the reason we're stuck on 2005 SP3 is that I'm TOLD our server admin team tried to get it up to SP4 but that "it wouldn't take". That the original group put some incompatible software on it that prevented SQL from being updated. As far as I know this original group had only installed database drivers and the like on it so SSIS packages/jobs could pull from other sources.

Thanks,
Ken
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search