Articles

SQLServerCentral Article

Best Practices are always the Best

On this site, we have taken a contrarian approach to looking at the ways to configure SQL Server with our Worst Practices series. However Microsoft still looks at it from the other side and release a tool called the Best Practices Analyzer for SQL Server. Author Dinesh Asanka brings us a short look at this tool.

(1)

You rated this post out of 5. Change rating

2004-11-11

12,629 reads

Technical Article

The OLE DB Command Transformation

In the newsgroups we have been asked on a number of occasions how to execute a stored procedure once for every row of input data. There's currently no really good way of doing this but in SQL Server 2005 DTS that is about to change. This article is going to show you how to take values from a source table and for every row execute a stored procedure which inserts values into another table.

2004-11-11

1,551 reads

SQLServerCentral Article

An Alternative XML Solution

SQL Server 2000 added support for XML documents in a few ways. However the support was a little kludgy as it had not been designed into the product from the beginning, but added on later. New author Wayne Fillis brings us some C++ code and a new way to easily retrieve well formed XML documents from your SQL Server.

You rated this post out of 5. Change rating

2004-11-10

8,641 reads

SQLServerCentral Article

Worst Practice - Detailed Disaster Plans

Another in our series of things you should avoid at all costs. Seems silly at first, not having a detailed recovery plan for your SQL Server. Perhaps it is, but having dealt with any number of problems over the last few years, Steve Jones has some ideas why a detailed plan may not be the best thing to spend your time on.

You rated this post out of 5. Change rating

2004-11-09

8,071 reads

Technical Article

SQL Server 2005 Express Edition Overview

SQL Server Express, a free product based on SQL Server 2005 technology, includes the unique Application XCopy feature, and networking and security that differ from other SQL Server 2005 editions. These topics and the integration of SQL Server Express with Visual Studio 2005 are discussed. Compare this product with the existing Microsoft free databases like MSDE and Jet.

2004-11-09

2,735 reads

Technical Article

SQL Server 2005 Partitioned Tables and Indexes

Although partitioning tables and indexes has always been a design tactic chosen to improve performance and manageability in larger databases, Microsoft SQL Server 2005 has new features that simplify the design. This whitepaper describes the logical progression from manually partitioning data by creating your own tables to the preliminary features, which enabled partitioning through views in SQL Server 7.0 and SQL Server 2000, to the true partitioned table features available in SQL Server 2005. In SQL Server 2005, the new table-based partitioning features significantly simplify design and administration of partitioned tables while continuing to improve performance.

2004-11-05

3,625 reads

Blogs

Shifting Mindsets: Why FinOps is Essential for Cloud Efficiency

By

As a DevOps practitioner, I’ve always focused on performance, scalability, and automation. But as...

March 2026 SQL Server Security Updates

By

On Patch Tuesday, in addition to OS and Office security patches, Microsoft also released...

How Fabric Mirroring Transformed with SQL Server 2025

By

When mirroring was first released for Azure SQL Database, it used Change Data Capture...

Read the latest Blogs

Forums

Multiple Deployment Processes

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Multiple Deployment Processes

How to Use sqlpackage to Detect Schema Drift Between Azure SQL Databases

By Kunal Rathi

Comments posted to this topic are about the item How to Use sqlpackage to...

Upgrading Admin Queries

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Upgrading Admin Queries

Visit the forum

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