Hi,
I am attempting to troubleshoot a "mysterious" performance problem. We have an Excel vba application that calls a function in SQL Server 2000.
The function performs very differently from Excel than it does from QA. That is, it's a lot slower from Excel. Also, the performance changes due to data loads in relevant tables that the function queries, (in both QA and Excel).
I am trying to come up with a LIST of all possible things I should be checking that could help me pinpoint WHY the performance between the two environments is so different.
So far I have:
* connection settings, such as arithabort (make sure these are the same!)
* table statistics (are they changing, thereby causing recompiles?)
* syscacheobjects (right now there are TWO different compile plans for the same function, even though I though setting arithabora ON from vba would solve the problem, but no)
* parameter sniffing
Any experience, advice greatly appreciated!!
I am attempting to troubleshoot a "mysterious" performance problem. We have an Excel vba application that calls a function in SQL Server 2000.
The function performs very differently from Excel than it does from QA. That is, it's a lot slower from Excel. Also, the performance changes due to data loads in relevant tables that the function queries, (in both QA and Excel).
I am trying to come up with a LIST of all possible things I should be checking that could help me pinpoint WHY the performance between the two environments is so different.
So far I have:
* connection settings, such as arithabort (make sure these are the same!)
* table statistics (are they changing, thereby causing recompiles?)
* syscacheobjects (right now there are TWO different compile plans for the same function, even though I though setting arithabora ON from vba would solve the problem, but no)
* parameter sniffing
Any experience, advice greatly appreciated!!