Ask HN: Where do you store SQL and does it cut down "can you pull this?" pings?

We keep seeing the same two problems:

1. *Saving & sharing* – queries end up everywhere (Slack, Git repos, BI folders, Notion pages…).

2. *Endless requests* – because nobody knows what exists, engineers and data folks still get hammered with “please run this query / build this dashboard” tickets.

How is your team handling both sides?

- Do you have a single, searchable library? - Can non-devs discover and trust queries without bugging you? - What’s failed, what’s stuck?

---

We got frustrated enough to build *Galaxy*:

- *Cursor-style editor* → fast, modern, context-aware AI copilot for querying. - *Collections* → shared, version-controlled query library (like Postman). - *Endorsements* → mark a query as “Endorsed” so the next person stops asking.

Tiny pre-alpha opens tonight — brutal feedback welcome. We are excited to reimagine the SQL editor from the ground up and bring Datagrip, Dbeaver, Tableplus, etc into the modern age.

- Reddit threads that sparked this: - https://www.reddit.com/r/SQL/comments/1kzdn2p/does_your_team_have_a_sql_library_or_just_chaos/ - https://www.reddit.com/r/dataengineering/comments/1l049w2/how_do_you_push_back_on_endless_urgent_data/

• Feature overview: https://getgalaxy.io/features/collaboration

Would love to hear your war stories (and see if our approach actually helps).

5 points

・

garrettwolfe

・

2 days ago

1 comment

PaulHoule ・ 2 days ago

I've long been frustrated with database query tools like pgadmin 4, Microsoft SQL Explorer, etc. There are quite a few reasons, not least that they don't really give you tools to deal with the reality that your tables form a graph and your rows form a graph (e.g. you should be able to see the user record plus records that are effectively part of the user record as a graph on one screen) but the other one is the one you mention, that they just don't integrate with version control and the way people use SQL in code (e.g. maybe you should have *.sql files with your queries but practically people spray SQL all through their PHP, Java, Python, Ruby, whatever they are coding)

I think the most disciplined organizations use stored procedures but the ordinary methods people use for managing those often date from before version control. (e.g. so many people would wrongly laugh at stored proc users for being so 1990s + Oracle)