Can you force a query execution plan for BAQ

Never mind, it used to work that way.

Same indexes for me; different plan. Not surprised there.

Thank you @Mark_Wonsil and @Banderson for putting up with me. This was helpful.

OK, makes sense. That confirms what was kind of in my mind. Best practice (and necessity) tends to lead you toward good indexes. But you never know what you don’t know about, so it’s good to check the indexes, especially when you are hitting a wall with efficiency.

And you’re right. There is one exception, which is a topic you were involved with:

Yes, that one came to mind a few times.

Now to tackle an efficient join of PartTran to TranGLC. :dumpster_fire:

3 Likes

Efficient? lol… I don’t know how efficient it is but if you have some criteria to lead you in the right direction, it works OK. I’ve found it to be extremely helpful for reconciling some financial things that had to be reversed, etc. But in those cases, we always knew which account to start from and/or a fairly small date range… or a specific invoice(s)…

Yeah, same here.