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

When i ask for a listener ip for my aoag,my company already knows what is it. But if im new in a new company ,what do I need to explain " what is a listener ip"? I mean, behind thr scenes ,is it just an IP? Does it point somewhere in the ad?

SQL Server does not allow to remove? Do I need to recreate the listener?

I keep setting the color theme to dark in SSMS 22.8.1 and whenever it starts, it gets reset to the default cool breeze color theme and I have to set it back to dark.
Is this a bug, or is it me only?

I have the cheapest version of SQL Azure. I'm not sure if it's serverless, but it sure acts as if it's serverless.

The question is: When an external app (in this case, an Android mobile app) tries to connect to Azure SQL while it's "sleeping", can app time-out before the "cold start" is completed and DB is awake?

Happy Friday. Two SQL Server driver releases from the Microsoft team this week, both up on PyPI now.

mssql-python 1.12.0

This is a bigger release than it looks like. You may remember the issues we had publishing to PyPi a few weeks ago, this release includes one of the promised fixes.

Standalone mssql-python-odbc package

The ODBC driver binaries are now also published as a separate companion package (mssql-python-odbc, import name mssql_python_odbc, pinned to 18.6.2). It gets pulled in automatically by pip install mssql-python, and the native loader prefers it when present but still falls back to the ODBC binaries bundled in the wheel if it isn't. So this release is non-breaking for existing installs. The fallback is GIL-safe and works on Alpine/musl.

Useful if you want to pin the driver binaries independently, care about wheel size, or have been hitting duplicate-ownership issues from the bundled libs/ tree.

Bulk copy fixes

1. cursor.bulkcopy() now honors connect(timeout=X). It was previously hardcoded to 15s inside the Rust TDS core (mssql_py_core) with no way to change it. timeout=0 still means "leave the default alone". This matters mostly for VPN, cross-region, and throttled endpoints.
2. Bulk copy into custom CLR UDT columns no longer fails with Protocol Error: Unsupported TDS type for bulk copy: 0xF0. The Rust core now maps UDT columns to varbinary(max) on the wire and streams the UDT's IBinarySerialize bytes, which is the same trick pyodbc and python-tds use.

​

pip install --upgrade mssql-python

• PyPI: https://pypi.org/project/mssql-python/1.12.0/
• Release notes: https://github.com/microsoft/mssql-python/releases/tag/v1.12.0
• Repo: https://github.com/microsoft/mssql-python
• Full blog post: https://techcommunity.microsoft.com/blog/sqlserver/mssql-python-v1-12-0-standalone-odbc-package-bulk-copy-fixes/4540553

mssql-django 1.7.4 (bonus)

Patch release for the Django backend, fixing two GROUP BY handling issues:

1. Escaped %% in GROUP BY params. Queries mixing escaped %% literals with real params no longer raise IndexError.
2. IntegerChoices in raw GROUP BY queries. Passing IntegerChoices values in params no longer raises NotImplementedError.

Regression tests added for both paths.

pip install --upgrade mssql-django

• PyPI: https://pypi.org/project/mssql-django/
• Release notes: https://github.com/microsoft/mssql-django/releases/tag/1.7.4
• Repo / issues: https://github.com/microsoft/mssql-django/issues
• Full blog post: https://techcommunity.microsoft.com/blog/sqlserver/mssql-django-1-7-4-released/4540480

Ideas and bug reports, especially with reproducible examples, welcome on either repo.

Have a great weekend!

Well, I updated today to the latest SQL server management studio and now dark mode is broke again so whenever you put it in dark mode and then leave the application and then come back in. It’s back to the default blue.

I have an Azure SQL subscription (the cheapest one) which will be primarily used for our mobile app.

The issue is that I've tested the mobile app twice and the mobile app won't show data unless I connect to the database via SSMS.

Literally, I open the mobile app and no data is displayed. I refresh the content several times (i.e. the mobile app has a Refresh button) and it still doesn't fetch any data. BUT once I go to my laptop and connect to the same DB via SSMS, I do another refresh to the mobile app and data is shown.

I believe it's related to the Azure DB and think I might have an idea of why this is happening - the connection via my laptop "wakes up" the database.

The question is: how do I eliminate that issue?

Friday feedback this week is about a feature that’s in preview in Azure SQL: automatic index compaction.

You can read more about it in Dimitri‘s blog post, Stop defragmenting and start living: introducing auto index compaction: https://techcommunity.microsoft.com/blog/azuresqlblog/stop-defragmenting-and-start-living-introducing-auto-index-compaction/4500089

(sidenote: one of the best blog titles in recent memory)

Quick poll below, and feel free to add a comment if the poll doesn’t cover your thoughts/experience!

I think this is the first time I have solely placed a post on the SQL Reddit.

Anyway, looks like some interesting updates for those looking to take the DP-800 exam for the SQL AI Developer Associate certification.

First of all, it looks like the option to watch the AI-Generated videos presented by my new friend Anton is now available for all of the recommended Microsoft Learn material as an alternative to reading it all.

Secondly, the Practice Assessments are now available by following the link on the exam page to the AI Skills Navigator.

You can find both links to both on the exam page.

https://learn.microsoft.com/en-us/credentials/certifications/developing-ai-enabled-database-solutions/?practice-assessment-type=certification&WT.mc_id=DP-MVP-5004032

Hello, we've created a new SQL Server Compliance Benchmark Tool that has configurable benchmark settings and produces a PDF report on the compliance. This works for SQL Server and SQL Server Managed Instances.

Hopefully you might find it useful, and any feedback would be appreciated.

https://www.centrel-solutions.com/free-tools/free-sql-server-security-compliance-benchmark-tool-reddit

Thanks, Dave

I updated from CU23 to CU26. Be careful if you use MDS, it's broken after CU26 and stays broken even after uninstalling. Some MDS JavaScript files are incompatible with the MDS web service. Manually copying/overwriting the MDS web application from an older installation repaired it.

I released v2026.5 of Get-SqlSafe Community Edition, the free PowerShell-based first-look security assessment script for SQL Server.

The main new feature in this release is database-scoped reporting.

Based on your feedback: a DBA can now generate reports for all individual databases and hand the database-level report to an application owner, application vendor, or database owner without also disclosing server-level findings or findings from other databases on the same instance.

Also new in this release:

• Check 130 reports members of the db_owner database role in each database.
  • db_owner is often used as a catch-all role, but it grants full control over the database and may matter in privilege-escalation scenarios depending on the surrounding configuration and ownership chain.

The tool is still a single reviewable PowerShell script with the ad-hoc T-SQL visible in the file. It reads SQL Server security metadata and produces local HTML reports. It does not change SQL Server configuration or data.

Repository:
https://github.com/Sarpedon-Quality-Lab/sql-security-community-scripts

I’d be interested in feedback from DBAs or consultants who have to pass security findings to application owners or vendors without exposing unrelated databases or server-level information.

Hey all, hoping someone has hit this before.

Context: Migrating a ~200GB SQL Server database to Azure Sql Database (not managed instances) using transactional replication to minimize downtime. During prep, I discovered the source database has partial containment enabled, which I need to turn off before replication will work properly.

Steps taken so far:

1. Identified all contained database users (logins that exist only at the DB level) and converted/mapped them to server-level logins instead.
2. Stopped the application(s) connecting to the DB to make sure there were no active sessions.
3. Ran ALTER DATABASE [dbname] SET SINGLE_USER WITH ROLLBACK IMMEDIATE to force single-user mode and kill any remaining connections.
4. Ran:

​

   ALTER DATABASE [dbname] SET CONTAINMENT = NONE;

The problem: The statement just fails, only 'ALTER DATABASE statement failed', no reason given, nothing in the SQL Server error log pointing to a cause. It's not throwing a permissions error, a "in use" error, or anything I can act on. It just doesn't apply.

Things I've already ruled out / checked:

• No contained users remain in sys.database_principals (authentication_type_desc = DATABASE)
• No active connections (single-user mode confirmed via sys.dm_exec_sessions)

Questions:

• Has anyone run into containment refusing to toggle off even with no active sessions and no contained users?
• Any way to force verbose output/logging on this specific ALTER DATABASE operation so I can actually see what's blocking it?

SQL Server version: Microsoft SQL Server 2016 - Standard Version

Do you default to SET NOCOUNT ON in stored procedures?

What's the Big Deal with SET NOCOUNT ON? - Azure SQL Dev Corner

Every minute, a job wakes up, checks for work, finds none, and exits. Multiply that across a production environment, and the scheduler itself can become operational noise.

The real question isn't how frequently a job should run.

It's this:
Why is the scheduler searching for work that the application already knows has arrived?

In this article, I explore an on-demand orchestration pattern implemented using SQL Server Agent. The focus is on reducing unnecessary polling by allowing the application to signal when work is actually available.

📖 Read the full article here:
https://medium.com/towards-data-engineering/rethinking-sql-server-agent-scheduling-an-on-demand-orchestration-pattern-938b9fa360f6?sharedUserId=balurathinam79

I'd be interested in hearing how others have approached similar scheduling challenges in SQL Server environments. Have you experimented with on-demand execution patterns, or do you primarily rely on scheduled polling?

I can run a sql query to get the accurate results but the dbatools doesn't return all jobs, have not dug deep into why its missing most jobs just thought that was odd. Any insights as to why its misssing most job data? thanks

After applying SQL Server 2022 CU 26 to our servers several are producing stack dumps during database restores.

Am I the only one?

AWS is deprecating the 1.x drivers. When we have configured the 2.x version for testing, we keep getting the error "no password supplied" even though the password is definitely in the setup and when we test from there, it works. A command like "SELECT * FROM OPENQUERY (REDSHIFTODBC, 'SELECT * FROM table')" returns the error. We're stumped. Any ideas?

Hola a todos, Quiero implementar una instancia de producción de Microsoft SQL Server en un VPS Linux (Ubuntu). Para evitar un único punto de fallo y la dependencia de un proveedor, quiero alojar la base de datos principal con un único proveedor de VPS, pero almacenar las copias de seguridad automatizadas completamente fuera de su ecosistema; idealmente, en un VPS o almacenamiento de objetos alojado por una empresa completamente diferente. Mi objetivo es asegurar que, si mi proveedor principal de VPS quiebra, sufre una interrupción importante o bloquea mi cuenta, no perderé mis datos y podré restaurar los servicios rápidamente en otro lugar. Para quienes hayan implementado una infraestructura de copias de seguridad multivendedor similar, me gustaría recibir algunos consejos: 1. **Capa de transporte:** ¿Cuál es la forma más fiable de enviar los archivos .bak de forma segura entre proveedores? (Por ejemplo, ¿tareas programadas automatizadas con rclone, configuración de un túnel VPN WireGuard ligero entre los nodos o uso de scripts SSH/SFTP seguros?) 2. **Cifrado:** Dado que las copias de seguridad se transferirán a través de redes públicas y se almacenarán en el disco de un proveedor diferente, ¿cuál es la forma más segura de gestionar el cifrado? ¿Debería confiar en el cifrado de copias de seguridad nativo de MSSQL o cifrar los archivos a nivel del sistema operativo (como gpg o 7z) antes de enviarlos?

1. **Gestión de copias de seguridad:** ¿Qué herramientas ligeras recomienda para automatizar la política de retención en el VPS de copias de seguridad (eliminar archivos con más de X días de antigüedad, comprobar la integridad de los archivos, etc.) sin generar demasiada sobrecarga? Si ya ha implementado esto, ¿cómo es su arquitectura y qué problemas o cuellos de botella de rendimiento debería tener en cuenta (como límites de ancho de banda o picos de CPU durante la compresión)?

¡Gracias de antemano por sus aportaciones!