This article documents a SQL injection vulnerability I discovered in sys.sp_dbmmonitorupdate, a Microsoft-signed system stored procedure. For other SQL Server security vulnerabilities I’ve discovered, see the full series here.
In this article, you’ll learn step-by-step setup, Python code implementation, troubleshooting, and best practices to ensure your solution is secure and scalable.
Large databases usually have a negative impact on maintenance time, scalability and query performance. For maintenance, these large single databases have to be backed up daily while the amount of actual changing data might be small. For performance, tables without correct indexes result in full table or clustered index scans. As the data grows the total query time increase linearly. How can we decrease downtime for the maintenance window for large databases and optimize the performance of daily queries?
Steve notes SQL Server 2016 went out of support this past week. What are you plans if you run this version?
Learn about implicit conversions, which can dramatically affect the performance of your workload.
Preparing for disaster is important, both at work and in your personal life.
Learn how to use VECTOR_DISTANCE and VECTOR_SEARCH in SQL Server to find semantically similar data.
Security is an important consideration for anyone working with data, but it's especially a concern with AI.
Learn about using classification as a technique to prepare your data for additional machine learning analysis.
By ReviewMyDB
The T-SQL Tuesday #201 round-up: nine bloggers on whether temp tables are a friend...
By Steve Jones
I have been experimenting with MCP servers in a few ways, including the Redgate...
By Zikato
I deployed a schema change to 30 servers using multi-server query and deploy-at-low-priority. Small...
Comments posted to this topic are about the item A Challenge of Our Knowledge
Comments posted to this topic are about the item The memory toll of VARCHAR(MAX)...
In SQL Server 2025, where can I find information about items that prevent or delay the transaction log truncation?
See possible answers