Believe in Your Data - Database Weekly (Aug 25, 2008)
As DBAs we must secure and protect data, but what can we do when there are fundamental issues with the way the systems are designed. Steve Jones comments on problems with voting machines.
If You Ain't Cheatin'
Gaining recognition or an award without earning it is something Steve Jones thinks is a problem in society in general, and it's filtered into the IT industry.
If You Ain't Cheatin'
Gaining recognition or an award without earning it is something Steve Jones thinks is a problem in society in general, and it's filtered into the IT industry.
If You Ain't Cheatin'
Gaining recognition or an award without earning it is something Steve Jones thinks is a problem in society in general, and it's filtered into the IT industry.
Managing Security
This Friday Steve Jones comments on the practice of using Active Directory to help manage your SQL Server and what the best practice should be.
Believe in Your Data - Database Weekly (Aug 25, 2008)
As DBAs we must secure and protect data, but what can we do when there are fundamental issues with the way the systems are designed. Steve Jones comments on problems with voting machines.
Believe in Your Data - Database Weekly (Aug 25, 2008)
As DBAs we must secure and protect data, but what can we do when there are fundamental issues with the way the systems are designed. Steve Jones comments on problems with voting machines.
Concatenating Row Values in Transact-SQL
It is an interesting problem in Transact SQL, for which there are a number of solutions and considerable debate. How do you go about producing a summary result in which a distinguishing column from each row in each particular category is listed in a 'aggregate' column? A simple, and intuitive way of displaying data is surprisingly difficult to achieve. Anith Sen gives a summary of different ways, and offers words of caution over the one you choose.
Recover from a SQL Injection Attack on SQL Server
Lately it seems like SQL Injection attacks have been increasing. Recently our team has worked through resolving a few different SQL Injection attacks across a variety of web sites. Each of these attacks had a number of similarities which proved to point back to the same source. With this information in hand, the resolution should be much quicker. As such, if your web site is attacked with SQL Injection, how should you address it? How can the identification, analysis, recovery and resolution be streamlined? What are some lessons learned?
Creating Lift Charts - SQL School Video
This video covers lift charts, an advanced data mining feature in SQL Server 2008. MVP Brian Knight walks through a data mining example that tests a model with a lift chart.
Blogs
Shifting Mindsets: Why FinOps is Essential for Cloud Efficiency
By HeyMo0sh
As a DevOps practitioner, I’ve always focused on performance, scalability, and automation. But as...
March 2026 SQL Server Security Updates
By Brian Kelley
On Patch Tuesday, in addition to OS and Office security patches, Microsoft also released...
How Fabric Mirroring Transformed with SQL Server 2025
When mirroring was first released for Azure SQL Database, it used Change Data Capture...
Forums
Multiple Deployment Processes
Comments posted to this topic are about the item Multiple Deployment Processes
How to Use sqlpackage to Detect Schema Drift Between Azure SQL Databases
Comments posted to this topic are about the item How to Use sqlpackage to...
Upgrading Admin Queries
Comments posted to this topic are about the item Upgrading Admin Queries
Question of the Day
Upgrading Admin Queries
I have a query from a former DBA that we run on SQL Server 2025 to check on database metadata. This query references sys.sysaltfiles. I want to refactor this code to be more modern. Which DMV should I reference instead?
See possible answers