May 2, 2012 at 5:17 am
durai nagarajan (5/1/2012)
current deploying the archive stratergy in some tables and making the changes in report as i am moving it to different DB. this is an activity monitor table.As i have to pull the data based on login, activity and datetime and data load is also high the performance of reports are not as expected despite of indexes.
Is there any other workaround apart from partitioning.
As already posted partitioning is not even an option - provided right indexes are in place.
Hard to tell without knowing the environment but my wild guess is that there is a problem with the indexing strategy and/or with the way queries are written.
Trace the five queries that hurt you the most, check where time is spent - focus on wait events. Fix the offending queries then start again with the five queries that hurt you the most, etc. By this time you will know the drill.
_____________________________________
Pablo (Paul) Berzukov
Author of Understanding Database Administration available at Amazon and other bookstores.
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.Viewing post 16 (of 15 total)
You must be logged in to reply to this topic. Login to reply