We develop an application that uses Sql Anywhere 11.0.1 as the database. Database size can be anywhere from 5GB to 25GB. My task has been to come up with specs for the application to run in a virtual environment. I'm not a virtual expert, but I do know there are many different ways to virtualize. We have small, medium and large/enterprise customers that use our application. We have tested extensively on physical hardware and specifically RAID and mulitple SSD drives, so we know what performance can/should be. We have recommended specs built for physical hardware.
I read through many of the posts regarding MS SQL Server regarding virtualization(since I didn't find a lot specifically geared toward SQLanywhere). There are a number of ways to allow access to the DB (through shared storage on SAN, local storage on host machine, or possibly having multiple instances of the DB to share the load). So, my question is it plausible(from an industry standpoint) to not necessarily give VM requirements on our spec sheet, but have some fine print about DB performance "gotcha's" if running in a VM.
thanks for your thoughts
Request clarification before answering.
I have a client running ASA 11.0.1 (don't remember the build) on a VM Windows 2008 server. It has 8 gigs of RAM, virtual disks, etc. They have 80 connected users throughout the day and Mobilink running on the same server. There are 65 salesman that connect (Mobilink) during the day. Not all of the salesman connect at one time. It has been working for the last 18 months without a problem.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 5 | |
| 4 | |
| 4 | |
| 3 | |
| 2 | |
| 2 | |
| 2 | |
| 2 | |
| 2 | |
| 2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.