June 10, 2009 at 7:08 am
Hi,
a third party software tries to update it's database structure and get's error 1105 that's says "No disk space is available in a filegroup" ( it's the Primary filegroup ).
As written in BOL the solution should be one of the followings:
1. "Free disk space on the full disk."
There's about 300 GB of free disk space available...
2. "Move data files to another disk."
not necessary because of free disk space
3. "Add files on a different disk."
not necessary because of free disk space
4. "Enable autogrow."
enabled for data (increase by 50 MB unlimited) and log file (increase by 10% unlimited).
Disk space on drive where tempdb resides is about 40 GB ...
The database file is about 300 GB large using SQL Server 2005 Enterprise Edition.
Does anybody has a hint where to look for the cause of this error ?
Thanks for any idea,
Karsten
June 10, 2009 at 7:13 am
June 10, 2009 at 7:19 am
did you mean the Free disk space available on the disk where tempdb resides is 40GB and the size of the Database you are working on is 300GB and is on another Drive/volume.
Can you list your disk configuration and how data/log/system/binaries files are placed/managed.
This is to get a first hand view of what is happening...Also on which Drive does this Database reside and the amount of free space available on this drive itself...
Maninder
www.dbanation.com
June 10, 2009 at 7:23 am
Hi,
joeroshan (6/10/2009)
Have you tried manually growing the file?
yes, that's the way we're working at the moment.
We've grown the database file manually to 350 GB with success.
The question is why has this error occured?
Karsten
June 10, 2009 at 7:27 am
Did you check your error log/event log for timeouts or any other errors?
June 10, 2009 at 7:33 am
Mani Singh (6/10/2009)
Can you list your disk configuration and how data/log/system/binaries files are placed/managed.
Configuration:
Drive C:
* System, SQLServer binaries & system db's (e.g. tempdb)
* ~ 40 GB disk space available
Drive D:
* database data & log file
* ~ 300 GB disk space available
Karsten
June 10, 2009 at 8:41 am
It's possible to have autogrowth enabled, but also have max file size restricting the growth. I think you'd get a different error though.
June 10, 2009 at 9:18 am
Hi,
thanks for your thoughts.
homebrew01 (6/10/2009)
It's possible to have autogrowth enabled, but also have max file size restricting the growth. I think you'd get a different error though.
As I mentioned within my first post MAXSIZE is set to unlimited so this can't be an option...
["enabled for data (increase by 50 MB unlimited) and log file (increase by 10% unlimited)."]
Thanks,
Karsten
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply