External company makes remarks that the server is the issue or could be the issue.
This is easy then... have a video meeting where you drive and they tell you what to look for/try/etc. HAVE THEM PROVE what they say. They should be happy to do it so that they can "prove" it's not actually their database design/software.
Almost every 3rd party database/software company I've complained to about performance have always blamed the server/hardware/index maintenance/blah/blah/blah. They also say, "Well, you're the first customer to complain". I so much want to tell them that we're also the first customer they've had that can actually tell. 😀
I've recently had one 3rd party database/software company explain that they need to archive rows from the biggest table to avoid documented major slow downs once it goes over [insert drum roll here] 40,000 rows. It's got like 15 columns of data in it and none of it has large character based columns.
There's another company that can't understand why them doing 149,000 reads on the same table for the same rows every time someone tabs to a new filed (close to 200 active sessions) is a bad idea.
is pronounced "ree-bar
" and is a "Modenism
" for R
ow.First step towards the paradigm shift of writing Set Based code:________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.
Dear Lord... I'm a production DBA. Please grant me patience because, if you grant me strength, I'm gonna need bail money to go with it.
Helpful Links:How to post code problemsHow to Post Performance ProblemsCreate a Tally Function (fnTally)