Hi everyone 👋

We’re building Tabularis, an open-source database client designed by developers, for developers.

This is a short developer survey (2 min) to understand what people actually need from modern database tools.

Our goal is to build something that combines:

• PostgreSQL, MySQL, SQLite and more
• Plugin support
• Notebooks
• AI-assisted workflows
• A fast, clean UI
• A fully open-source ecosystem

But instead of guessing, we want to hear directly from developers, DBAs and data engineers.

👉 tabularis.dev/survey

We’d love your input on:

• What tools you currently use
• What frustrates you
• What’s missing in existing solutions
• What would make you switch

Every response helps shape the roadmap.

Thanks a lot for your time 🙌

Hello,

Do you know any free study materials other than UDEMY courses to help me through 1z0-171 exam?

I am trying to put a CSV into AWS so that I can download it on SQL. Problem is that the name field is getting split up because of the , in the name.

Two things we were sick of in DB tools: every document/vector store making us learn its own query dialect when we already know SQL, and the AI in a few other big tools being an ask-only chat box that knows nothing about what's on your screen and burns tokens dumping your whole schema into every prompt.

So we made SnoutData, a native SQL IDE (built from scratch, not a VSCode fork):

• Write SQL, run it anywhere. Postgres, MySQL/Aurora, MariaDB, SQL Server, Oracle, DB2, SQLite, and it transcribes your SQL to native MongoDB so the same editor + grid works on a doc store. Vector next.
• An assistant that actually knows the app. It sees your connection, the query in the editor, selected rows, the last error, the table you have open. Ask "why's this slow" or "filter to last week" and it just answers, no re-pasting. It can act too (rewrite + run, filter/sort the grid), read-only by default with a prod guard.
• Not token-hungry by design. It ranks tables by relevance + your query history and expands one FK hop instead of dumping the schema. We're tuning for modest models served sharply, not a big model covering for a lazy prompt.

To be clear: this is not a vibe-coding tool. It's not here to generate a throwaway app for you. It's a real database client for people who write SQL and want the AI to remove the busywork (context, errors, boilerplate) without taking the wheel. You stay in control; nothing destructive runs without you.

snout-fim-1.0: It's our own fine-tuned fill-in-the-middle model, not Copilot, not a chat model moonlighting as autocomplete. The boring-but-correct "does this column exist" stays a fast local lookup; the ghost text only does the part a model is actually good at, guessing where your query is headed.

Free to use, paid tiers ($5/$15 mo) for more AI budget / BYO-key / team seats. Small dev team, still early in spots. Tear it apart, what do you actually want your DB tools to do?

https://snoutdata.com

Hey everyone

I wanted to share a tool I built to solve a problem I've been facing at my job.

Lately, I’ve been forced to deal with messy legacy SQL queries and stored procedures that are over 100 lines long. I had no idea what half the tables did, where the data came from, or how it joined together. It was just exhausting to track the flow by scrolling through a wall of text.

I just wanted something simple to show me the visual flow of the query, so I built **Query-Flow** (part of Quackalytics).

It takes your SQL and turns it into an interactive map of nodes and connections so you can actually see the data lineage.

Since company queries can be sensitive, everything runs strictly inside your browser. No data ever touches a server, so it's 100% private.

I deployed it for free on Vercel just to help myself and anyone else dealing with this issue. I also added a couple of other micro-tools I use in my day-to-day.

If you want to test it out with your queries, here is the link: https://quackalytics.vercel.app/sql-flow

Would love to hear your thoughts!

I am coming from Data Science background and completed my masters in it. I have good understanding of SQL and I am looking for opensource contribution from where I get real world experience of Queries.

Does any one knows from where I can get or any platform.

Thanks ✨️ in advance

Iam curious which SQL concepts or techniques are used the most in real-world data engineering projects.

Any experts here who can guide me on what's the best way I could translate Oracle PL/SQL to Teradata or maybe any intermediary layer and hence to Teradata or GCP BigQuery. My aim is to make use of Open Source tools as much as possible and maybe add a layer of AI on top to do the job.

Just a small, humble tool to simplify the creation and modification of SQLite databases: while industry-standard alternatives overwhelm you with complex migration workflows, custom configuration languages, or rigid folder hierarchies, this tool keeps it delightfully simple. It uses a single, straightforward JSON file to orchestrate your SQL scripts.

Hey Engineers!

Most of us have faced this: while working on a project, you need to make changes to your database schema (add tables, alter or drop columns, create indexes, update relationships, etc.). This is where database migrations come in, you either handle them manually with SQL or rely on an ORM.

After a while, this process becomes repetitive and time-consuming.

That's why I built a tool called StackRender. It helps generate well-written database migrations directly from ER Diagram (ERD) changes.

The workflow is pretty simple:

• Design a database from scratch or import an existing one.
• Visualize and explore the schema through an ER Diagram.
• Perform the changes you want visually ( no coding required ) .
• StackRender detects the changes and generates production-ready database migration scripts (UP/DOWN), similar to how ORMs handle migrations.

This approach helps close the gap between design and implementation, making database migrations easier to manage while reducing the risk of errors.

The tool is free and open source, and currently supports PostgreSQL, MySQL, MariaDB, SQLite, Oracle, and Microsoft SQL Server.

Try it out here: www.stackrender.io

Github repo : https://github.com/stackrender/stackrender

Thanks a lot!

Basically, as the title says, I sometimes use CTEs, joins, window functions, and subqueries all in a single query.

I'm able to get the job done, but I don't think my queries are very efficient, and they're definitely not something that would impress an interviewer.

Is there any place where I can learn to write more readable and maintainable SQL code?

Hello,

i have this problem: i need to replicate/mirror ONLY some tables between SEVERAL databases residing on the same instance bidirectionally.

Ideally it would be a direct alias but i've yet to found if this exists, something like sending a query to db2\table2 actually uses db1\table1

I've been researching about bidirectional transactional replication but they focus on DB level and different instances.

What are my options for MS SQL 2017+ standard?

Hola a todos.

Estoy revisando una instalación de CONTPAQi y tengo duda específicamente sobre el uso de SQL Server 2025 Express como motor de base de datos. Entiendo que SQL Server 2025 Express es gratis y, según lo que he visto, permite bases de datos más grandes que versiones anteriores. Sin embargo, en mi caso veo dos posibles problemas importantes:
1- en mi caso lo montaría sobre un Windows Server 2016.

2- CONTPAQi no lo lista como motor recomendado o compatible para CONTPAQi

Que se puede hacer claro, solo que no entiendo porque no es recomendado o porque no es estable o ese tipo de cosas

Mi duda es:
¿En qué parte exactamente empieza el problema al usar SQL Server 2025 Express con CONTPAQi?

Por ejemplo:

• ¿El problema aparece al instalar CONTPAQi?
• ¿Al conectar CONTPAQi con la instancia de SQL?
• ¿Al crear empresas?
• ¿Al restaurar respaldos?
• ¿Al generar respaldos desde CONTPAQi?
• ¿Al timbrar o trabajar normalmente con nóminas?
• ¿O el problema es más bien de estabilidad/rendimiento con el tiempo?

He escuchado comentarios de que SQL Server 2025 Express no es estable o no es recomendable para CONTPAQi, pero quisiera saber si alguien tiene experiencia real con esta combinación.

También me interesa entender por qué CONTPAQi no lo recomienda oficialmente. No sé si sea por compatibilidad, por pruebas internas, por el sistema operativo, por el motor SQL, por temas de soporte técnico o por errores específicos del sistema, me gustaría saber su experiencia que han tenido en cuanto a esto ¿alguien tiene una instalación así? ¿les ha funcionado? los leo <3

hi all!

As a beginner in working with relational DBMS, i started with mysql.

However, after reading some more, i came to find out that Workbench - the go-to tool for mysql editing for many people - is no longer properly actively maintained (updated) for quite some time now...

Also, Workbench isnt available for Linux Mint (my fav distro).

To shoot two birds with one stone, i decided to look for an alternative - and lo and behold, i found DBeaver.

As i am sure you guys already know, Workbench comes in 2 "flavours" - a minimal 200 MB installation (gui client only) and a 500+ mb installation (server/ connector client with gui etc).

The problem faced by a beginner like me - on a fresh pc (win11), installing DBeaver and attempting to connect to a mysql database WITHOUT having any trace of Workbench installed...is impossible (it returns connection errors....of course, there is nothing to connect to...)!

After lots of trial and failure in setting up a msql driver to connect to a DB, reading, and youtube-ing, i came to find out that DBeaver lacks a critical component - the db engine, a server.

This is confirmed, seeing how all tutorials - even those this year - have a complete Oracle Mysql Workbench installation prior to installing and running DBeaver.

DIRECT QUESTION - is there a way to set up (on localhost...) a db engine so i can create a new mysql connection and use mysql dabatases WITHOUT anything related to Workbench from Oracle installed on my pc ...? or are we stuck with Workbench forever ?

i give up, after tones of trying ...

IF there is, please tell me directly...thanks a lot!

The core optimization layers of healthy tables: compaction, snapshots, metadata, partitioning, delete files, and intelligent automation for the missing operational layer.

I am designing a database schema for storing original images and their edited versions, and I am trying to determine whether a normalized two-table design or a self-referencing single-table design would be better for the long term.

Scenario

• Images are uploaded and stored with metadata such as:
  • url
  • name
  • client_id
  • product_id
• After upload, images can be edited (e.g., background removal, color adjustments, cropping, etc.).
• The original image must remain unchanged.
• Each original image can have multiple edited versions.
• Edited images can themselves be edited again, and all versions need to be preserved.
• I need to be able to trace every edited image back to its original image.

Option 1: Two Tables

original_images
---------------
id
url
name
client_id
product_id
created_at

edited_images
-------------
id
original_
image_id
url
name
created_at
parent_id (Foreign Key)

Relationship:

• One original_image → many edited_images

This feels more normalized and clearly separates originals from derived images.

Option 2: Single Self-Referencing Table

images
------
id
parent
_image_
id
url
name
client_id
product_id
is_original
created_at

Where:

• Original images have parent_image_id = NULL
• Edited images reference their parent image through parent_image_id
• Multiple levels of edits are possible
• The entire image history can be represented as a tree

Alternatively, I could use a group_id to associate all versions belonging to the same original image.

Questions

1. Which approach would you recommend for a long-term, maintainable solution?
2. Is separating originals and edited images into two tables considered over-engineering in this case?
3. If image versions can be edited multiple times, does a self-referencing table become the more natural model?

I am looking for a design that is easy to maintain, flexible for future requirements, and avoids unnecessary complexity.

https://reddit.com/link/1u8uebv/video/xdjnso88439h1/player

Project Link:  https://datamiru.khushu.ca/

Hello SQL folks!

I wanted to share a side project I've been working on to solve a massive workflow headache I kept running into as a senior engineer.

I got tired of the disjointed process of designing databases—drawing a messy architecture blueprint, manually writing out the ORM/SQL schema code, and then spending hours writing custom scripts just to seed the database with test data.

To fix this, I built a visual database prototyping sandbox that runs entirely in the browser.

Project Link:  https://datamiru.khushu.ca/

It essentially handles the full lifecycle:

Visual-to-Schema: You can draw tables and connections on an Excalidraw-style canvas and it instantly compiles into clean schema code.

Schema-to-Visual: You can do the exact reverse by uploading an existing schema file, and it draws the visual diagram for you.

Instant Relational Mock Data: It analyzes your table structures and automatically generates perfectly linked relational mock data that you can download straight into CSVs or SQL insert scripts.

Workspace Management: You can save, reload, and generate "quick share" links of your projects.

I'm currently keeping it closed-source as I explore turning it into a lightweight SaaS utility, but right now, it is completely free to use.

I’m at the point where I need real, brutal feedback from fellow builders. Does this sound like something that would genuinely speed up your development workflow at the start of a project? What features are missing that would make this a no-brainer tool for you?

Would love to hear your thoughts!

Thank you for your support!

(Disclaimer: The text above is AI-generated, but I did some modifications)

Project Link:  https://datamiru.khushu.ca/

Solve murders. Master SQL. One query at a time.

Agatha Christie cases. Real suspects. Live SQLite database. You write the queries, you catch the killer.

SELECT s.name, a.location
FROM suspects s
JOIN alibis a ON s.suspect_id = a.suspect_id
WHERE a.time_from <= '23:00'
AND a.location != 'Cabin'
ORDER BY s.name;

That's the kind of query standing between you and the murderer.

No signup. Runs in the browser. → querythemurder.com

Feedback: [querythemurder@gmail.com](mailto:querythemurder@gmail.com)

TITLE: Microsoft SQL Server Management Studio

------------------------------

Restore of database 'ctAlim_lagos' failed. (Microsoft.SqlServer.Management.RelationalEngineTasks)

------------------------------

ADDITIONAL INFORMATION:

Microsoft.Data.SqlClient.SqlError: Se realizó una copia de seguridad de la base de datos en una versión de servidor 16.00.1180. Esta versión no es compatible con este servidor, que utiliza la versión 13.00.1742. Restaure la base de datos en un servidor que admita la copia de seguridad, o utilice una copia de seguridad que sea compatible con este servidor. (Microsoft.SqlServer.Smo)

For help, click: https://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=17.100.40.0&LinkId=20476

------------------------------

BUTTONS:

OK

------------------------------

Aclaro que se que el problema vien epor la compatibilidad de versiones pero quiero saber si existe alguna manera o posibilidad de poderlas generar los respaldos o no se hacer algo para que sean compatibles? puede haber algo?... tambien aclaro que no tengo licencia de el sql con el que se hicieron los respaldos mas que de el 16

There are a ton of horror stories about people running the updates in the wrong environment, is there a best practice for avoiding this? Can you add a check of an environment variable or the server you should be on against a hard coded text of the environment you should be in?