+ Reply to Thread
Page 2 of 2 FirstFirst 1 2
Results 11 to 12 of 12

Operating system error 112(There is not enough space on the disk.)

  1. Re: Operating system error 112(There is not enough space on the di

    > The LDF size is 3.65 GB, after reaching this size it is giving me this error.
    > You mean to un-check the option of Enable Autogrowth property for LDF file?
    > And set Initial size to some Number?? How do I set the size as Fixed?


    NO. If you disable autogrowth on the log file, you will kill the script at
    least as early if not earlier. Set the GROWTH to a fixed number instead of
    a percentage. But anyway, obviously your transaction requires much larger
    log file than 3.65 GB. Even increasing by 10 percent or 1 GB now is not
    going to help anything because if your transaction requires 80 GB of log,
    well, I don't even want to do the math on how many 10% growths it will take
    to get there, but clearly it is too many.

    Unless you want to manually expand the file to 200Gb or something, and hope
    that the log file won't need more room than that, the answer is going to be
    to change your script so it does not migrate all of your data in one single
    statement / transaction. Can't really give any recommendations here because
    all you said was "I am migrating data."


  2. Re: Operating system error 112(There is not enough space on the di

    This is a tool that we have developed to migrate data from MSDE to SQL Server
    2005 database. We wrote code to migrate because of the underlying database
    table/schema changes.

    We run this migration in one transaction and have to roll back if any error
    occurs. I was able to migrate some of the datasets from the customers
    successfully. For only with this dataset causing failure giving the above
    said error.

    There wil be no other applications running to access the database when I run
    this TOOL.

    Correct me if I am wrong, You mean to say, set File Growth in MEGABYTES
    instead of IN PERCENT?

    "Aaron Bertrand [SQL Server MVP]" wrote:

    > >> see the log_reuse_wait_desc column in
    > >> sys.databases. The value for this column is NOTHING.

    >
    > Did you try looking at this column while the transaction was occurring,
    > instead of after the error? If the transaction has failed and this specific
    > connection has given up and has stopped doing anything, this value may have
    > been changed by activity from another connection (or by the system) in the
    > meantime.
    >
    >


+ Reply to Thread
Page 2 of 2 FirstFirst 1 2