Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2003-07-30 : 07:53:26
|
| daylinda writes "Our database data and log files are in separate drives in the server. I just increased my log file and then realised that the remaining space is only 33MB on that drive.Infoe:\ DB Data - 11000MB ; capacity=40GB g:\ DB Log - 2500MB ; capacity=3GBAt the moment I didnt get any performance complain from the clients. What is the ideal free disk space that i should have for my g:\ drive? Does this affect SQL servers performance at all?SincerelyDaylinda" |
|
|
X002548
Not Just a Number
15586 Posts |
Posted - 2003-07-30 : 10:30:52
|
| Have you set the log to autogrow? If so it's only a matter of time..How many logs do have stored on the drive?What's your recovery model?When do you take a full backup?Can you archive some data of to the 40 gb drive?Brett8-) |
 |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-07-30 : 12:46:40
|
| The lack of free disk space on that drive will not affect performance. But once you run out of space due to the transaction log growing, all users will receive errors when trying to use that database.Ideal free disk space should be around 20%, but that's just my opinion. Here we alert when the free disk space drops below 20%.Tara |
|
|
|
|
|
|
Very low free (disk) space against performance