Viewing 15 posts - 3,901 through 3,915 (of 59,087 total)
Thanks, Johan. That sounds like one of the many reasons why I stopped working in the front-end world. Having been one long ago, I appreciate what they actually have to...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 17, 2022 at 4:07 pm
Thanks for the explanation, Steve. I appreciate it.
But, aren't notifications working "just fine now"?
--Jeff Moden
Change is inevitable... Change for the better is not.
February 17, 2022 at 4:04 pm
If you've not had scale issues, then why all the business about limiting notations and shutting down notifications on old posts?
--Jeff Moden
Change is inevitable... Change for the better is not.
February 17, 2022 at 5:03 am
Asked the question as part of the triage and planning for this work about how many threads might be affected, or might be exceptions.
Perhaps you should read the article --Jeff Moden Change is inevitable... Change for the better is not.
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.
Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)
February 16, 2022 at 5:05 pm
I know it was mentioned in the article but it needs to be stressed a bit. One of the biggest reasons for massive log file sizes IS index maintenance and,...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 16, 2022 at 4:28 pm
table and script trigger attached.
Thanks
Where? I see no attachments anywhere on this thread,
--Jeff Moden
Change is inevitable... Change for the better is not.
February 14, 2022 at 10:21 pm
Also the trigger is to add logs to another table. This is usually used when user change address from user interface web site, so it is usually one record...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 14, 2022 at 9:55 pm
Yes collation fix helped...
"Second, look at the stuff in the SELECT list and FROM clause... basically, it's all a repeat of the same thing with a different qualifier. That's...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 14, 2022 at 9:47 pm
Which edition of SQL Server are you using and what are the parameters you're using for the "reindexing job"?
--Jeff Moden
Change is inevitable... Change for the better is not.
February 14, 2022 at 8:18 pm
The sample rate is at roughly a half second. It's hard to tell what the actual data is from the graphic you posted but are they actually recording the time? ...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 14, 2022 at 8:09 pm
I recently tried to run a update statemene with joins on a table that has 200,000 records. I suppose it should be very quick.
But it turned out it ran30...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 14, 2022 at 7:55 pm
Big improvement, do you see anything else that could be tweaked?
Many thanks for suggestion.
Two way street, first... what does the code look like now that you've improved it?
[EDIT] Either...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 14, 2022 at 7:45 pm
Post deleted. I missed the fact that the post I answered was a spam post.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 14, 2022 at 7:13 pm
You're using SQL Sever 2019... that means that there's little need to do such things using the likes of C#. Please see the following article and look for the 2019...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 14, 2022 at 7:11 pm
Try this as a start... How to Post Performance Problems , which might also give you a hint on how to start troubleshooting performance issues as...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 14, 2022 at 6:51 pm
Viewing 15 posts - 3,901 through 3,915 (of 59,087 total)