June 9, 2011 at 3:24 pm
If I'm not having the exact same problem reported in this thread, it's certainly very close. The circumstances are different, but I'm getting an 1105 when there are clearly no space issues. In fact, I can cut and paste the bullet points directly:
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).
The differences are minor. I have 7TB free instead of 300GB and in my case autogrow is turned off for the database in question. The system databases all have autogrow with unlimited growth and plenty of space. All of the databases are on a 10TB drive (SAN LUN actually) and like I said, there is just over 7TB free.
For some reason that I can't explain, the vendor has told us to keep autogrow off and to use multiple data files. They said not to exceed 16GB, but that they prefer 8GB. At present the data is 260GB and has roughly 15 GB of space available. The database is now up to 31 data files and I get the 1105 when I try to add another one.
Could not allocate space for object ‘sys.sysfiles1’.’sysfiles1’ in database “MyDB’ because the ‘PRIMARY’ filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup. (Microsoft SQL Server, Error: 1105)
I have 7TB free, but get an 1105 trying to add another 8GB data file. That just isn’t right.
June 10, 2011 at 3:13 am
A couple of things. You can get this error if the drive that TempDB is on happens to be full or if its Primary filegroup is at its max growth limit. Check that first.
Second, when you checked this database's files & filegroups, did you verify that they didn't have a max size set? That's the next thing that prevents a db from growing, despite autogrowth settings.
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply