|
-
 Originally Posted by kanika
I told already...non-unique,non-clustered indexing i have tried was not of much help...unique indexing is the last option...
Either indexing strategy is wrong or business specs are asking to process a high percentaje of the rows in each table.
Have you traced the query? do you know what is doing?
On the other hand ...
1- the only option to increase performance in such an scenario is by resorting to parallel hint.
2- 1 lac is like 100,000 isn't it? ... a couple of tables in our shop have a population of in excess of 2 billion rows and we have no issues with indexes, not sure why it is not doable for in your case.
Last edited by PAVB; 04-30-2010 at 08:06 AM.
Reason: typo
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.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|
Reply With Quote