Results 1 to 3 of 3

Thread: "Logsegment is Full" error

  1. #1
    Jim Story Guest

    "Logsegment is Full" error

    I am trying to load 200,000 records into a MS SQL 6.5 database table using a Visual Basic data load program. I continuously receive the following error message after 175,000 records.

    [Microsoft][ODBC SQL Server Driver][SQL Server]Can't allocate space for object 'Syslogs' in database 'ECAPDemo' because the 'logsegment' segment is full. If you ran out of space in Syslogs, dump the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to increase the size of the segment. Occurred on 01/22/1999 03:35:41 pm
    ODBC--call failed. Occurred on 01/22/1999 03:35:41 pm

    I increased the Master database size up to 200 Mb, with TempDb at 250 Mb but I still receive the error.

    Any suggestions?


  2. #2
    Ray Miao Guest

    "Logsegment is Full" error (reply)


    On 1/22/99 2:43:01 PM, Jim Story wrote:
    > I am trying to load 200,000 records into a MS SQL 6.5 database table using
    > a Visual Basic data load program. I continuously receive the following
    > error message after 175,000 records.

    [Microsoft][ODBC SQL Server
    > Driver][SQL Server]Can't allocate space for object 'Syslogs' in
    > database 'ECAPDemo' because the 'logsegment' segment is
    > full. If you ran out of space in Syslogs, dump the transaction log.
    > Otherwise, use ALTER DATABASE or sp_extendsegment to increase the size of
    > the segment. Occurred on 01/22/1999 03:35:41 pm
    ODBC--call failed.
    > Occurred on 01/22/1999 03:35:41 pm

    I increased the Master database size
    > up to 200 Mb, with TempDb at 250 Mb but I still receive the error.

    Any
    > suggestions?

    It's nothing about master or tempdb. You have to expand log size for ECAPDemo, then check db option 'truncate log on checkpoint' or dump log time to time.


  3. #3
    Tony Sellars Guest

    "Logsegment is Full" error (reply)


    On 1/25/99 7:45:34 AM, Ray Miao wrote:
    >
    On 1/22/99 2:43:01 PM, Jim Story wrote:
    > I am trying to load 200,000
    > records into a MS SQL 6.5 database table using
    > a Visual Basic data load
    > program. I continuously receive the following
    > error message after
    > 175,000 records.

    [Microsoft][ODBC SQL Server
    > Driver][SQL
    > Server]Can't allocate space for object 'Syslogs' in
    >
    > database 'ECAPDemo' because the 'logsegment' segment is
    >
    > full. If you ran out of space in Syslogs, dump the transaction log.
    >
    > Otherwise, use ALTER DATABASE or sp_extendsegment to increase the size of
    >
    > the segment. Occurred on 01/22/1999 03:35:41 pm
    ODBC--call failed.
    >
    > Occurred on 01/22/1999 03:35:41 pm

    I increased the Master database size
    >
    > up to 200 Mb, with TempDb at 250 Mb but I still receive the
    > error.

    Any
    > suggestions?

    It's nothing about master or tempdb.
    > You have to expand log size for ECAPDemo, then check db option
    > 'truncate log on checkpoint' or dump log time to time.

    Also chop up your load into smaller chunks. Look at the Begin and End transaction statements in the books on line. These will allow the transactions logs for completed segments of your load to be cleared from the log. It is still possible to to fill up the log segment doing this and at that point you may need to dump the log.

Posting Permissions

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