@ExtensionsF No, it still applies to SaaS. Actually this issue cropped up in a SaaS environment first and I had difficulties reproducing it on my local dev instance. Bulk inserts are enabled in SaaS, no other differences in locks during inserts.
I almost never use the return value of the Insert function in AL, but recently I found it useful in avoiding a specific deadlock situation. And the deadlock itself was a very curious one.
https://t.co/5HcaxOy2c4
Did you ever get confused with Business Central's temporary tables and the way temp tables are passed to procedure parameters? I did too, so I wrote a post as a memo.
#businesscentral#dyn365bc
https://t.co/B5XqLS4SAZ
@ajkauffmann@EPErnst@KarolakNatalie Oh, I did not know that I'm also accounted in that number! webpack, babel/core, jest-cli, ts-loader - looks like my package.json dependencies.
@KarolakNatalie I don't expect it to be widely adopted in BC solutions. Never actually heard of any live implementations with columnstore indexes. And that's really the main reason I'd like to hear from people who tried it.
This post is an attempt to summarize my experience in using columnstore indexes in Business Central: possible use cases and some performance analysis.
What is your experience in using columnstore indexes?
#dyn365bc#businesscentral
https://t.co/zmaRdHTOub
@KarolakNatalie@EPErnst Yes, definitely. But you know what really drives me nuts?
Constructs like this. Which I've also seen quite a few times.
procedure DoSomething(): Boolean
begin
if MySetupRec.BooleanField = true then
exit(true)
else
exit(false);
end;
@DuilioTacconi I don't think that SaaS experience is so unique that even core runtime libraries are totally different.
This is a debugger snapshot from a sandbox session. SQL4 returned a row, then three sequential queries return empty set, and the last two run "IF EXISTS".
I went as far as doing another post on the "if not IsEmpty then FindSet" pattern. Don't beat me too hard for reviving the topic again, but I think this query can shed some light on the old urban legend of the "second roundtrip" of the FindSet function.
https://t.co/EKYg0sgvrF
@DuilioTacconi Thanks for the note. Right, it's a Docker container. I actually ran into this when I was looking at the server code - counter is in the query command object, so I'm sure this is not a weird fluctuation. But I'll run the test on a sandbox as well to leave no space for doubts.
@JeremyVyska Exactly, that's the idea I want to convey - there is no silver bullet solution. What works good for reads can backfire on writes and vice versa.
Although, when used creatively, SIFT keys can be turned into posting safeguards, like MS did with the new warehouse posting design.
In a couple of my previous blog posts I was reviewing the benefits and dangers of SIFT views in Business Central. Now I want to take a look at a possible alternative - how indexes with included fields perform compared to SIFT.
#dyn365bc
https://t.co/MtHF49NrRC
Recently, I've been practicing my TypeScript skills, and now Κ§arm is the result of my exercises. This is a tool allowing intuitive graphical presentation and editing of timelines.
https://t.co/DU8D9pEykq