Results 1 to 5 of 5
  1. #1
    Join Date
    Dec 2002
    Posts
    6

    Question Unanswered: DataBase Restoration Problem (SQL Server 7)

    I'm restoring a database daily. However until last two days, I'm getting the following error (this happens in Enterprise Manager and also when I use the Query Analyzer):


    Server: Msg 5149, Level 16, State 1, Line 1
    MODIFY FILE encountered operating system error 112(There is not enough space on the disk.) while attempting to expand the physical file.
    Server: Msg 3140, Level 16, State 1, Line 1
    Could not adjust the space allocation for file 'corporate'.
    Server: Msg 3013, Level 16, State 1, Line 1
    Backup or restore operation terminating abnormally.


    The server has sufficient amount of space. Where data resides there is 13.5GB free and where the log resides there is 4.75BG free.
    The backup file itself is 3.3GB.

    When peaking into the backup file, it looks good:
    data file being 4.4GB and the log 300MB

    What could be the problem? The server is running Windows 2000 Server, RAID Solution and SQL Server 7.0 Service Pack #4

  2. #2
    Join Date
    Dec 2002
    Posts
    6

    Re: DataBase Restoration Problem (SQL Server 7)

    I just want to also add, that on another server, where there is less space available, the backup restores fine. This is very strange.

  3. #3
    Join Date
    Oct 2002
    Posts
    369

    Question Re: DataBase Restoration Problem (SQL Server 7)

    If you are restoring to the 'PRIMARY' filegroup, or another filegroup with lots of member files, it may be that the filegroup is 'full' (from the point of view of Sql Server).

    Unfortunately this may correspond to different situations for which error messages are often not particularly helpful (the issue being due to some combination of the autogrowth algorithm, how auto growth may be constrained at a user level % / fixed increment, actual disk availability, etc., etc.). Such issues are more commonly seen in autogrow situations occurring during maintenence and / or production batching (but reasonably may occur in DB restore situations as well). Generally the error means that the disk(s) where the database(s) is / are located is / are full and /or the files of your database(s) cannot grow any more on their disk(s) (given the fixed increment or % setting constraint); or autogrowth of files may have been disabled. On DB creation (and hence mdf, ldf, sgf, etc. file creation) one either specifies or takes defaults for the initial size for each file. Similarly, one either specifies or takes defaults for how each file will increase via growth increment settings. Each time a file 'fills', it increases its size by the growth increment. When there are multiple files in a filegroup, (as is typically the case with the primary filegroup), filegroups do not autogrow until all the files are 'full'. Autogrowth then generally is initiated in a round robin type fashion. You may wish to manually check and increase the sizes of, and / or change the growth options of files that are members of the filegroup involved, as may be appropriate. If possible, I would be inclined to perform some experimentation on an identical (or very similarly configured) dev server to get a better idea of what the exact issue is in your case (before traumatizing the production server).

  4. #4
    Join Date
    Feb 2002
    Posts
    2,232
    Do you happen to be using fat32 as your file system (as opposed to ntfs) ? If so, fat32 has a 4 gb limit on file sizes.

  5. #5
    Join Date
    Dec 2002
    Posts
    6
    rnealejr>>FAT32 was the problem. I've checked and the drive was FAT32. The moment we converted to NTSF, the problem disappeared. Thanks a bunch.

Posting Permissions

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