Performance problem

Question

Performance problem

August 3, 2022 at 9:06 am

This was removed by the editor as SPAM
August 4, 2022 at 12:56 am

This was removed by the editor as SPAM
August 23, 2022 at 9:37 pm

This was removed by the editor as SPAM
August 26, 2022 at 3:13 pm

This was removed by the editor as SPAM
September 9, 2022 at 11:03 pm

This was removed by the editor as SPAM

Viewing 8 posts - 16 through 22 (of 22 total)

You must be logged in to reply to this topic. Login to reply

jefferyjordan26 SSC Veteran Points: 229 More actions · Answer 1

Jeff Moden wrote:

jefferyjordan26 wrote:
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-Check your 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?

thank you so much for your suggestion

This reply was modified 2 years, 3 months ago by jefferyjordan26.

Jeff Moden SSC Guru Points: 1004363 More actions · Answer 2

paanjii2 wrote:

sometime i got same issue, how can i solve this

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".

--Jeff Moden

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.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

homebrew01 SSC Guru Points: 55548 More actions · Answer 3

Jeff Moden wrote:

paanjii2 wrote:
sometime i got same issue, how can i solve this
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".

I think you win "BINGO" today !