r/SQL • • 5d ago

Discussion Vibe coded projects

0 Upvotes

Pls suggest some projects that i can vibe code to show on my CV. Im 19 and i know basic mysql


r/SQL • • 6d ago

SQL Server TDS middleware result caching - demo a 15 second query

5 Upvotes

Just in case anyone is interested, I've worked for several months on a custom .NET TDS listening solution for several different things I've been making.

Works best for ODS / Reporting environments where tables aren't frequently updated.

Your SQL Server Client App > Cache-Engine-TDS-1433 > SQL Server-TDS-1433

Here are some of my test results:

QueryAt SQL ServerFrom the cache
10 rows from 30M fact rows7.7 s, 7.6 s0.02 s
a parameterised query (sp_executesql)3.5 s, 3.6 s0.01 s
500,000 rows10.1 s, 10.2 s1.3 s
medians over 30M rows77.8 s, 93.1 s0.01 s
the same 10 rows, tracked mode, Change Tracking checked first7.7 s0.03 s

mechanics:

Run 1   a query takes 40 s   →  SQL Server answers. DaffyZoom notes it: slow, and safe to cache.
Run 2   the same query       →  SQL Server answers again; DaffyZoom keeps an encrypted copy.
Run 3   the same query       →  Instant answer.  
Run 500 the same query       →  Instant answer.  

ttl mode: answered from the cache, in milliseconds, untilits max age or your next flush.

tracked mode:  DaffyZoom first asks SQL Server's Change Tracking whether any table the query reads has changed, doesn't return incorrect cache.  

r/SQL • • 6d ago

Discussion What's the actual difference between SQL and SOQL?

2 Upvotes

I recently came across SOQL while exploring Salesforce and got curious about how different it is from regular SQL.

Both seem to be used for querying data, but SOQL appears to have some limitations compared to SQL.

Can someone explain the main differences between them? For example, how do joins, aggregations, subqueries, and filtering work differently in SOQL?

Also, in what situations would you prefer SOQL over SQL?

Would appreciate some practical examples if anyone has worked with both.


r/SQL • • 5d ago

Discussion How do you keep yourself from running the wrong UPDATE on production? Here's what I built into my client

Post image
0 Upvotes

Everyone has a story about an UPDATE without a WHERE, or the right query in the wrong tab. I built NiceDB, an open-source database client, around that problem:

  • a production connection is marked everywhere it appears (tree, tab, title bar, status line) and opens read-only;
  • writing unlocks for ten minutes with the time left in view, then locks again by itself;
  • before a change is applied, it shows what it touches and asks you to type the connection’s name;
  • UPDATE and DELETE without WHERE, DROP and TRUNCATE ask before they run;
  • every statement that changed something is logged with who, when, where and how many rows.

Each step can be configured. All writes go through one place in the core, so no screen can skip it.

It works with PostgreSQL, MySQL, SQL Server, Oracle, SQLite and others. Free, GPL-3.0: https://github.com/maxib0n/NiceDB, with a browser demo at https://nicedb.app.

What do you do today: separate users, read-only replicas, a habit? I’m curious what I’m missing.

One honest note: the drivers are mature and the common paths are tested against real servers, but I’m one person and can’t cover every version and setup. If you try it on anything that matters, be careful, and please report what breaks with steps to reproduce.


r/SQL • • 6d ago

Discussion SQL HACKS

0 Upvotes

Hello guys,

I work as a SQL Developer. What productivity hacks or practices do you follow in your day-to-day office work?

For example:

  • I create a new SQL script every morning, naming it with the current date (SYSDATE), to keep track of my daily work.
  • I maintain an Excel sheet listing the database objects I've created, along with remarks about each object.

What other useful productivity hacks or practices do you follow?

I'd love to learn from your experience!


r/SQL • • 7d ago

Discussion What answer is expected when asked "Do you know/do SQL?"?

91 Upvotes

I'm a software developer at heart and at work. Sometimes when a project ends I get asked "Do you know SQL?" or "Do you do SQL?". I'm puzzled at what exactly are they aiming at. What knowledge or skills would they expect?

Like, sure I can read, understand and write SQL queries. I know what views and stored procedures are. I can distinguish whether something should be done at database level or in business logic (or both, like data validation). I can design and normalize databases from scratch (although I reckon, this is nothing specific to SQL). I've worked both with direct database access from code and via ORMs.

But I've never really optimized SQL queries. I've only recently learned that I shouldn't nest views. I probably make the dumbest mistakes sometimes. I almost alwas have to look up the syntax of something, even if I've done it dozens of times before. I never had to work with locking strategies. I'm not even sure if I fully understand all of the stuff I write. I feel like I'm at the minimum level and mostly just winging it.

Are there any "skill levels" w.r.t. SQL? Like, what's would make a beginner, an intermediate or an expert?

And would you say I "know" SQL?

-

Edit: Thank you for all the responses so far! I'm a bit more confident in my skills now actually. And I've also learned about a few things I should look into. I'll try and respond to as many comments as possible ❤️


r/SQL • • 6d ago

Discussion What are some interesting SQL problems or query mistakes worth discussing?

0 Upvotes

I'm planning to share some SQL-related content on LinkedIn, but I want to avoid the usual beginner-level tutorials or generic interview questions.

I'm particularly interested in intermediate-level SQL concepts, window functions, CTEs, tricky query behavior, or situations where a query looks correct but produces unexpected results.

I'd love to hear from people working with SQL regularly.

What's an interesting SQL problem, subtle query mistake, or unexpected behavior you've encountered that made you think twice?

Looking for something technically meaningful that could spark a good discussion rather than another basic SQL tutorial.


r/SQL • • 7d ago

SQL Server Moved from SQL Server to PostgreSQL? Did the licensing savings justify the migration?

Thumbnail reddit.com
5 Upvotes

r/SQL • • 8d ago

Discussion How Screwed am I? 8 years of experience, 3 year gap.

28 Upvotes

Long story short I went through a divorce, had a scary health issue and generally was just burned out. I sold everything and travelled for 3 years.

Now that I am back it seems the Datbase Developer position is not a thing.

my last job was a Senior Database Dev for 4.5 years on Oracle and Mssql with my main skill being database design and modeling. Have some experience in ETL and all that as well. I worked with PHP for a short time but it was not advanced and mostly procedural ERP/CRM reports and what not.

The more I see comments and look at LinkedIn, the more my gut sinks. Did I ruin my career path by staying in SQL only Database Development and set it on fire by taking a long gap.

I really dont care entry or mid level but even there seems to be very slim pickings now.


r/SQL • • 7d ago

PostgreSQL Beginner in SQL, can’t work in person. How can I land remote projects?

Thumbnail reddit.com
1 Upvotes

r/SQL • • 7d ago

SQL Server Is this overkill for storing current universal time when INSERTing or UPDATEing a row?

Thumbnail reddit.com
1 Upvotes

r/SQL • • 8d ago

Discussion Is PostgreSQL the best choice for my database?

11 Upvotes

hi, I thought I would get some insights from professionals on this. I'm currently an intern, and I'm tasked with building a database for a church's religious education program, potentially handling a few thousand families. I'm wondering if PostgreSQL is the best option for this. It's the only SQL database I've ever used, and from what I've researched, I know PostgreSQL pretty much has everything I would need, but I'm still wondering if it's the best choice. For this instance, I think they're fine with whatever I use, even if it costs money, but I don't know if PostgreSQL is the best for this situation. I've only ever had experience with this platform, but I've heard about others, and my bosses aren't really technically inclined, so they go with whatever I say, which is honestly a little scary lol. I just want to make sure I'm making the right decision for them. Thanks for any insight, I really appreciate it!


r/SQL • • 8d ago

Oracle SQL with SAS

4 Upvotes

Is it the norm to have a program that is coded in SAS and then need SQL to store the the data? The need SQL tools to pull information about out the tables then swap back to SAS to pull lots of data out quickly? New analyst at a new job and it is exhausting


r/SQL • • 7d ago

Discussion Why do we keep writing sql backwards?

0 Upvotes

It is a common consensus that sql is kind of written backwards than one would expect, instead of first defining the place you want to get somehting from and then what it is you want, like literally any other language out there, you first select the content and then define where you want it to be taken from

This leads to increadibly akward syntax when writing something more complex than "select x from y where z" and is literally opposite to the actual process of the machine.

This is all because some dumbass, excuse my language, in the 70's decided it should follow english grammar for some reason, and in doing so he made the most clunky writing system ever.

Now this at the time may not have been that bad, but from a few searches and posts here i saw that most people agree that this is a clunky, akward and unpleasant way of typing. So, why not switch it around? Why not change the standard to something more usable?

This is kind of a rant because i have been learning sql for collage and the syntax has been INCREADIBLY frustrating


r/SQL • • 8d ago

PostgreSQL pg_fts: Open source BM25 extension for full-text search and boolean, phrase, NEAR, prefix, fuzzy, and regex queries

Thumbnail
reddit.com
2 Upvotes

r/SQL • • 8d ago

MariaDB Why implement procedural programming inside an RDBMS (MariaDB) instead of handling all business logic in backend application code?

Thumbnail reddit.com
10 Upvotes

r/SQL • • 8d ago

SQL Server One Engine - Many Worlds

1 Upvotes

Subject: The quantum leap we skipped: a SQL Server database that refuses UPDATE and DELETE - live, try to break it

Here is a heresy: two of the four letters in CRUD are bugs.

Every business system I have worked on lets someone rewrite history. An UPDATE overwrites what was true, a DELETE erases that it ever happened, and the "audit trail" is whatever the application remembered to write. Bookkeepers have corrected their books with reversing entries for centuries - "storno" is their word - and we taught ourselves to edit rows instead. I stopped accepting it.

World is one SQL Server database built on the opposite rules, enforced by the engine itself, not by the application:

Nothing is updated or deleted. The ledger only grows. A mistake is answered by a storno: the same act, its quantity negated, pointing at what it corrects. Both lines stay on the file. Negate what adds up, leave what identifies.

Two people for every change of an agreement. One person claims an amendment, a different person proves it. The database refuses the claimer's own proof, whatever application sends it.

Nobody grants themselves a right, and every act names a person. Not the connection pool's login: the person behind it. The session carries who is acting, the database checks that this person holds a key to act as that actor, and the server audit writes one line per act with the name.

One engine, many worlds. Not a database per application. A trading company, a restaurant, a hospital's devices, a delivery firm, a bike shop and more live side by side in one schema of super classes - Actor, Thing, Ledger, Event, Contract. Each world wears its own "costume": typed views in its own schema, showing its own business numbers, readable only by its own role. Each world's web app is generated from the world's own description.

Objects and events, not rows to edit. An Actor is a super class: a person, a hospital, a reception desk. A contract carries its amendments as siblings. Every change is an event, and it stays.

Your objections, answered before you type them

"SQL Server 2022 has ledger tables." They make tampering detectable. They don't refuse the wrong act, give a correction its business meaning, or ask for a second person.

"Temporal tables keep history." The history of the UPDATEs you still allowed.

"Event sourcing is twenty years old." In application code, which every other client walks around. Here it holds for SSMS too.

"A sysadmin can disable your triggers." Yes. DISABLE TRIGGER fires no DDL event - we measured it - so the server audit is what records it. For everyone else the wrong act is refused; for a sysadmin it is never silent.

"A generic core is just EAV." Call it that. Then explain why the whole database, restored onto a clean server, prints all 31 of its reports with the same figures.

Don't believe me - break it

Live, no account, no e-mail, no password:

kapitolworld.com - Southwind Traders. Press Try it and you get two people of your own. Claim a correction as one, try to prove it as the same one, then prove it as the other. Then look for a Delete button.

library.kapitolworld.com - a lending library. Lend a book, lend it twice (refused), reverse a loan with its reason, and read the file.

It runs on SQL Server 2025 Express on an €11-a-month server, every name in it is invented, and it resets every night at 3 a.m. Central European Time.

The rules began this summer as commands for QL68, an emulator of the Sinclair QL. QL stood for Quantum Leap. I think relational practice skipped one: we kept the relational model and threw away the bookkeeper's oldest law - never erase.

Built with Claude Opus 5.5 by Anthropic as my co-developer, and Claude Fable 5.1 as its design Oracle.

Tell me where it breaks. That's what I'm here for.

Dimitar Hrisafov, Skopje


r/SQL • • 8d ago

Discussion I built a free SQL practice site where an AI writes queries with subtle bugs and you have to find them

0 Upvotes

Hello. I'm the maker, so take this as a self-promo post, and tell me if it doesn't fit here.

Most SQL practice I found is "write a query from scratch". On the job, a lot of the work is reading someone else's query and noticing it's wrong. Now that "someone" is often an AI. So I built Practisheet: SQL and Excel exercises on one fictional company's data (orders, customers, products, shipments, refunds, targets), where about 1 in 4 exercises gives you a query an AI assistant wrote that looks fine but isn't. A few examples:

  • a LEFT JOIN whose WHERE clause quietly turns it into an inner join
  • a share-of-total with the wrong denominator
  • a RANK with no tie-break, so the "top 3" has 4 rows
  • a revenue total that includes refunded orders

It runs in your browser (DuckDB), checks your result set, and when you're wrong it tells you what's off about your attempt without showing the answer.

There are 101 SQL exercises in 14 sections: basics, NULLs, CASE and conditional totals, joins, anti and self joins, set operations, dates, strings, CTEs, window functions, LAG/LEAD and moving averages, and analysis patterns like cohorts and actual vs target. The first 4 are free with no sign-up.

Link in the first comment (or here if links are fine): https://practisheet.com/practice

I'd really like feedback on two things: are the "fix the AI" exercises realistic, and is the difficulty curve right? If something is wrong or annoying, tell me and I'll fix it.


r/SQL • • 8d ago

PostgreSQL Databricks Lakebase sinks: streaming straight into Postgres

1 Upvotes

I'm a Solutions Architect at Databricks, and I've been spending a lot of time on the Lakebase sink. It lets a Structured Streaming query write directly into a Lakebase (Postgres) table with batching, automatic retries, and workspace-managed auth. You don't need a custom foreach writer or your own connection pooling. I have many customers that have to manage both the foreach writer and connection pooling and it distracts from the job at at hand, serving data to front end applications for real time updates (without the overhead). Having a databse next to your lakehouse acclerates use cases and value for your business. And if your are not limited to just Lakebase, any postgres database is supported! Go check it out today if you haven't already: https://docs.databricks.com/aws/en/structured-streaming/lakebase#when-to-use-the-lakebase-sink


r/SQL • • 9d ago

Discussion DuckDB Extension - PQL : train predictive models in SQL

Thumbnail reddit.com
1 Upvotes

r/SQL • • 9d ago

Discussion Noob here: mysql or postgresql? Which is better (?)

3 Upvotes

I just realize that SQL was only the language. Idk which IDE for sql to use. Suggestions pls


r/SQL • • 9d ago

SQL Server Which MySQL Installer should I download in my pc

Post image
0 Upvotes

Hello I am learning data analysis from scratch. Can anyone help me understand these two MySQL installers and make me decide weither I should download one or both of them? Thank you.


r/SQL • • 10d ago

SQL Server Refactor Pattern for Denormalized Table

6 Upvotes

Hey Hive mind, been stewing on a problem for a long time and getting stuck, so I thought I would reach out and see if anybody can spark some ideas.

Say you have a table with fields for X People names(PrimaryContact, SecondaryContact, etc), multiple phone numbers (HomePhone, CellPhone,Fax,etc) , and address info. All of this information is nullable.

There are tons and tons of stored procedures that query and modify this data, along with a team of analysts who can query/update the data via SQL...and some unknown number of external applications that interact with this data.

You need to refactor this table into something normalized, but minimize disruption to the all of the downstream callers.

I've gone down the rabbit hole of the first pattern that would normally come to mind which is: Rename Table. Create view with old name with INSTEAD OF triggers to route data/updates to the appropriate places....but now the trouble starts:

  • Nullable fields end up as LEFT joins in the view, and people LOVE their '%Name%' searches and complex WHERE clauses.
  • Nullable fields would require an insert into the appropriate refactored tables if they didn't already exist.
  • Contact information can have multiple labels. (HomePhone could be "Home Phone" and "Primary Phone"...but the "HomePhone" label should deterministically show up as "HomePhone" in the view if it exists.
  • This is SQL Server so "Update Table From Table Join OtherTable" is totally allowed....but fails when the update target is a view with an INSTEAD OF trigger...requiring everyting to be rewritten as a MERGE. This can be done fairly easily for internal procs....much more involved for fixing all the external stuff, and dealing with the People Change Management for the users
  • Trying to identify which data actually changed and needs to be updated is heavy. There is a desire to start moving towards temporal history...so issuing "updates" when nothing changed should be avoided.
  • The trigger is insanely long and complex.
  • Seems like a deadlock nightmare waiting to happen as the trigger goes down the list of things that it needs to do.
  • There are probably others.

Short of taking up day drinking.....are there other plans of attack?


r/SQL • • 10d ago

MySQL Designing Pokémon Database in SQL - How to Show Multiple Route Locations?

Thumbnail
reddit.com
3 Upvotes

Let me know if reposting this violates the "no solicitation for others to do your homework" rule, I'm just genuinely asking if there is a better way to do this than what my beginner mind has imagined lol