question

pits avatar image
pits asked

file group is running out of space

Hello, If file group for perticular database is running out of space then we shrink log files to release space but if during the same time if any backup job same databse is running then system won't let you perform shrink operation since backups is in progress for the same database. can you please advise then how we can perform shrink in such situation or resolve file group running out of space issue? rgds,
filegroupfile
10 |1200 characters needed characters left characters exceeded

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Kev Riley avatar image
Kev Riley answered
If you are finding that your log files are too big, then you might want to consider increasing the frequency of log backups. Shrinking the log files is not a workable option. Also consider how much data you have and how big the disks are - you might simply be getting to the point where you need to physically increase the disk sizes.
10 |1200 characters needed characters left characters exceeded

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Pavel Pawlowski avatar image
Pavel Pawlowski answered
I suggest you to move the log files to other drive to allow a database files to grow. Other thing is why your log is growing so much and then you have to shrink it. IF you have a FULL recovery mode, then you can lower the interval of periodic log backups to allow reuse of the VLF inside the log. If you are running in FULL recovery mode and you are not performing regular log backups, then consider whether you need the FULL recovery mode or not. If not, then switch to SIMPLE recovery mode and if you need the full recovery mode, then you should schedule regular log backups which will allow the log file to recycle and will not cause extensive log grow. In case you are in a SIMPLE recovery mode and the logs grows a lot, then you should analyse what causes that grows, as you are probably manipulating very large amount of data in single transaction. Then you should find such sources and consider to rewrite those parts to work in more convenient way. Eg. do updates of very large amounts on data in multiple batches instead of single batch etc.
4 comments
10 |1200 characters needed characters left characters exceeded

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Well said Kev..frequent shrinking of log file is not at all a good idea....
0 Likes 0 ·
that really good idea to set database from FULL recovery mode to simple , there after shrink the database,but if log shipping or db mirroring is running what about the jobs then
0 Likes 0 ·
As I wrote, if there is no reason for FULL recovery model, switch to SIMPLE, otherwise keep FULL and make more frequent backups of the log as laso @Kev stated. The VLFs will be reused after log backup.. Of course in case then the data were processed by eventual log shipping and mirroring.. But if the log grows because accumulating data for mirroring or log shipping, than I would investigate, why the log data are not consumed by mirroring or log shipping and are accumulating in log.
0 Likes 0 ·
If file group primary is running out of space,what maximum impact it will have ? will it cause in to disk crash?
0 Likes 0 ·
msocp avatar image
msocp answered
hi every one, i am facing the same problem as, 1)Could not allocate space for object in database 'OperationsManager' because the 'PRIMARY' filegroup is roll up. 2)Could not allocate a new page for database 'OperationsManager' because of insufficient disk space in filegroup 'PRIMARY'. 3)file group is running out of space. I apply these command but not resolved the problem. Plz help me urgent regards. shafiq
10 |1200 characters needed characters left characters exceeded

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.