Results 1 to 3 of 3
  1. #1
    Join Date
    Apr 2004
    Posts
    16

    Exclamation Unanswered: i need you...............

    our database can dump transaction but the trans wasn't be truncated and it was being increasing all the time ,i found some old transaction in master..syslogshold i want to kill it ,but it doesnot work,he already exists.so i need you......please help me.thank you.

  2. #2
    Join Date
    Jun 2003
    Posts
    140
    Sometimes even if kill command is successful, you will see the spid running in syslogshold or sysprocesses. sybase tries to roll back the entire trasaction in if it was killed and time to back depends upon the length of the transaction so it may take long to roll back and the spid will be there untill its fully rolled back.

    To reduce the trancation log problem try to break long transactions in to smaller one and make sure sp_dboption "trunc log on chkp" is set to on, it will truncate the transcation log while chkpoint happens.

  3. #3
    Join Date
    Apr 2004
    Posts
    16
    thanks a lot,i get it.

Posting Permissions

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