Grant Fritchey (5/4/2015)

---

Sean Lange (5/4/2015)

---

Lynn Pettis (5/4/2015)

---

Jack Corbett (5/4/2015)

---

And for back to back posts to the thread. I really can't stand it when an OP says something like:

Please help me fix this poorly performing query, but without any code changes.

So how am I supposed to help? Maybe with some indexing tips, but, in my opinion, that's a code change.

Sometimes, improving the indexing is the only option available. Supporting a product where most of the code is embedded in the code and requires approval to make changes, then needs to go through extensive testing and approval processes, you do what you can where you can.

Wow that person is way too snarky to the people who are trying to help him. It doesn't seem like any amount of indexing is going to help a flawed implementation. How can indexing fix the problem? It isn't a problem of data retrieval being too slow. It is a problem of pushing all the data over the network when only 1 row is needed. I also don't understand why changing a single query to execute a proc on another server requires "thousands" of stored proc changes. If that is true, which I highly doubt, then they need a complete system rewrite because everything is far too tightly coupled to be successful anyway.

You can smell the desperation coming out of that one. No need to pile on. They clearly made some poor choices early in their process and those choices are chewing on them now and they're trying to find a quick, free, way out from under. Still no excuse for treating the people trying to help in an unkind fashion.