Author Topic: Too much information!  (Read 3668 times)

Tony Tillyer

  • Guest
Too much information!
« on: January 01, 1970, 12:00:00 AM »
We've cut down all of our application logging to our SQL db Server but still there's a huge amount being written to the database. Anyone have any suggestions where else we could look to find out what else may be being written that we are not aware of?

TIA

Marked as best answer by on Today at 10:25:19 AM

Z

  • Guest
Too much information!
« Reply #1 on: January 01, 1970, 12:00:00 AM »
  • Undo Best Answer
  • what is your applications ?
    Check if MessageServer itself has network logging ON

    JG

    • Guest
    Too much information!
    « Reply #2 on: January 01, 1970, 12:00:00 AM »
    Check:
    Message Server (db_storage=false)
    Stat Server (QINFO table= false,status table= off, login_table: off)
    CCON?
    CCA?

    And the worst of all is...

    if your message server was up and your logdb was down, chances are you have a tremendous amount of files in your message server directory containing all the messages that the message server could not save into DB. So, check your message server directory for *queue* files... and if there are any well, then this is why. Of course, if you do not need those logs, just delete them and you should be fine.


    Tony Tillyer

    • Guest
    Too much information!
    « Reply #3 on: January 01, 1970, 12:00:00 AM »
    Thanks guys! We had used wizards to bring everything down that we could. The one we missed was the Message Server itself(!) We've switched down logging now and continue to monitor.

    Thanks again,

    Tony

    Kevin

    • Guest
    Too much information!
    « Reply #4 on: January 01, 1970, 12:00:00 AM »
    One other thing you can do
    If you want to keep some level of the message logging to the database (so you don't need to sift through debug log files for Trace or Standard messages), you can also work with your DBAs to create scripts to "clean" old messages from the database.

    If you run through the Log Maintenance Wizard in SCI, it will "create" for you the SQL query to update/remove certain types of messages that are over X days old (we do 30 days for trace, 90 for standard and alarm) . Copy this SQL and provide to the DBA with the requirements you need. They should be able to modify it to a script that can be run by a cron job during low raffic periods (early Sunday morning).

    The DBA should also be able to have it commit the deletion after so many rows, so you do not run into errors around the transaction logs filling up and the server trying to roll back millions (!) of records.