RKRakesh Kishoreintunedinstance.com·Jun 16 · 8 min readManaging Parameter Sniffing: Overcoming the Silent Execution Plan SaboteurEvery experienced database professional has faced this exact production mystery: A core application query or stored procedure that has run flawlessly for months suddenly slows to a crawl, triggering w00
RKRakesh Kishoreintunedinstance.com·Jun 14 · 9 min readMastering Execution Plans: How to Read a Query MapYou are a Junior DBA, and you just finished setting up an Extended Events session to capture long-running production queries. You open your capture file and immediately find a massive, resource-heavy 00
BPBharani Preetham Perakainbytebharani.hashnode.dev·May 14 · 1 min readOpening a form based on user filters in D365FO Using X++ and Query ClassesIf let's say there is a requirement to show a filter query where user can add different ranges he wants and once he clicks 'Ok', based on the query selected by user, the form should render. Or let's s00
IAIkem Adainviolacordis.hashnode.dev·May 5 · 7 min readInside the Query Optimizer: How Databases choose and Evaluate Query PlansYou write a query. The database runs it. You get your result. Simple, right? Not quite. Before your query ever runs, the database is already making decisions behind the scenes. It evaluates different 00
IAIkem Adainviolacordis.hashnode.dev·May 4 · 6 min readHow to Read Query Execution Plans and Fix Slow QueriesYou run a query, and it feels slow. You tweak the SQL. Add a condition. Rearrange a join. Sometimes it helps. Sometimes nothing changes. At this point, many developers are guessing. But the database i00
IAIkem Adainviolacordis.hashnode.dev·May 4 · 4 min readWhy Some Queries Are Fast and Others Are Slow.You run a query, and it works. Everything feels fast and responsive. Pages load quickly, dashboards update instantly, and there is no reason to worry. But as your data grows, things begin to change. A00
IAIkem Adainviolacordis.hashnode.dev·Apr 30 · 4 min readWhat Happens When You Run a Query? From SQL to ResultsWhen you write a query like: SELECT * FROM users WHERE id = 10; it feels simple. You send a request, and the database returns the result. But behind that one line of SQL, a lot is happening. The data00
ASAnsh Sachaninmongodb-aggregation-pipelines.hashnode.dev·Apr 21 · 2 min readHow AI read documents ?If you want to understand what type of content is available in this document you go to chatGPT and say “Summarize this document and AI reads the document and summarizes it”. But Have you ever think t00
ESEric Siwakotiinericsiwakoti.hashnode.dev·Apr 13 · 4 min readOvercoming Hard-Question Failures in RAG Using Agentic Design PatternsI reviewed post-mortems from teams deploying Retrieval-Augmented Generation (RAG) in production and found a consistent failure mode: RAG handles simple questions well but breaks down on ambiguous quer10
PPPRATIK PATELinblog.pratikpatel.pro·Mar 31 · 6 min readPrisma N+1 in Production:Real Query Plans and Fixes The silent killer hiding in your ORM It was a Tuesday morning when our on-call alert fired. P95 latency on /api/dashboard had crossed 4 seconds. Nothing had been deployed. No traffic spike. The databa00
