Results 1 to 7 of 7
  1. #1
    Join Date
    Jan 2006
    Posts
    74

    Unanswered: Autogrow of file 'FORMS' in database 'FORMS' cancelled or timed out after 30547 ms.

    Afternoon

    I'm getting the below error message:

    Autogrow of file 'FORMS' in database 'FORMS' cancelled or timed out after 30547 ms. Use ALTER DATABASE to set a smaller FILEGROWTH or to set a new size.

    FORMS.LDF file is 7613952 KB and the growth is 512MB .

    By how much should I set the filegrowth? The users are complaining that the application is freezing on them.

    This is sqlserver 2000.

  2. #2
    Join Date
    Jan 2004
    Location
    In a large office with bad lighting
    Posts
    1,040
    Have you checked to see if the disk that the LDF file on has enough space left to grow? Is your databse in full recovery mode without a tran log backup EVER taking place? Do you need it in full recovery mode, or will simple do? Do you have a long running transaction filling up the log file?

    -- This is all just a Figment of my Imagination --

  3. #3
    Join Date
    Jan 2006
    Posts
    74
    hi

    There is nearly 2GB of free space on the server and the database is set to full recovery mode as it needs to be. There is only 1 transcation log being created and it's filling up day by day. Currently the users are unable to login.

  4. #4
    Join Date
    Jan 2004
    Location
    In a large office with bad lighting
    Posts
    1,040
    Are you doing transaction log backups?

    -- This is all just a Figment of my Imagination --

  5. #5
    Join Date
    Jan 2006
    Posts
    74
    I changed the recovery model to simple and it managed to free up some space, I then changed it back to full and limited the space. All seem's to be working.

  6. #6
    Join Date
    Jan 2004
    Location
    In a large office with bad lighting
    Posts
    1,040
    With the database in full recovery mode, you will have to do periodic log backups in order to allow sqsl server to truncate and reuse log file segments.

    If you do not institute tran log backups, you will run into the same problem as you had when you started this exercise ... the log file will fill up, autogrow, and continue until there is no more disk space for it to grow.

    BTW ... I hope you did a full database backup after you did the change to simple and back to full, because you lost the ability to restore to a point in time with transaction log backups ... oh that's right ... you aren't doing log backups. So you will have lost all changes since your last full backup.

    For a database in full recovery mode, best practice is to do a full backup periodically, and transaction log backups on a regular basis until you do another full backup. That helps keep the transaction log from growing out of control, and allows you to restore to a point in time if neccessary.

    -- This is all just a Figment of my Imagination --

  7. #7
    Join Date
    Jan 2006
    Posts
    74
    Yes I did a full database backup after I made the changes.

    I have not lost any data the last database backup was done last night as the database and the server gets backed up every night. The users have not made any changes for the past 5 days.

    I will def look into a long term fix for this.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •