r/SQLServer • • 19d ago

Discussion November 2026 | "What are you working on?"

3 Upvotes

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!


r/SQLServer • • 20d ago

Discussion November 2026 | Job Opportunities

10 Upvotes

Welcome to the monthly job thread!

Posting a job or opportunity? Include:

  • Role title and description
  • Location or remote/hybrid status
  • Company or client context
  • Direct application link

Looking for work? Share your skills, experience level, and what you're looking for.

Rules:

  • One top-level comment per opportunity
  • No "DM me" or link-free posts — include a direct, verifiable link
  • Scam or misleading comments will be removed and may result in a ban

r/SQLServer • • 1d ago

Community Share I made four small SQL Server tools that run entirely in your browser (formatter, CSV → INSERT, IN-list builder, CONVERT date styles)

6 Upvotes

I kept pasting work SQL and data into random online formatters and converters and didn't love that, so I built a few that run 100% client-side. Nothing you paste is uploaded. The pages' security policy only allows a cookie-free page-view counter, and you can check that in your browser's network tab.

  • T-SQL formatter. Handles CTEs, CASE, MERGE, [bracketed] names, N'...' strings and GO batches. It changes only whitespace and keyword case, and never touches identifier case (it's careful with columns named type, language, date etc.).
  • CSV → INSERT. Paste CSV or cells from Excel. Escapes quotes, keeps leading-zero codes like 02134 as strings, and splits into batches of 1,000 rows to stay under SQL Server's VALUES limit.
  • IN-list builder. Paste a column of values and get a quoted, de-duplicated IN (...) list.
  • Date format converter. Shows what CONVERT returns for every documented style, or paste a date string to find which style reads it. For example, with 2026-03-07 14:05:09.123:101 03/07/2026 103 07/03/2026 112 20260307 23 2026-03-07 120 2026-03-07 14:05:09 126 2026-03-07T14:05:09.123 Every style was checked against SQL Server 2019 output, not just the docs.

https://querybench.dev

I made it, it's free, and there's no sign-up. I'd really like to hear what breaks: SQL the formatter mangles, CSV it parses wrong, or a small tool you wish existed.


r/SQLServer • • 1d ago

Community Share Trying Database Agents with Azure SQL Database

6 Upvotes

When an Azure SQL Database issue shows up, Database Agents in Fabric Database Hub can help investigate supported performance conditions and show the evidence and guidance behind the issue. Azure SQL Database support includes Hyperscale and serverless.

Database Hub also brings together a wider SQL estate, including SQL Server on Azure VMs and SQL Server enabled by Azure Arc. Agent support is narrower than the Hub’s overall coverage.

If you try it, I’d be interested in hearing about an issue you investigated. Did the evidence help you understand what was happening? What would you want to see next?


r/SQLServer • • 1d ago

Community Request Friday Feedback - increasing the number of steps in the histogram

4 Upvotes

Happy Friday folks, today's feedback is related to a long-standing request to increase the number of steps in the histogram. I've linked the feedback item below and my request is that folks go to the feedback item and, if you'd like to see more steps, upvote it *and* add a comment about why, and the number of steps you want to see. 📊

If you don't have a login for the site, and don't want to create one, you can vote and comment below. Some of you will probably do both. That's cool too 😉

Finally, for context, other databases offer max values of 100, 255, 1024, 2048, and 10000. Remember: just because you can, doesn't mean you should. There are trade-offs for adding more steps...are those trade-offs ones you will accept?

https://feedback.azure.com/d365community/idea/76e6b527-5725-ec11-b6e6-000d3a4f0da0


r/SQLServer • • 2d ago

Community Share Microsoft Drivers for PHP for SQL Server 5.14.0 released - PHP 8.6 support

10 Upvotes

Working late tonight for a great reason - We just released Microsoft Drivers for PHP for SQL Server 5.14.0.

What changed:

  • Added support for PHP 8.6
  • Continued support for PHP 8.4 and 8.5
  • Removed support for PHP 8.3 and earlier
  • New releases now publish through PIE instead of PECL

Install:

pie install microsoft/sqlsrv
pie install microsoft/pdo_sqlsrv

Full blog post: https://techcommunity.microsoft.com/blog/sqlserver/microsoft-drivers-for-php-for-sql-server-5-14-0---now-with-php-8-6-support/4574976


r/SQLServer • • 2d ago

Community Share We just published mssql-python 1.18.0

7 Upvotes

This release focuses on performance and reliability:

  • Faster fetch paths and repeated-query execution
  • Better prepared statement reuse and pyformat handling
  • Custom application names for easier monitoring
  • Fixes for pooled connection behavior and Arrow reader shutdown

Blog post with details:

https://techcommunity.microsoft.com/blog/sqlserver/announcing-mssql-python-1-18-0-faster-fetch-paths-smarter-reuse-stronger-reliabi/4574946


r/SQLServer • • 2d ago

Question Latest Windows patches on the Linked Server OLEDB bug

13 Upvotes

The October 13 patch introduced a bug in Linked Servers where the connections were not cleaned up and it still isn't fixed. https://support.microsoft.com/en-us/servicing/os/windows-server/2026/11/kb5136487-windows-server-2022-update (see known issues)

I see Linked Servers heavily used in my workplaces where the Linked Server definition is to other MSSQL Servers.

Is the issue occurring where the Linked Servers are other SQL Servers, or is it limited to non-MS?

Has anybody noticed issues?


r/SQLServer • • 3d ago

Discussion Anyone stopped nightly index rebuilds and seen no downside?

37 Upvotes

For example an index hits 30% fragmentation, the job rebuilds it. Does anyone check whether performance improves enough to justify the work?

I posted about this on LinkedIn a while back and got two useful examples.

One DBA stopped nightly rebuilds spilling into business hours and addressed the query problems with targeted statistics updates. Another described a page-split storm after rebuilding nonclustered indexes at fill factor 100.

We’ve been working on page-density checks ourselves. Checking every index was expensive before we’d even rebuilt anything, so we narrowed the checks to heavily used indexes.

For rowstore indexes, low page density deserves attention. Half-empty pages still occupy buffer-pool space when cached. But packing everything tightly won’t necessarily help if the write workload quickly splits those pages again.

And if a query improves after a rebuild, was the benefit from updating the index statistics? Would a stats update alone have been enough?

My view is to start with the indexes the workload depends on and establish what needs fixing. Crossing a fragmentation threshold isn’t enough reason on its own.

Anyone here reduced scheduled rebuilds? What improved, and what eventually needed attention?


r/SQLServer • • 5d ago

Discussion Post-ADS poll: what’s your main SQL Server client now?

3 Upvotes

ADS users had to move somewhere this year. Did you go back to SSMS, switch to VS, or jump to something else entirely? What’s missing in your current setup?


r/SQLServer • • 5d ago

Community Share aisqltuner-index-tuner Version 1.1 release

8 Upvotes

aisqltuner-index-tuner, an open-source automated index tuning stored procedure for SQL Server 2025 and Managed Instance, is now at version 1.1.

Version 1.1 focuses on production readiness: automatic cleanup, safer index changes, improved reliability, and improved security.

Specifics are:

  1. Run history cleanup. Old runs used to be kept forever, so history tables kept growing. Two new settings delete old runs after a number of days. Each run cleans up after itself, so one Agent job is enough. There’s also a newsp_AIIndexTuner_Purge stored proc to clean up on demand.
  2. Safer automatic changes.

    • New limits skip index builds on very large tables, or for indexes over a size you set. To help stay within a maintenance window a new time limit parameter stops new changes from starting after a specified number of minutes in the run.
    • Builds give up after a short lock wait instead of blocking other work.
    • Before dropping an index for low usage, the procedure validates actual index usage statistics rather than relying solely on AI recommendations. It also never drops a unique index for low use.
    • Widening an existing index now keeps its compression and fill factor.
  3. Safer on busy servers. Data collection no longer waits indefinitely when blocked, and the physical-stats checks can be capped by table size or disabled completely to avoid adding load when a maintenance window is unavailable.
  4. More reliable AI calls. Brief throttling or network errors are now retried instead of failing the run. A response that times out is cancelled, so it stops using tokens. The copy of each request kept on the Azure OpenAI side is now deleted after use.
  5. Security and privacy.

    • The setup script is simplified so endpoints only need to be entered once and it now removes the API key from the plan cache and Query Store.
    • The AI is told to treat query text in the input as data, never instructions.
    • The README now spells out exactly what data is sent and what is kept.
  6. Fixes.

    • Databases whose collation differs from the server’s now work.
  7. Housekeeping. There’s a version stamp (SELECT AIIndexTuner.fn_Version();), an uninstall script, and automated tests on every change. The repo also now includes a CONTRIBUTING.md.

Release notes with the details are at aisqltuner-index-tuner/RELEASE_NOTES.md at main · AI-SQL-Tuner/aisqltuner-index-tuner and the repo is AI-SQL-Tuner/aisqltuner-index-tuner.

Let me know if you have any questions or feedback.

Enjoy!


r/SQLServer • • 5d ago

Solved SSRS failure with windows update fix..

Thumbnail reddit.com
3 Upvotes

r/SQLServer • • 5d ago

Question How do I speed up this query?

0 Upvotes

This is the query I have:

SELECT o.soc_text AS [Occupation Title], COUNT(a.series_id) AS [Records], CONCAT('$',ROUND(AVG(a.value),2)) AS [Average Salary]

FROM occ AS o

LEFT JOIN series AS s

ON o.soc_code = s.soc_code

LEFT JOIN all_data AS a

ON s.series_id = a.series_id

WHERE s.datatype_id_code = 10

GROUP BY o.soc_text, o.soc_code

ORDER BY o.soc_text

It currently takes ~9 seconds, and I need it to take <1 second, and I have genuinely no clue what I'm doing. In my second class at uni that's using sql, and in my first class we learned pretty much nothing about optimizing queries, just learned basic sql commands and stuff; and now in my second sql class we have to optimize a query that's querying like millions of lines of data, and I am quite stuck. Most of that info isn't really relevant, I just felt like complaining.

Anyway, any help would be greatly appreciated, preferably keep it in simple enough terms so I can actually understand it lol.


r/SQLServer • • 6d ago

Discussion Looking for unique, real-world database project ideas (MS SQL Server + C#)

Thumbnail reddit.com
1 Upvotes

r/SQLServer • • 8d ago

Discussion Interested to see peoples MDF/LDF sizes to settle and argument

7 Upvotes

I’ll cut to the chase. We support a company server side, we do the hardware and vm support plus patching etc and another company supports their proprietary software on one of the said servers. The software they have is backed by SQL.

We ran into an issue this week where the logs disk filled up and placed the database on a separate disk into recovery. It then had to replay the LDF over the MDF for consistency etc.

The trouble is the LDF at that point was 992gb. Yes you saw that correct. And it reported it would finish in around three days…

The MDF is 2.4Tb.

Basically my argument is that if setup correctly the LDF should never be that size given backups happen every 15 minutes.

They said they needed additional space so we gave them an extra 1tb which the used to attach a second log file onto the database. This has since used an additional 400gb for logs.

Can I ask, does this sound right to you guys why are the logs so huge, we can’t just keep allocating more and more storage to logs. Surely the logs should truncate?

Thoughts?


r/SQLServer • • 8d ago

Community Request Friday Feedback - plan guides

2 Upvotes

Friday Feedback this week is about a capability that has been around for a long time in SQL, but in my experience, I haven't seen a lot of folks use it. But maybe I'm an anomaly!

Question: Do you use plan guides in your current environment?

Feel free to provide more details in a comment about what problem this helps you solve (and why you can't use plan forcing 😉)


r/SQLServer • • 9d ago

Community Share Recent Windows updates cause SQL Server performance issues

41 Upvotes

r/SQLServer • • 9d ago

Community Share Get-SqlSafe with refreshed design and custom Note field released at PASS Summit

Post image
5 Upvotes

At the PASS Data Community Summit I published another update for Get-SqlSafe:

Besides a modernized design and several fixes, you can now specify a custom note to be shown in the report header. This will help to put the report in context, and can also be used to keep track of who prepared it.

If you haven't downloaded Get-SqlSafe yet: it is a free, low-friction, UI-based PowerShell script that scans your SQL Server for a selected list of high-level security posture indicators.
It supports SQL Server 2016 up to 2025, SQL Server on AWS RDS and Azure SQL Database.

You can get get-SqlSafe for free on Github https://github.com/Sarpedon-Quality-Lab/sql-security-community-scripts or Sarpedon Quality Lab's resources page: https://sarpedonqualitylab.us/resources/

If you need to run it at scale against multiple SQL Servers, you can see and download some examples on how to do that is these blog-posts:

Running Get-SqlSafe at Scale Across a SQL Server Estate

Building a SQL Server Estate Summary from Get-SqlSafe Reports

Leave a star at Github if you like it. And your feedback helps me prioritize functionalities to be included.


r/SQLServer • • 10d ago

Discussion SSMS and Net 8 runtime

7 Upvotes

Latest SSMS 22.12.0 still installs .Net 8 runtime even though MS dropped support for it!

What is stopping Micros~1 from moving to using newer framework?

Disappointing.


r/SQLServer • • 10d ago

Discussion Working on a live view of table changes. Looking for opinions

Post image
2 Upvotes

I'm building a live watch view in my database workbench and would love your opinion on this. I want to be able to do something in my app and see what happened to the tables without going through them one by one and refreshing.

Something like placing an order. An order gets created, items get added, the cart gets cleared, maybe a background job starts. I want to see those changes together.

This is what I'm trying so far:

  • Each table gets a line on a timeline. Inserts, updates and deletes have different markers. (if a new table updated showcase it in the chart). I am also thinking of just allowing users to select the tables to watch.
  • Hovering over a change shows the row and the values that changed.
  • You can pin a watch for something specific, like jobs changing to failed, and keep it checking while this workbench is opened.

I'm a visual person, so seeing the changes lined up across tables makes sense to me. But I'm still figuring out how useful this would be beyond a small local database. A busy table could fill that line pretty quickly.

Would you use something like this while developing or debugging? I'm particularly curious what you'd want to see when an update happens. Is the before and after enough, or would you immediately want to know which query caused it?

Still building this, so any criticism of the idea or how I'm showing it would help. 😊


r/SQLServer • • 10d ago

Discussion Is it a security risk for the name of the database to be exposed?

7 Upvotes

If I have a workflow where a handheld device was talking to the database and the real name of the database was transmitted instead of an alias (MyDBName instead of DBAlias), how big of a risk would that be? My gut is telling me that I should expose as little information as possible over the network, so using an alias would be better. I'm going to modify my workflow to use an alias, but I wanted to know what people think about this, security-wise.


r/SQLServer • • 10d ago

Community Share PASS Data Community Summit 2027 Dates & Locations Announced

Thumbnail
passdatacommunitysummit.com
13 Upvotes

r/SQLServer • • 11d ago

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

61 Upvotes

I would say I honestly hear “PostgreSQL is free. We’ll save a fortune on SQL Server licensing” at least once a month.

And yes I nderstand the appeal but the major cross-platform migrations I’ve been involved in became bigger, slower and more expensive than planned.

The work people underestimated:

  • Running and supporting both environments until cutover.
  • Testing differences in data types, rounding and comparisons against application behaviour.
  • Reworking stored procedures and the business logic buried in T-SQL.
  • Replacing SQL Agent jobs, SSIS packages, linked servers and reporting dependencies.
  • Rebuilding monitoring, backup and failover procedures around the new platform.

The data transfer was only part of the project and most of the work involved everything depending on the database.

PostgreSQL might still be the right choice. I’d want the migration budget to account for those dependencies before treating the licence savings as money saved.

My experience is weighted toward projects that became difficult, so I’m interested in the successful ones too.

For anyone who’s completed a substantial SQL Server-to-PostgreSQL migration: what did your estimate miss, and did the savings hold up?


r/SQLServer • • 10d ago

Solved Changes to SQL Server SECURITY Patching

0 Upvotes

SQL Server customers used to, effectively, have TWO options for deploying SECURITY fixes to their installed SQL Server instances:

  • GDR - security ONLY patches/updates (i.e., via Windows Updates/etc.)

    • only fixes directly related to SQL Server's attack surface.
  • CU - Security + ALL other bug-fixes (non-security), perf-enhancements/tweaks/options, and even (occasionally) new 'features', etc.

Take-away being that there were OPTIONS for DBAs/Admins relative to WHEN they could/would deploy ENGINE-LEVEL/BEHAVIOR-LEVEL changes - without having to sacrifice worries about security.
e.g., don't want a new, known, bug released on CUxxx but also don't want to leave your instances unpatched? GDR it is until the bug/issue in question has been fixed.

Fast forward to the past few months:

  • Microsoft is now bundling GDR fixes BOLTED-ON to (the most recent) CU.
  • i.e., IF you want security fixes to patch some fun vulnerabilities being discovered ...

    • then you're FULL on getting engine-changes as well.

While I'm not a HUGE fan of this, I ... get it - ish.

My question, though, is:

  • Has anyone seen this CHANGE 'documented' or mentioned in any public channels (or, cough, back channels; I mean, you could tell me, then I'd let you kill me, but I'd happily die with the answer tucked away into my brain) that would explain:

    • why (formally)
    • if this is ever going to go "back the way it was" (choice/options) and/or if this is the NEW path forward (sit down, shut up, and LIKE it).

TIA.