Error 1105: - the ''PRIMARY'' filegroup is full

Question

Post reply

Error 1105: - the ''PRIMARY'' filegroup is full

Navi Toor

SSC Veteran

Points: 227
More actions
January 3, 2007 at 1:48 am

#170900

Hi, wondering if somebody can help or point me in the right direction. (Please note I have none to limited knowledge of SQL which probably won't help).
I have encountered error on 1105 for an SQL database on our SQL 2000 server running Biztalk. Now doing research I have found that this can be caused by low disk space, which would make sense because there is only 4KB free on the drive.
Now that makes sense to me, however, what is concerning is that this DB is growing at a ridiculous rate, any space we free up on the dirve it eats up. we managed to clear 70MB and it grew into that within 5 minutes.
From what I have been told this database was in the 20MB region for size before xmas and now its 27.5GB.
Anyone have any ideas on what could cause or resolve this?
December 20, 2015 at 11:11 pm

This was removed by the editor as SPAM

Viewing 8 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic. Login to reply

Minaz Amin SSChampion Points: 11052 More actions · Answer 1

Hi,

What is the version of SQL Server ?

Unplanned growth of the Data or Transaction log can take up space in the disk. Check if the autogrow option for both Data and log are not set * By percent * .

You can see this by selecting Database->properties->Data files tab and Transaction log tab.

Please refer the following links for more information:

http://support.microsoft.com/kb/305635/

Regards,

Minaz Amin

"More Green More Oxygen !! Plant a tree today"

MohammedU SSCoach Points: 19644 More actions · Answer 2

Post the details of your data file and log file size with used and free space info.

What is the recovery model of the db?

Check if there is any table growing faster than you guys imagined using the code from the following link...

http://vyaskn.tripod.com/code/sp_show_huge_tables.txt

If some of your tables are growing faster than you thought then if possible archive and purge them if not you may need to add more space to the disk...

To resolve this issue withou a down time you can create new to a different drive by adding new file to PRIMARY FILGROUP...

MohammedU
Microsoft SQL Server MVP

Manoj Srivastava SSC Journeyman Points: 77 More actions · Answer 3

Make sure that the database has been setup for unrestricted file growth. Sometimes when you restrict the file growth and the file size reached its limit, you may get this error message when trying insert / updates on database.

Hope this helps

Manoj

Anil-465051 SSC Journeyman Points: 98 More actions · Answer 4

Hi All

Im also facing the same issue even when i have given unrestricted file growth by 10 percent, also i have a disk space of 12 gb available when i have the DB.

Please suggest the necessary changes that have to be made.

Thanks

aNIL

Rudy Panigas SSChampion Points: 10702 More actions · Answer 5

Not sure the db size but if you have set the growth to be 10% and if you take 10% of the current size and it's bigger than the free disk space, then you will get this error.

You can do 2 things. 1) set the growth to megabytes (not percent) or 2) manually set the new db file size and accommodate the space needed.

Worked for me 🙂

Rudy

SQL ORACLE One Orange Chip Points: 27807 More actions · Answer 6

Check you log file size. If it is bigger than your expectation, you may try the following approaches.

1. Have transactional log backups regularly;

2. Turn the recovery mode of this database to SIMPLE;

3. Add another data or log file on other drive.