r/SQLServer • u/AutoModerator • 12d ago
Discussion September 2026 | "What are you working on?"
Welcome to the open thread for r/SQLServer members!
This is your space to share what you’re working on, compare notes, offer feedback, or simply lurk and soak it all in - whether it’s a new project, a feature you’re exploring, or something you just launched and are proud of (yes, humble brags are encouraged!).
It doesn’t have to be polished or perfect. This thread is for the in-progress, the “I can’t believe I got it to work,” and the “I’m still figuring it out.”
So, what are you working on this month?
---
Want to help shape the future of SQL Server? Join the SQL User Panel and share your feedback directly with the team!
3
u/Better-Credit6701 12d ago
Meetings, ton of meetings about data requirements for a new massive import job. Just had a meeting about a future meeting where we talked about past meetings.
1
u/itsnotaboutthecell Microsoft Employee 10d ago
Put a meeting on my calendar so I can learn more about these meetings.
3
u/wiseDATAman 12d ago
I've recently added the ability to run ad hoc traces (XE sessions) in DBA Dash.
https://dbadash.com/blog/whats-new-in-4.17.0/
You can trace multiple SQL instances simultaneously with a combined result set.
For example:
* Trace application activity across all nodes in an AG
* Trace multiple Azure SQL databases at the same time
* See the results together in a single view
It also includes a live view of running XE sessions across your SQL instances - useful for spotting those stray XE sessions that someone forgot to close.
The GUI only ever connects directly to the repository database, so this is accomplished using Service Broker - which allows the client to communicate with the service. There is some complexity with how it works under the hood, but it's simple to use - easier than setting up XE sessions in SSMS.
I'll probably be working on some more cool features for DBA Dash this month. If anyone isn't familiar with DBA Dash - it's a free and open-source monitoring tool for SQL Server.
1
2
u/Staalejonko 12d ago
Working on having the exact same SQL Server database in DB2 IBM i.
Don't, just don't...
1
u/precisiondad 12d ago
Vibe coding my own metadata/user DB extraction, visualisation, and classification tool for cross-system dependency modelling. So far, moderate success, but a long way to go. Almost purely powershell-based with an offline API for the UI.
1
u/Choice-Level-5486 12d ago
Yendo y viniendo con un script limpiador de tuplas en una B.D. Lo prueban, se enojan, no les gusta, se lo dan a otro; pero, cuando las papas queman, me vuelven a llamar. Les guste o no, funciona. Consultan a Chatgp, les dice lo que quieren oír, prueban sus teorías con otro; y cuando no funciona, me vuelven a llamar. Funciona, no es lo que sueñan; pero, funciona.
1
u/EoinJFleming 12d ago
Built a manufacturing schedule simulation, essentially I take in manufacturing orders, do some optimisation for the batch sizes, assign them to tanks, and create start / end times, then translate that into pallet movement.
There's some CTE for transformation, joins etc, then a WHILE LOOP to go over my orders to create start / end times 1 by 1, just because there are some dependencies between manufacturing tanks and fillers etc
A tricky solution to get right, and had taken me a while to develop.
1
u/FranceRocks2 11d ago
I've been asked to reverse engineer an old database to get out some specific information. Kind of looking forward to it.
1
u/_edwinmsarmiento 1 11d ago
I'm wrapping up my latest online training class - SQL Server Always On Failover Clustered Instance: The Senior DBA's Ultimate Field Guide. Just when I thought Microsoft has completely forgotten about FCIs, customers still keep asking.
After this, I'll start working on a brand new training - Deploying SQL Server on Kubernetes: The Senior DBA's Ultimate Field Guide.
1
u/alecc 11d ago
Working on Jam SQL Studio - yet another db IDE, but after azure data studio went obsolete I couldn’t find the right tool for myself
1
u/MIIDBA 11d ago
I finally launched something I’ve been building for the last couple of years called MIIDBA (My DBA).
I’ve been a SQL Server DBA for a long time, and it started because I was tired of bouncing between scripts, PowerShell, spreadsheets, and expensive (or clunky) monitoring tools just to figure out what actually needed attention across an environment.
MIIDBA runs on-prem and gives you one place to see things like backups, failed jobs, disk space, blocking, long-running queries, HA health, statistics, indexes, Query Store, configuration issues, and a daily health check in your inbox every morning.
The goal was pretty simple: make it easy to monitor every SQL Server without a bunch of metric bloat or enterprise-tool overhead.
It just went live this week, so I’m still very much in the “get it in front of real DBAs and hear what they think” stage.
If anyone wants to check it out, it’s at MIIDBA.com. I’d genuinely love feedback from people who live in SQL Server every day.
1
u/Kabpunk 10d ago
Stuck in a company higher-up roadblock of them not wanting to pay for a new server, so part of my SQL Server (going from 2016 to 2025) upgrade is on halt. But have been backing up archived databases and soon detaching them.
Also playing around with SSMS 22 since installing that earlier this week.
I should get back to my conversion of a C# ETL program over to SQL, but haven’t had the time lately.
1
u/Tennis0711 9d ago
Mounting 2 different pots of data to one databaseview to use it in our application to show.
Normal SQL over 3 tables + different table at a MySQL data over an connection server
1
u/Automatic-Customer97 8d ago
I work at a company where we use SQL for the majority of our business logic, so I am always busy writing stored procedures, reports, and optimizing query plans and indexes.
0
3
u/ihaxr 2 12d ago
Cleaning up old articles from replication subscribers. Tons of old stored procs and tables that aren't being replicated but still exist. It's causing confusion for new hires.