I've looked through the 9.0 upgrade documentation and outside of some basic sizing guidelines I'm not really finding what I'm looking for.
I've also downloaded the worksheet that BMC put together for planning your resource requirements for 9.0 install based on users, ticket throughput, etc. What I am after are recommendations on a virtualized Microsoft SQL cluster and what we should provide to our SQL team on how SQL should be provisioned to support Remedy. In the past, we ran into several issues with DB connectivity from ARS due to an unidentifiable issue with latency between the cluster (veritas in this instance) and the storage array where the database was actually housed. The only solution was to revert back to a physical SQL server. We want to avoid this situation with our 9.0 upgrade by ensuring all of the SQL requirements are provided up front. Unfortunately, it looks like BMC documentation is kind of lacking in this regard. So, for anybody that has upgraded to 9.0 and has a large user base and large DB with a lot of transactions, do you have any lessons learned or recommendations for Microsoft SQL server in a clustered environment? _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
