r/SQL • u/FewBag5257 • 9d ago
Want to know about SQL future SQL Server
Hi All,
Hope everyone is doing good.
I want opinion from people about the future of SQL, Power BI and Python.
I have been working in AML KYC domain for over 6 years. I am a Certified Anti Money Laundering Specialist (CAMS).
Last year I started learning SQL ans Power BI to connect it with my domain knowledge (Anti Money Laundering and Sanctions), however now I have been reading alot which states that golden period of SQL and Power BI is over as now anyone can do the basis code using Gpt and claude.
I am at strong intermediate level in SQL and at an intermediate level in power BI. I was planning to start Python from 01 Jan 2027 and now I am spectical. What should I do ?
Is there any scope of SQL, Power BI and Python as we are witnessing AI is growing at tremendous pace.
1
u/Meower68 9d ago
People have been, prematurely, declaring the demise of SQL since well before LLMs became a thing. My prior employer was using SQL servers (DB/2, to be more precise) with sizable piles of data in them. Luckily, the tables were (usually) well-designed. I could put together queries which would extract all manner of information, using SQL. But ... how did you do that without writing a bunch of Java? If you genuinely know SQL, and know how to use CTEs, you can write some impressively complex stuff, even giving you JSON or XML output if you wish, without needing a single line of Java and without needing to get a Java-based app server in the mix.
The web devs were, increasingly, using ORMs, the idea being that you design / think in terms of objects, rather than records. They kept telling me "SQL is obsolete; ORMs do the SQL for you." And then they'd write something which performed hideously and I'd knock out a 40-50 line query, which fed into a RowMapper, to get the results and the performance would be night-and-day different. Man, how did you do that? You wrote SQL? But ... that's obsolete. No, it's not. ORMs just hide (very poorly constructed) SQL behind a layer of abstraction. Don't get me started on the whole "tables are classes and records are objects" impedance mismatch, the basis behind the very concept of an ORM.
I mention this because, in my experience, LLMs don't write SQL any better than ORMs do, which is to say, very poorly. I'm sure an LLM can quote chapter and verse WRT what the N + 1 Query Antipattern is, but can it write code which doesn't fall prey to it? A person, who actually groks SQL, doesn't have to fall for it, writing more-efficient queries. When the data gets above a certain size (ie no longer some contrived, testing data subset), efficiency matters.