Viewing 15 posts - 6,916 through 6,930 (of 59,091 total)
<quote>From the Last Sentence of the Conclusion in the Article...
To maintain the best precision of the final result all intermediate calculations must be performed on numbers in floating point formats,...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 15, 2020 at 12:29 pm
I've attached a screen shot of the table definitions.
Ya know... If you were to post an actual CREATE TABLE bit of code for the pertinent columns for this problem...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 15, 2020 at 1:02 am
I have to ask... were the databases previously on-premise? If so, did they "work fine"?
--Jeff Moden
Change is inevitable... Change for the better is not.
June 14, 2020 at 8:09 pm
Also, please enjoy sp_Who3
Perhaps the author should spend a bit more time on it first.
Msg 8152, Level 16, State 13, Line 1
String or binary data would be...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 14, 2020 at 7:28 pm
Just like the best managers, "GateKeepers" must not be just enforcers... they must also be "servant-providers". That doesn't mean they should just rollover and give in just because someone wants...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 14, 2020 at 3:07 pm
Worked like a champ. Thanks jeff.
😀 Thanks for the feedback.
To be sure, though, do you understand how and why it works?
--Jeff Moden
Change is inevitable... Change for the better is not.
June 14, 2020 at 3:27 am
and what are advantages of using trace flags for saving deadlock data to transaction log compared to seeing them in the default XE sessions?
Heh... it's a part of EVERYTHING...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 14, 2020 at 3:25 am
Frederico mentioned the most important thing in his very first sentence, which is...
you don't need to measure everything - if someone asked you to do that they don't know...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 14, 2020 at 3:21 am
Thank you, Jeff, for your
very valuable comment. And I am doing that , too (top 10 worst , etc.).
but aside along from that, there is a specific question asked...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 14, 2020 at 3:01 am
SELECT STRING_AGG(d.value,',')
FROM (
SELECT value
...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 14, 2020 at 12:24 am
--Jeff Moden
Change is inevitable... Change for the better is not.
June 13, 2020 at 4:46 pm
You're doing the wrong thing badly. You don't seem to know the table must have a primary key by definition; this is not an option! A row is not...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 12, 2020 at 4:40 am
Here's one way to do this... it's horrible because, without a Clustered Index on the ID column, it takes 4 scans of the table and doesn't do much better with...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 12, 2020 at 4:33 am
I believe it's because an empty string in Power BI is a value. Try using nulls instead and see if you get the intended behavior.
'' <> Blank() in Power...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 11, 2020 at 6:51 pm
Heh... sounds almost as bad as the default trace. We blow through that in about 10 minutes.
--Jeff Moden
Change is inevitable... Change for the better is not.
June 11, 2020 at 6:45 pm
Viewing 15 posts - 6,916 through 6,930 (of 59,091 total)