Viewing 15 posts - 2,251 through 2,265 (of 59,067 total)
Problem with learning on one's own [dt]ime is you can really only barely scrape the surface of all these techs going through books and training courses. The ecosystem is...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 19, 2022 at 4:14 pm
Not sure if anyone is ever coming back to this thread but having just worked on migrating JDE data out and found the above useful - here is the...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 19, 2022 at 7:01 am
Most of my IT coworkers aren't even interested in improving their skills on the company nickel. They will only improve their skills if whatever old technology is permanently removed,...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 19, 2022 at 12:19 am
And we can see earlier in this post how some people use tally from a function found on the net, because they have learned, that this is the only...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 18, 2022 at 10:46 pm
Interestingly I found that a setting of 8 (vs 6) does speed up the original slow query significantly it testing.
Perhaps it is time to increase the value due to...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 18, 2022 at 10:18 pm
A slightly different way to put it ... I'ts because SQL Server cannot actually use anything directly from Physical Reads. It MUST be loaded into memory before it can be...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 18, 2022 at 10:04 pm
What I've found is that a lot of employees have the proverbial 9-to-5- attitude and only want to improve their skills on the company nickel and on company time.
And, if...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 18, 2022 at 9:54 pm
Most people are still using a version earlier than 2022! So just using the 2022 version to solve this problem is not the right solution - for some developers...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 18, 2022 at 9:32 pm
For me, it's very much something that MS got wrong. They're even trying to make it so that the NULL settings are not optional and Front-Enders are ready to march...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 18, 2022 at 9:28 pm
Thank you.
I tweaked it a little and implemented this for my case and it worked.
Can you post your "tweaked" code? Others may learn from it.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 18, 2022 at 7:02 am
I agree... since NULL is not "nothing" nor even equal to another NULL, I don't know why they made it evaluate for NULL behind the scenes at all or why...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 16, 2022 at 7:44 pm
As expected!!!! On my desk it takes only 14 seconds to process 131,000 rows. Hardly not a statement that will be executed several times every minute or several times...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 16, 2022 at 6:32 pm
The problem is documented (well, kind of) in the Microsoft Documentation. They "cop" out on explaining exactly what could happen by "only" saying that having a NULL in the object...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 16, 2022 at 5:42 pm
I'll also tell you to never just up and delete a table. Instead, rename it and see if the proverbial phone rings. The job you save will be your own.
After...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 16, 2022 at 4:47 pm
@carsten.saastamoinen
That "split" contains an incremental recursive CTE and it's going to be absolutely terrible for performance. See here...
https://www.sqlservercentral.com/articles/hidden-rbar-counting-with-recursive-ctes
--Jeff Moden
Change is inevitable... Change for the better is not.
December 16, 2022 at 4:43 pm
Viewing 15 posts - 2,251 through 2,265 (of 59,067 total)