Hello,
we have a problem at hand - after updating from 4.0 SP2 to 4.0 SP3 and disabling index hinting the whole database turned to crawl. So much, in fact, that it takes 10 minutes to open for example detailed customer ledger entries. Monitoring shows heavy tempdb usage. Otherwise, neither other disks nor CPU are overloaded.
What could be going on here?
0
Comments
The most of us has some perf. probs, after the update.
But all these problems can be solved. U are working under SQL2000 or SQL2005? And which SP has the SP Engine?
It's ever the same answer.... so checkt the postings in this forum before, i know it's a hard work ..... but with this answers u can understand it better .....
viewtopic.php?f=34&t=13154
viewtopic.php?f=34&t=34879
viewtopic.php?f=34&t=35150
viewtopic.php?f=34&t=34639
viewtopic.php?f=34&t=32657
and so on.
Are u a Navision partner or a enduser?
Regards
yes, I know I have to search - I do infact, we solve most of our issues. I think we're close to solution already here aswell - it seems that some tables dont have their primary key as clustered, which makes sql server query optimiser select poor execution plan, and do sorting in tempdb. This sounds like viable theory to me, right?