Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
With some reason my sql database file exploded to become over 88 GB and i can’t see a reason why. i run few scripts to search for large tables, found nothing to be too big. i also tried to run shrink database (which did nothing) and shrink files (which return an error).
has anyone has any idea what else i can do?
Thanks.
First thing I’d check (if you’ve already checked the table and index sizes and still see a big difference) is the file properties.
In SQL Server Management Studio, go to the Object Explorer, right click on your database in question and do “Properties”, and then go to the “Files” tab.
What files do you have? What are their settings, especially the “Autogrowth” settings?? If a data file gets close to filling up, SQL Server will expand it, in a way defined in those settings – if you define that 50GB should be added to the file, and the disk space is available, SQL Server will happily oblige and do so – even if it needs just a few hundred extra bytes.