| || |
Database bench marking
Actually it is not just bench marking.
I am supposed to review the database and report anything suspicious. Then do some bench marking for the database(MySQL & MS SQL Server) with real data and report obvious bottleneck or problems if any. Finally, give some suggestion on possible tuning. What are the approaches I can take? Any good tool? Thanks.
Re: Database bench marking
I feel strongly that you cannot review a database without looking at the applications that use that database.
Example: A while back we were testing a system that turned out to be very slow due to lock waits and the occasional deadlock. This had nothing to do with the database set up but everything with how the application operated.
But there are things that you can review in the database independent from any application.
* Stored Procedures: Check execution plan
* Review custom built functions
* Review indexes
* Review general structure, has the right level of normalisation been applied (very dependent on your intended usage)
* Review relation integrity rules
But again, first and formemost is check the database with the applications that use it.
Focus on contention issues, response times, data consitency, relational integrity after inserts, updates and deletes, use of indexes by the app. etc.