Results 1 to 4 of 4
  1. #1
    Join Date
    Aug 2003

    Unanswered: tempdb tran log getting full

    Problem solved
    Last edited by sspruthi; 09-19-03 at 07:03.

  2. #2
    Join Date
    Feb 2002
    Willy is on vacation
    Hiya there,

    There is no point increasing tempdb when you have rogue(bad) users that write dumn SQL to the server. For eg: Cartesian joins, which can easily fill your 500MB tempdb too.

    So what you really need isthe multiple tempdb feature, and then you can allocate all the bad users to work in a particular tempdb and sa and sso in it's own.

    This feature is available in IR onwards and is quite easy to setup. The beauty of this feature is sa is never locked out.



  3. #3
    Join Date
    Jul 2003

    Wink Re: tempdb tran log getting full

    Originally posted by sspruthi
    we are having a tempdb of 200 MB size on 2 different db devices with data and log on same devices. Our prodn database size is around 6 GB.I am facing problem of transaction log full quite often and we are not even able to dump tran(including no_log option) to free up space in tran log and at that time we cant execute a single command.
    tempdb size is quite less and infact we are planning to make it to we cant go beyond that due to some constraints...will that help the cause or do we need to put a separate logdevice for tempdb..and if yes..what size it should be..??
    I am quite a beginner in sybase so can u plz tell me how to solve this issue....
    U shud clarify u r currnent Sybase setup here. Certainly u can increase tempdb size to 500 MB also separate Data and Log also. This certainly increase the performance.

  4. #4
    Join Date
    Jan 2002
    Hi surjeet,

    do not discuss issue with the forum.. first consult with yr higher officials.. and first ask yr higher official to send u for the sybase course..



Posting Permissions

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