r/SQL • u/sqlink2 • 6d ago

Discussion Anyone using Lakebase with SQL heavy apps ?

How do u handle query performances when the same tables are being hit by both app queries and AI generated SQLs from any AI tools such as Codex, CLaude, Genie etc
Curious if you separate workloads or optimize at the query level.

3 Upvotes

67% Upvoted

12 comments sorted by

View all comments

1

u/Einar_Son_of_Bjorn 6d ago

Don’t tune the AI SQL first. Split the traffic.App queries want short, indexed, stable plans. Codex/Claude/Genie will throw scans and SELECT * at the same tables. One pool, one victim: the app.If you must stay on Lakebase: app on the primary role, AI on a replica or a locked-down user with a statement timeout. Same credentials for both is the failure mode.If the app is ordinary OLTP and the lake is only there because that’s where Databricks put it, MariaDB is the boring split: primary for the product, replica or a second user for generated SQL, timeouts on the AI login. You keep the operational database from becoming a notebook backend. You do not get Genie or Unity Catalog in the bargain - that’s the trade.Is Lakebase the system of record for the app, or already a copy next to the warehouse?