X hits on this document

169 views

0 shares

0 downloads

0 comments

32 / 48

Microsoft’s SAP ERP (R/3) System (cont)

Multiple Problems with multiple solutions in this scenario:

When query is compiled, statistics are way out of line:

Queries like shown before get compiled to take the wrong index

Problem worsens when query like that is part of a nested loop join

With ISV packages you usually don’t know all the cases or catch all the cases

Solutions:

For known cases schedule update statistics on sensitive column

Check out http://support.microsoft.com/kb/922063 for new logic in SQL Server 2005 SP1 and SP2 to deal with ascending columns

DBA-416M• ISV configurations & implementations – Lessons Learned

Document info
Document views169
Page views169
Page last viewedMon Jan 23 14:59:33 UTC 2017
Pages48
Paragraphs862
Words4327

Comments