Todd, We are on 7.6.03 and MS SQL 2005. This version of the database has some kind of obscure bug which only becomes apparent with the READ_COMMITTED_SNAPSHOT on. What happens is that under certain conditions the SQL generated by AR Server generates a deadlock and one of DB sessions is killed by the SQL server. AR Server, however, does not realise the session was killed and keeps sending SQL commands down that connection. As it is not getting anything back, users start getting random "Entry does not exist" error messages (depending on which thread/session AR Server decides to use to serve the SQL command). After weeks of investigating, our DBA narrowed down the issue to the afore mentioned bug and the only solution was to disable the READ_COMMITTED_SNAPSHOT option (or upgrade to MS SQL 2008). Could all have been specific to our environment, but it is something to keep an eye on if you go for this setting in production.
Regards Jiri Pospisil LCH Clearnet From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Arner, Todd Sent: 20 December 2011 17:39 To: arslist@ARSLIST.ORG Subject: Using the READ_COMMITTED_SNAPSHOT database option on ARS Database ** 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. ================================================================================ _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ ************************************************************************************************* This email is intended for the named recipient(s) only. Its contents are confidential and may only be retained by the named recipient(s) and may only be copied or disclosed with the consent of LCH.Clearnet Limited and/or LCH.Clearnet SA. If you are not an intended recipient please delete this e-mail and notify postmas...@lchclearnet.com. LCH.Clearnet Limited, LCH.Clearnet SA and each other member of the LCH.Clearnet Group accept no liability, including liability for negligence, in respect of any statement in this email. The contents of this email are subject to contract in all cases, and LCH.Clearnet Limited and/or LCH.Clearnet SA makes no contractual commitment save where confirmed by hard copy. Cet e-mail et toutes les pièces jointes (ci-après le "message") sont confidentiels et établis à l'intention exclusive de ses destinataires. Toute utilisation de ce message non conforme à sa destination, toute diffusion ou toute publication, est interdite, sauf autorisation expresse de LCH.Clearnet Limited et/ou LCH.Clearnet SA. Si ce message vous a été adressé par erreur, merci de le détruire et d'en avertir immédiatement postmas...@lchclearnet.com. LCH.Clearnet Limited, LCH.Clearnet SA et les autres entités du groupe LCH.Clearnet Group, ne peuvent en aucun cas être tenues responsables au titre de ce message à moins qu’il n’ait fait l’objet d’un contrat signé. LCH.Clearnet Limited, Registered Office: Aldgate House, 33 Aldgate High Street, London EC3N 1EA. Recognised as a Clearing House under the Financial Services & Markets Act 2000. Reg in England No.25932 Telephone: +44 20 7426 7000 Internet: http://www.lchclearnet.com LCH.Clearnet SA, Siège Social, 18 rue du Quatre Septembre, 75002 Paris, Chambre de Compensation conformément au Code Monétaire et Financier. ************************************************************************************************* _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
