Results 1 to 4 of 4

Thread: Huge Transaction Log

  1. 09-30-2002, 12:31 PM #1
    harpua78
    harpua78 is offline Registered User
    Join Date
    Sep 2002
    Posts
    1

    Huge Transaction Log

    I am not a DBA and I run a personal web site that has gotten pretty large. I have never done anything to maintain my sql server, and now my transaction log is 10 Gigs and my data is only like 300 Megs. I am starting to get a memory leak with the sql service. What should I do? Is it bad to have a huge transaction log. I am not familiar with any of this stuff, so someone please point me in the right direction.
    Reply With Quote Reply With Quote
  2. 09-30-2002, 01:35 PM #2
    MAK's Avatar
    MAK
    MAK is offline Registered User
    Join Date
    Sep 2002
    Location
    Fantasy
    Posts
    4,254
    change your recovery model to simple.

    do a checkpoint on that database and shrink the log file.

    u can also do a sp_detach and sp_attach database.
    Reply With Quote Reply With Quote
  3. 09-30-2002, 01:38 PM #3
    MAK's Avatar
    MAK
    MAK is offline Registered User
    Join Date
    Sep 2002
    Location
    Fantasy
    Posts
    4,254
    OOPS. its sql server 7.0.

    u have to do a sp_detach on the database. (Database will be unavailbale for a min)
    delete the log file. (.ldf)
    then sp_attach_db (.mdf) on the database.
    Reply With Quote Reply With Quote
  4. 09-30-2002, 01:49 PM #4
    rmiao
    rmiao is offline Registered User
    Join Date
    Sep 2002
    Posts
    5,938
    You should backup log regularly or just set db option 'truncate log on checkpoint'.
    Reply With Quote Reply With Quote
« Previous Thread | Next Thread »

Posting Permissions

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

Forum Rules