January 9, 2009 at 5:13 am
Hi,
Please forgive me I am quite new to this. I have been playing around with SQL server 2005 and noticed that one of my drives (E: ) was running low on space.
I therefore decided to drop one of my databases to clear a bit of space up. However, once I did this the amount of free space on the disk did not change. The ldf, mdf, ndf files have been deleted so am I a bit puzzled on why this is happening.
I am sure that I am missing something quite fundamental but at the moment I can't see it.
Would anyone be able to help?
Cheers,
Samuel
January 9, 2009 at 5:47 am
What were the size of the database files? Specifically the MDF and LDF? In some instances I know that people have split their MDF and LDF files across two different drives for space reasons (as well as for recovery depending how things are set up). It depends on what you need for database performance.
When we ran into size problems we moved MDF and LDF over to a separate drive away from the primary SQL Server drive. We also do a nightly full database back up that was sopping up space and move that to a third drive.
***************
wnylibrarian
Buffalo, NY US
January 9, 2009 at 5:54 am
What was the size of those files?
Check if windows didn't grow the paging file.
Also temp files might have gobbed it back up.
There are 12s of explanations, especially on the system drive.
January 9, 2009 at 5:59 am
Hi,
The files I removed should roughly be the size of:
CDR_200810.MDF = 1,000,000 KB
CDR_200810_log.LDF = 16,000,000 KB
CDR_200810FILE.NDF = 600,000,000 KB
So they are big files. Also I am fairly sure that should solely be on this drive (nothing shared anywhere else). I have looked at my notes and I don't see where I have gone wrong as dropping the DB has deleted these files and should therefore free space on this server.
Like I said I am quite new to this so I'm assuming that I have made a clumsy mistake somewhere.
Cheers,
Sam
January 9, 2009 at 6:03 am
Am I reading right, 617 GB???
Assuming the drop succeeded, that might be some windows error.
Have you tried rebooting the server?
January 9, 2009 at 6:08 am
Are you sure those files aren't simply sitting in the trash bin?
--Jeff Moden
Change is inevitable... Change for the better is not.
January 9, 2009 at 6:13 am
They shouldn't, unless manually deleted.
But they could be part of some undelete trash can.
January 9, 2009 at 6:18 am
Jeff Moden (1/9/2009)
Are you sure those files aren't simply sitting in the trash bin?
Me thinks they are a mite big for the recycle bin, but I may be wrong. :w00t:
Samuel - I'm a bit confused how a database this size could be clogging up space. 🙂 I am wondering though how it could be that big and not be valuable in some way. Hard to believe that a simple drop is the answer here but this doesn't answer your question.
The only time that drop database does not delete the files is when the database was offline to begin with. Was that the case with yours? If so, you would have to physically delete them by browsing to the directory. Have you verified that they are indeed gone? Stupid question I know but have to ask. 🙂
David
@SQLTentmaker“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot
January 9, 2009 at 7:33 am
Ninja's_RGR'us (1/9/2009)
They shouldn't, unless manually deleted.
How else would they be, Remi? 😉 And, what else can you think of that would cause these symptoms? :hehe:
--Jeff Moden
Change is inevitable... Change for the better is not.
January 9, 2009 at 7:44 am
Hi,
Thanks for your concern but the DB I dropped was not that important and the data is present and easily accessible on other servers (and has also been backed up). In addition, nobody is using this DB anymore (hence the reason why it could be dropped). As I am new to this I have not been given anything that is considered of high importance.
When I dropped the DB i did look to see if the files have been removed physically (which they have) and also checked the recycle bin (files are not there either).
The only thing that I can think of is a windows error due to the size of the DB? However, thought I would post on here to see if anyone else had any thoughts (I would rather not resort to rebooting the server is possible).
Cheers,
Sam
January 9, 2009 at 7:59 am
Jeff Moden (1/9/2009)
Ninja's_RGR'us (1/9/2009)
They shouldn't, unless manually deleted.How else would they be, Remi? 😉 And, what else can you think of that would cause these symptoms? :hehe:
I already answered that!
Seems weird but I've seen errors like this where everything was deleted but the available size didn't show it (bad driver for the drive in my case). Only a reboot did solve the issue.
I was under the impression that once you DROP a DB, that the files are DELETED, FOREVER. (not witstanding a good undelete APP).
Please correct me if I'm wrong :hehe:.
January 9, 2009 at 9:53 am
BWAA-HAAA!!! ...
... "It depends". 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
January 12, 2009 at 3:56 am
Hi,
Sorry guys turns out that the problem was not to do with me. A user was running a stupidly large query on one of the other DB's which was eating up space. Should of spotted it sooner apologies!
Thanks for your help!
Cheers,
Sam
January 12, 2009 at 4:52 am
600 GB large???????????
January 12, 2009 at 9:57 am
Glad it worked out
but yeah, a user query can cause +600GB when you -600GB on the drive? WOW...
CDR_200810.MDF = 1,000,000 KB
CDR_200810_log.LDF = 16,000,000 KB
CDR_200810FILE.NDF = 600,000,000 KB
Viewing 15 posts - 1 through 15 (of 21 total)
You must be logged in to reply to this topic. Login to reply