We are looking at enabling the READ_COMMITTED_SNAPSHOT database option to ON for AR System database per the recommendations in the Performance Tuning for Business Service Management white paper from BMC. I am curious if others are using this option and if it caused any issues after you enabled it? Any information you can share on how you sized your tempDB or other helpful tips is greatly appreciated.
We turned the option on in our development environment and it seemed to work for about a week until the drive that housed the tempDB filled up and shut down the SQL server. An additional 10 GB of storage was added and it filled up within 2 hours. Our ARS DB is 57 GB The tempDB had 23 GB at first and an additional 10 GB was added. According to our DBA, this should be more than enough space to handle the setting. The SQL server that houses the ARS DB also include 55 other "test" DB, so I am not convinced that Remedy is the cause of the tempDB filling up. ARS 7.5 MSSQL 2005 Thanks, Todd Arner Great Lakes -------------------------------------------------------------------------------- The information contained in this communication may be confidential, is intended only for the use of the recipient(s) named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please notify the sender immediately and destroy or delete the original message and any copy of it from your computer system. If you have any questions concerning this message, please contact the sender. ================================================================================ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
