Additional Articles


Technical Article

Using TRY/CATCH to Resolve Deadlocks in SQL Server 2005

Deadlocks are unavoidable artifacts of today's RDBMS architecture–and all too common in high-volume OLTP environments. But thanks to .NET's Common Language Runtime (CLR), SQL Server 2005 provides developers with a new way to deal with error handling. In this month's column, Ron Talmage shows you how to harness TRY/CATCH to help resolve a deadlock.

You rated this post out of 5. Change rating

2005-08-15

2,347 reads

External Article

Database Geek of the Week - Shawn Wildermuth

Shawn Wildermuth is the “go-to guy” for information on ADO.NET. He is the author of Pragmatic ADO.NET: Data Access for the Internet World and numerous articles, is a Microsoft MVP, and works as an independent consultant in Atlanta.

Shawn’s web site, The ADO Guy, is a good resource for developers looking for answers to questions about ADO and ADO.NET. The site also lists interesting blogs, books and sites that are among Shawn’s favorites.

2005-08-11

1,821 reads

External Article

ADO.NET Data Sets

This article looks at how partial classes can be used to implement business logic into datasets so that they are more business aware and intelligent.

The dataset is an integral part of Microsoft’s new data access model ADO.NET. It introduces a simple offline method for retrieving and updating data. Before using the dataset, you should have an understanding of the Microsoft .NET platform and a basic understanding of the dataset model.

2005-08-05

3,652 reads

Technical Article

Michael Rys on XML in SQL Server 2005

Michael Rys is one of two program managers responsible for the XML features in SQL Server. He also represents Microsoft on the W3C XQuery Working Group, and on the ANSI working group for SQL. I asked him what is distinctive about the XML support in SQL Server 2005, as opposed to that found in rival database management systems. As Rys acknowledges, "all the three major vendors, Oracle, IBM and Microsoft, are moving towards second or third generation suppor

2005-08-04

1,979 reads

Technical Article

SQL Server Integration Services - Part 5

We will continue our review of Foreach enumerators starting with Foreach ADO, since this one probably qualifies as the most popular choice in its category. This is due to the fact that ADO recordsets offer a convenient way of dealing with data sources, regardless of their type (for example, within SSIS, you can easily populate a recordset by executing a SQL query or by reading the content of a flat file)

You rated this post out of 5. Change rating

2005-08-01

1,791 reads

External Article

Attack of the predatory sales force

Most skilled professionals—be they butchers, bakers or software makers—take pride in selecting their own tools of the trade. Why is it then that developers and DBAs in large corporations often are not afforded the same professional courtesy or opportunity? The tools they use are just as vital to their livelihood, yet when it comes to high-cost software, developers and DBAs often have no input into what is purchased for their use.

2005-07-29

2,572 reads

External Article

The identity crisis in replication

This article discusses three common problems DBAs are likely to encounter when columns have the identity property, which is defined as an attribute of int, smallint, bigint, decimal, numeric or tinyint columns that will auto-increment their value when data is inserted. These problems are humorously referred to as the identity crisis.

2005-07-28

3,765 reads

Blogs

When Your Microsoft Fabric Capacity Runs Out: Optimize, Scale Up, Scale Out, or Isolate?

By

Microsoft Fabric makes it wonderfully easy to put many analytics workloads on one platform....

Accessing the Data API Builder MCP Server from VS Code

By

I recently started playing with the MCP Server for SQL Server, which is a...

From DBA or Data Engineer to AI Engineer: A Realistic Path

By

If you spend your days tuning queries, managing pipelines, or keeping a production database...

Read the latest Blogs

Forums

Two queries work until compared with EXCEPT statement

By Leo.Miller

I've got multiple databases on 2 SQL 2019 CU32 servers , all using the...

STRING_AGG DISTINCT

By Phil Parkin

Has anyone written a wrapper function (or similar) around STRING_AGG() to allow the retrieval...

In-place OS upgrade or migration to new OS?

By jasona.work

Putting this here as we're currently on SQL Server 2019 installed on Windows Server...

Visit the forum

Question of the Day

Rebuilding All Indexes

I have added a few indexes to one of my tables in SQL Server 2025:

ALTER TABLE dbo.CustomerContact
ADD CONSTRAINT PK_CustomerContact
    PRIMARY KEY (CustomerID);

-- Create index on CustomerEmail
CREATE INDEX IX_CustomerContact_CustomerEmail
ON dbo.CustomerContact (CustomerEmail);
CREATE INDEX IX_CustomerContact_CustomerPhone
ON dbo.CustomerContact (phone);
I then do this to disable one index:
alter index IX_CustomerContact_CustomerPhone on dbo.CustomerContact disable
I see this when I check the index status:Index status for CustomerContactI decide to rebuild all indexes with this command:
ALTER INDEX ALL ON dbo.CustomerContact rebuild
After I do this, what will I see for the index status?

See possible answers