Identity Columns
When Nigel Rivett takes us on a tour of the apparently innocuous subject of Identity Columns in TSQL, even the seasoned programmer is due for one or two surprises.
Introduction to SQL 2005 Profiler Part 1
Profiler is a tool that monitors the events and activity running on a SQL Server. Using profiler, this monitoring can be viewed, saved, and replayed. This article focuses on using Profiler with SQL Server 2005, but the tool is also included with SQL Server 2000 and SQL Server 2008.
A Private Database
Having separate databases for each client? It's a common problem and Steve Jones wonders if this might be a feature coming in SQL Server at some point.
Audit Trails and Logging Part I
Auditing becomes more important every day as new requirements for data access are implemented. New author Gsquared, well known in the forums, brings us a look at types of audits and some details on passive auditing techniques.
Open Source and SQL Server communities
The other day, I was chatting to a keen PostgreSQL user. We're used to having free databases, such as IBM DB2 Express-C, Microsoft SQL Server 2005 Express Edition, SQLite and Oracle XE, but PostgreSQL is different in that it is open source. It is a proper, dedicated community too, I was told...
Options for scripting database objects
SQL Server Management Studio is rich with features. So rich, in fact, that after almost 3 years I am still finding new tools in the application that afford me more control over my databases and the methods for supporting them. Recently I found myself needing to script out a database and its objects for reviewing a problem offline.
The Bulldogs
Steve Jones talks about IT Project Failure and how you should re-evaluate things are you move forward.
The Bulldogs
Steve Jones talks about IT Project Failure and how you should re-evaluate things are you move forward.
The Bulldogs
Steve Jones talks about IT Project Failure and how you should re-evaluate things are you move forward.
Using the OUTPUT clause for practical applications
Learn how using the OUTPUT clause in SQL Server 2005 queries simplifies T-SQL code and returns results of rows changed by an INSERT, UPDATE or DELETE SQL command.
Blogs
Advice I Like: Knots
By Steve Jones
Learn how to tie a bowline knot. Practice in the dark. With one hand....
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...
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