OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
From: Stephen Cooper (Stephen.Cooperbis.org)
Date: Fri Apr 05 2002 - 06:14:14 CST

  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

    TO UNSUBSCRIBE: email "unsubscribe issforum" in the body of your message to
    majordomoiss.net Contact issforum-owneriss.net for help with any problems!
    ----------------------------------------------------------------------------

    Yes!

    The one that bites me over and over is the size of the Transaction log and its growth rate.

    In my recent test lab migration to Site Protector, the data migration tool simply fails when it encounters transaction logs > 2GB on any database involved.

    The content of ISS Knowledgebase article 020212-000007 "Clearing the Transaction Log" is something worth having to hand.

    Once this procedure is run, you can shrink the ISSED transaction log through the SQL Server Enterprise Manager GUI

    Stephen

    >>> "Barronton, Scott A." <Scott.Barrontonnscorp.com> Wednesday 27, March, 2002 15:37:43 >>>

    TO UNSUBSCRIBE: email "unsubscribe issforum" in the body of your message to
    majordomoiss.net Contact issforum-owneriss.net for help with any problems!
    ----------------------------------------------------------------------------

    A question for the group,

    Has anyone experienced the growing pains of moving the ISSED off of MSDE2000
    to SQL? I know there are several problems, one being if you have more than
    1 GB of memory on your SQL server you have to do a manual restore. Any
    other gotchas that we should be aware of?

    Scott Barronton

    DISCLAIMER: Any e-mail messages from the Bank for International Settlements are sent in good faith, but shall not be binding nor construed as constituting any obligation on the part of the Bank.

    CONFIDENTIALITY NOTICE: This e-mail contains confidential information, which is intended only for the use of the recipient(s) named above. If you have received this communication in error, please notify the sender immediately via e-mail and return the entire message. Thank you for your assistance.