13th September, 2016
The performance of a database is obviously important; any DBA will tell you that. But, how do you define whatâ€™s acceptable and what isnâ€™t acceptable when it comes to performance? Itâ€™s imperative that the distinction between the two is nice and clear. In the first instance, developing baseline documentation for your environment can help you define this. So itâ€™s a good idea to have easily referenceable documentation to hand about your database as it can help in situations when youâ€™re attempting to un-earth degradation in your Oracle instance, for example. Understanding end users and the businessâ€™ expectations around the database performance is just as important too. Also, theyâ€™re more likely to notice issues with performance before your DBAâ€™s are. Having said this, there are many pro-active steps your DBAs can take to ensure database performance issues are spotted as soon as possible, such as regular health checks of your database environments which, can be cross referenced with the environmentâ€™s baseline documentation.
The steps that have been recommended in this short blog will help you easily understand what is needed to define the thresholds your database environment can comfortably operate within, although there are many more tailor made recommendations that we at RDB Concepts can make.
For more information on performance, please contact us.