I concur. If your database was chunking away at a CI reconciliation for instance, it would effectively lock other apps out of their part of the DB server.
I have seen this happen with Oracle, too. Rick -----Original Message----- From: LJ LongWing <lj.longw...@gmail.com> Sender: "Action Request System discussion list(ARSList)" <arslist@ARSLIST.ORG> Date: Fri, 30 Jul 2010 11:38:39 To: <arslist@ARSLIST.ORG> Reply-To: arslist@ARSLIST.ORG Subject: Re: MSSQL Virtualization? Drew, I can't talk directly regarding the problems BMC was talking about....but just from my own understanding, SQL Server is a very 'heavy' application...it requires lots of RAM and lots of CPU, typically virtualization would make an OS share those resources, which isn't 'best' for this type of application...any time you want something from a DB, you want it as fast as possible....won't be as good in virtual as it would with Physical... -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Drew Shuller Sent: Friday, July 30, 2010 10:59 AM To: arslist@ARSLIST.ORG Subject: MSSQL Virtualization? Hello all, While helping use architect a new Remedy system, BMC suggested to NOT virtualize the MSSQL server, without giving any reasons except that there were "problems." Could I get some insight please? I would like to virtualize AR Server 7.1 and eventually 7.6 ITSM on a virtualized MSSQL server. What issues should I expect? Thank you in advance. Drew Shuller Soto Cano AB Palmerola, Honduras ____________________________________________________________________________ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
