How fix SQL performance issues? Start by checking your wait stats
1-Ensure your TempDB database is configured optimally.
2-Make sure you're running index maintenance frequently.
3-Implement indexes that provide a benefit to your queries.
4-Checkyour most expensive queries and stored procedures.
5-Monitor your performance counters.
Item 2 is mostly incorrect for OLTP because a single row lookup takes exactly the same path on a 99% logically fragmented index as in does on one with 0% logical fragmentation. As for the rest, "It Depends". I will tell you that if your index maintenance includes the use of REORGANIZE, there's a very good chance that you're causing more problem than you're curing especially on indexes that you rely on lowing the fill factor to supposedly delay or prevent fragmentation.
The biggest bang for your buck is to keep index statistics up to date, especially if you have "ever-increasing" keys in your indexes.
I suppose you're going to tell folks how to accomplish the other 4 points, right?
To be honest, this sounds like a setup for a SPAM update. If you're not a spammer, go back to the beginning of this thread where it explains what was done to solve your "same issue".
RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row. 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.
Change is inevitable... Change for the better is not.