Has anyone used the new automatic database space expansion feature in ASE 15.7? Within our software, I am looking to switch over from using the traditional device creation methods (creating devices large enough to house all of required database data) to creating small devices and setting up the necessary thresholds and expansion rules.
However, since this is fairly new feature within ASE 15.7, I was wondering if there are any issues.
Some of my initial concerns are the following:
1. Disk fragmentation and how that effects database performance. Over time, the device(s) will be fragmented physically as space is allocated. Does this affect performance within the server/database?
2. When expansion is detected by the server, does the expansion process of the device and allocating of space to the database affect database performance?
3. Is there a limit to the size of the auto expanding device(s) - other than the amount of physical space available?
4. Any known bugs/defects within this feature that are show stoppers?
I am in the process of setting up a database with auto expansion, and will play around with it, but thought I would ask the experts for any known issues.
Thank you!
Lisa Sayre