https://technet.microsoft.com/en-us/library/cc917693.aspx

Frequently asked questions - SQL Server 2000 - failover clustering https://support.microsoft.com/kb/260758

SQL Server 2005 Failover Clustering White Paper

https://www.microsoft.com/downloads/details.aspx?FamilyID=818234dc-a17b-4f09-b282-c6830fead499&DisplayLang=en

Support WebCast Microsoft SQL Server 2005 Failover Clustering on Windows Server 2008

https://support.microsoft.com/kb/953170

Top Tips for SQL Server Clustering

https://technet.microsoft.com/en-us/magazine/2007.03.sqlclusters.aspx

SQL 2008 Failover Clustering Whitepaper

https://download.microsoft.com/download/6/9/D/69D1FEA7-5B42-437A-B3BA-A4AD13E34EF6/SQLServer2008FailoverCluster.docx

Getting Started with SQL Server 2008 Failover Clustering https://msdn.microsoft.com/en-us/library/ms189134.aspx 

How to: Create a New SQL Server Failover Cluster (Setup) https://msdn.microsoft.com/en-us/library/ms179530.aspx

Guidelines for choosing antivirus software to run on the computers that are running SQL Server

https://support.microsoft.com/kb/309422

Following is a compilation of all Sql server resources:

1. Sql Server Setup and Upgrade on a standalone box
2. Sql Server Setup and Upgrade on a Cluster
3. Uninstalling SQL Server 2000, 2005  & 2008 on a standalone box
4. Uninstalling SQL Server 2000, 2005  & 2008 on a Cluster
5. Sql Server Clustering
6. Security in SQL Server
7. SQL Server Corruption
8. SQL Server Tools
9. Log Shipping in Sql Server
10. Database Mirroring in Sql Server
11. SQL Server General Performance
12. Deadlock Identification and Resolution - SQL 2000 and 2005
13. Index Analysis using DMVs
14. Analysis Services 2005 - Setup and Upgrade on a Cluster
15. Reporting Services 2005 Deployment/Configuration
16. Configuring Notification/Integration Services on Cluster
17. SQLCLR in SQL 2005
18. Service Broker in SQL Server
19. SQL Server 2005 - A Developer's Perspective

A white paper for Database Administrators who have never used Log Shipping before and are interested in exploring Log Shipping as a strategy for disaster recovery is available; to access this white paper, please visit the following Microsoft Web site:   https://download.microsoft.com/download/SQLSVR2000/Utility/2.0/WIN98/EN-US/log_shipping.exe

Frequently asked questions - SQL Server 2000 - Log shipping https://support.microsoft.com/default.aspx?scid=kb;EN-US;314515

How to configure security for SQL Server log shipping https://support.microsoft.com/default.aspx?scid=kb;EN-US;321247

For more information about log shipping and typical models for its deployment, visit the following Microsoft Developer Network (MSDN) Web site:
Log Shipping https://msdn2.microsoft.com/en-us/library/aa213785(SQL.80).aspx

Backup, copy, and load job information is not updated on the log shipping monitor https://support.microsoft.com/default.aspx?scid=kb;EN-US;292586

Description of error message 14420 and error message 14421 that occur when you use log shipping in SQL Server https://support.microsoft.com/default.aspx?scid=kb;EN-US;329133

Log Shipping Monitor out-of-synchronization messages are incorrectly raised in an outage period in Microsoft SQL Server 2000 Enterprise Edition
https://support.microsoft.com/default.aspx?scid=kb;EN-US;311177

Support WebCast: Microsoft SQL Server 2000 Log Shipping https://support.microsoft.com/default.aspx?scid=kb;EN-US;325220

Support WebCast: Microsoft SQL Server 2000: Using Log Shipping https://support.microsoft.com/default.aspx?scid=kb;EN-US;821786]]> https://docs.microsoft.com/archive/blogs/pradipta/sql-server-setup-and-upgrade-on-a-cluster Tue, 27 Apr 2010 06:26:21 GMT https://blogs.msdn.microsoft.com/pradipta/2010/04/27/sql-server-setup-and-upgrade-on-a-cluster/ Setup a SQL 2005 Cluster from ground-up

Since the minimum hardware and software requirements for SQL 2005 have changed, I would suggest that you start by reviewing this article. You can confirm that your hardware and software meets the minimum requirements for sure.

https://msdn2.microsoft.com/en-us/library/ms143719.aspx

There are special considerations for SQL 2005 Clusters that you should be aware of. Review this link to ensure that you have configured all the pre-requisites before running the SQL 2005 setup.

https://msdn2.microsoft.com/en-us/library/ms189910.aspx

Also, SQL 2005 cluster setup prompts you for domain accounts. You need to have these domain accounts setup in advance. Refer to this article which talks about what to do and some of the best practices for setting up domain accounts.

https://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B915846

Once the pre-requisites are met, follow the instructions in this article to setup a SQL 2005 failover cluster.

https://msdn2.microsoft.com/en-us/library/ms179530(SQL.90).aspx

Upgrade from SQL 2000 and 7.0

The first step is to check if the upgrade from you existing SQL 2000 edition is supported. You can review the Version and Edition Upgrade Paths Matrix to learn more about it.https://msdn2.microsoft.com/en-us/library/ms143393(SQL.90).aspx

After you have confirmed that a direct upgrade path exists for your edition of SQL Server, you should do a sanity check by running the upgrade advisor. Some old features in SQL 2005 have either been deprecated or removed. To find out if you are using any feature that has been deprecated or removed in SQL 2005, run Upgrade Advisor tool against your SQL 2000 databases. This tool will give you a list of things to correct pre, during and post upgrade process in your database. I would strongly encourage you to run this tool in advance of your upgrade planning.

https://msdn2.microsoft.com/en-us/library/ms144256(SQL.90).aspx

After having confirmed that there are no upgrade blocking issues for your database, you can upgrade your existing cluster in-place by following the steps highlighted in this article.

https://msdn2.microsoft.com/en-us/library/ms191295(SQL.90).aspx

Once the setup is complete, it is important to verify that the SQL Server is configured and setup right. You can verify that by using the SQL Server setup logs. However, these logs are verbose and you need to know what you are looking for. To learn how to sniff the right information from these logs, refer to this aticle.

https://msdn2.microsoft.com/en-us/library/ms143702.aspx

Maintenance of a SQL 2005 Cluster

Here is a list of a few How-To articles that should come in handy to learn about the best practices of doing the mundane tasks.

https://msdn2.microsoft.com/en-us/library/ms190990(SQL.90).aspx

Also, on a cluster, a lot of stuff is different from a standalone box. Here is a list of clustered SQL do's and don'ts - a must read.

https://support.microsoft.com/?id=254321

Here is the SQL Server Clustering white paper.

• SQL Server 2005 Failover Clustering White Paper

https://www.microsoft.com/downloads/details.aspx?familyid=818234dc-a17b-4f09-b282-c6830fead499&displaylang=en

Known Issues:

List of known issues when you install SQL Server 2005 on Windows Server 2008  https://support.microsoft.com/?id=936302

List of known issues when you install SQL Server on Windows 7 or on Windows Server 2008 R2  https://support.microsoft.com/?id=955725

How to apply a hotfix for SQL Server 2005 or SQL Server 2008 in a transactional replication and database mirroring topology  https://support.microsoft.com/kb/977051

SQL Server 2000 / 2005 Failover Cluster Pre-installation Checklist https://blogs.msdn.com/arvindsh/archive/2009/01/03/sql-server-2000-2005-failover-cluster-pre-installation-checklist.aspx
 
Support WebCast: Microsoft SQL Server 2005 Failover Clustering on Windows Server 2008  https://support.microsoft.com/kb/953170

I would strongly recommend that you start by reading about the pre-requisites of installing SQL 2005.

https://msdn2.microsoft.com/en-us/library/ms143719.aspx

If you want to install SQL 2005 side-by-side with SQL 2000 or 7.0, you need to be aware of some special considerations. Refer to this article.

https://msdn2.microsoft.com/en-us/library/ms143694.aspx

After ensuring the pre-requisites are met, you should follow the steps mentioned in this article to install a SQL 2005 standalone instance on your machine.

https://msdn2.microsoft.com/en-us/library/ms143219.aspx

If you prefer to install SQL 2005 from command-prompt, you can do that too by following the steps highlighted in this article.

https://msdn2.microsoft.com/en-us/library/ms144259.aspx

Upgrade to a SQL 2005 Standalone instance from SQL 2000 and 7.0

The first step is to check if the upgrade from you existing SQL 2000 edition is supported. You can review the Version and Edition Upgrade Paths Matrix to learn more about it.https://msdn2.microsoft.com/en-us/library/ms143393(SQL.90).aspx

After you have confirmed that a direct upgrade path exists for your edition of SQL Server, you should do a sanity check by running the upgrade advisor. Some old features in SQL 2005 have either been deprecated or removed. To find out if you are using any feature that has been deprecated or removed in SQL 2005, run Upgrade Advisor tool against your SQL 2000 databases. This tool will give you a list of things to correct pre, during and post upgrade process in your database. I would strongly encourage you to run this tool in advance of your upgrade planning.

https://msdn2.microsoft.com/en-us/library/ms144256(SQL.90).aspx

After having confirmed that there are no upgrade blocking issues for your database, you should read more about some of the known issues with upgrade of each component of SQL Server and how to avoid them by visiting this link:

https://msdn2.microsoft.com/en-us/library/ms143710(SQL.90).aspx

Once the ground work is complete, you can upgrade your existing standalone instance in-place by following the steps highlighted in this article.

https://msdn2.microsoft.com/en-us/library/ms144267.aspx

Make sure that you follow the steps in the above upgrade article in the section titled Next Steps. This section talks about updating the statistics after upgrade and also about using DBCC UPDATEUSAGE. These steps are important from performance point of view.

Post Setup and Upgrade Activities

Once the setup is complete, it is important to verify that the SQL Server is configured and setup right. You can verify that by using the SQL Server setup logs. However, these logs are verbose and you need to know what you are looking for. To learn how to sniff the right information from these logs, refer to this aticle.

https://msdn2.microsoft.com/en-us/library/ms143702.aspx

Known Issues:

List of known issues when you install SQL Server 2005 on Windows Server 2008 https://support.microsoft.com/?id=936302

List of known issues when you install SQL Server on Windows 7 or on Windows Server 2008 R2 https://support.microsoft.com/?id=955725

How to apply a hotfix for SQL Server 2005 or SQL Server 2008 in a transactional replication and database mirroring topology https://support.microsoft.com/kb/977051]]> https://docs.microsoft.com/archive/blogs/pradipta/reporting-services-2005-deploymentconfiguration Tue, 27 Apr 2010 06:18:23 GMT https://blogs.msdn.microsoft.com/pradipta/2010/04/27/reporting-services-2005-deploymentconfiguration/ Many resources are available about SQL Server 2005 Reporting Services deployment and configuration options. However, here is a list of resources that we refer to and thought will share with you. 

Planning for Scalability and Performance with Reporting Services

Whether to scale-out or scale-up depends on your performance and load requirements. Refer to the following whitepaper for performance optimization tips and a comprehensive discussion that will help you decide which configuration is best for your situation.

https://www.microsoft.com/technet/prodtechnol/sql/2005/pspsqlrs.mspx

Accounts in a Reporting Services Deployment

When installing Reporting Services, you will need to consider the accounts and connections that are used.  The following MSDN article provides an overview.

https://msdn2.microsoft.com/en-us/library/ms159846(SQL.90).aspx

Configuring Report Server Security

You must analyze security options for the Reporting Services installation depending (among other things) on whether you will be internet facing or intranet facing.  For an overview, I recommend reviewing the following:

https://msdn2.microsoft.com/en-us/library/ms157198(SQL.90).aspx

If you require an internet facing installation, please review some additional configuration requirements:

https://msdn2.microsoft.com/en-us/library/ms159272(SQL.90).aspx

Deploying Reporting Services and Windows SharePoint Services Side-by-Side

This type of deployment requires a special configuration.  For more information, follow the instructions in the MSDN article below:

https://msdn2.microsoft.com/en-us/library/ms159697(SQL.90).aspx

Reporting Services Configuration Tool

Reporting Services 2005 has made configuration much simpler through the use of the Reporting Services Configuration Utility.  I highly recommend becoming acquainted with the tool.  For more information, see the following:

https://msdn2.microsoft.com/en-us/library/ms156305.aspx

1. Reporting services

2. Notification services

3. Integration services

Here are the articles using which we can configure Notification services and Integration Services on cluster group.

• Using Failover Clustering with Notification Services

https://msdn2.microsoft.com/en-us/library/ms171407.aspx

• How to: Configure Integration Services on a Cluster

https://msdn2.microsoft.com/en-us/library/ms345193.aspx

Statistics used by SQL 2005

As we know, existence and the subsequent updates of statistics is a very important factor governing SQL Server query performance. However, the implementation details are different in SQL 2005. Understand the nuances by referring to this article https://www.microsoft.com/technet/prodtechnol/sql/2005/qrystats.mspx

Troubleshooting Performance Problems in SQL Server 2005 - Whitepaper   https://sqlcat.com/whitepapers/archive/2007/11/19/troubleshooting-performance-problems-in-sql-server-2005.aspx

Caching in SQL Server 2005 and how it impacts performance

SQL Server, just like any other RDBMS, tries to minimize disk I/O. It achieves this balance by caching the data in memory. However, since memory is a limited resource, it is imperative that you implement the best practices to maximize your use of it. This is an excellent white paper that talks about the internals of SQL Server caching, with a focus on compilations and re-compilations of batches in SQL 2005.

Batch Compilation, Recompilation, and Plan Caching Issues in SQL Server 2005 - Whitepaper https://www.microsoft.com/technet/prodtechnol/sql/2005/recomp.mspx

Performance Analysis and Troubleshooting SQL Server 2005

This is an excellent whitepaper that provides scripts and queries to monitor, identify performance bottlenecks and suggests improvements. I would strongly recommend this - a must read.

https://www.microsoft.com/technet/prodtechnol/sql/2005/tsprfprb.mspx

SQL 2005 Webcasts

I thought I will also provide some links to useful webcasts. I love the format of the webcasts and the ease of replaying stuff at will.

Performance Diagnosis in SQL 2005

All production databases need to be high performing. However, often times, we don't have solid performance benchmark numbers which we should aim and maintain in the long run. The first step, then is to monitor SQL Server performance during the good and bad times. Based on the data collected during bad times and comparing them to the one collected during good times, we can see what is causing this slow performance. This 300 level webcast talks about performance monitoring and troubleshooting best practices.

https://msevents.microsoft.com/cui/webcasteventdetails.aspx?eventid=1032275587&eventcategory=5&culture=en-us&countrycode=us

Troubleshooting Performance Problems in Microsoft SQL Server 2005

Once you have monitored the performance over a period of time, you can use the techniques in this webcast to troubleshoot the performance bottlenecks. This webcast provides some really good practical advise on troubleshooting performance https://msevents.microsoft.com/cui/webcasteventdetails.aspx?eventid=1032275647&eventcategory=5&culture=en-us&countrycode=us 

This paper provides step-by-step guidelines for diagnosing and troubleshooting common performance problems by using publicly available tools such as SQL Server Profiler, System Monitor, and the new Dynamic Management Views in SQL Server 2005 https://technet.microsoft.com/en-us/library/cc966540.aspx

How to troubleshoot the performance of Ad-Hoc queries in SQL Server https://support.microsoft.com/default.aspx?scid=kb;EN-US;243588

Tuning options for SQL Server 2005 and SQL Server 2008 when running in high performance workloads https://support.microsoft.com/default.aspx?scid=kb;EN-US;920093

How to troubleshoot SQL Server performance issues https://support.microsoft.com/default.aspx?scid=kb;EN-US;298475

Description of the SQL Server Performance Analysis Utilities Read80Trace and OSTRESS https://support.microsoft.com/default.aspx?scid=kb;EN-US;887057

Understanding and Resolving SQL Server Blocking Problems: This article discusses how to troubleshoot and resolve blocking problems https://support.microsoft.com/kb/224453

Wait Types

SQL Server 2005 Waits and Queues - Whitepaper https://sqlcat.com/whitepapers/archive/2007/11/19/sql-server-2005-waits-and-queues.aspx

The SQL Server Wait Type Repository. https://blogs.msdn.com/psssql/archive/2009/11/03/the-sql-server-wait-type-repository.aspx

Tempdb

TEMPDB Capacity Planning and Concurrency Considerations for Index Create and Rebuild - Whitepaper
https://sqlcat.com/whitepapers/archive/2007/11/20/tempdb-capacity-planning-and-concurrency-considerations-for-index-create-and-rebuild.aspx

Working with tempdb in SQL Server 2005 - Whitepaper
https://technet.microsoft.com/hi-in/library/cc966545(en-us).aspx

This white paper describes how SQL Server 2005 uses tempdb. Many improvements in SQL Server 2005 optimize tempdb usage and make it easier to manage and to troubleshoot.
https://download.microsoft.com/download/4/7/a/47a548b9-249e-484c-abd7-29f31282b04d/WorkingWithTempDB.doc

SQL SERVER 2008

Troubleshooting Performance Problems in SQL Server 2008 - Whitepaper  https://sqlcat.com/whitepapers/archive/2009/04/14/troubleshooting-performance-problems-in-sql-server-2008.aspx

Statistics Used by SQL 2008

This paper describes what data is collected, where it is stored, and which commands create, update, and delete statistics https://msdn.microsoft.com/en-us/library/dd535534.aspx

Improving Performance with SQL Server 2008 Indexed Views

This document describes the indexed views capability of SQL Server 2005 and SQL Server 2008, including the new support for partition-aligned views added to SQL Server 2008.
https://msdn.microsoft.com/en-us/library/dd171921.aspx

Troubleshooting Performance Problems in SQL Server 2008

This paper provides step-by-step guidelines for diagnosing and troubleshooting common performance problems by using publicly available tools such as SQL Server Profiler, System Monitor, and the new Dynamic Management Views in SQL Server 2005 https://download.microsoft.com/download/1/3/4/134644fd-05ad-4ee8-8b5a-0aed1c18a31e/TShootPerfProbs.doc

You may experience slow performance when you run 32-bit SQL Server tools on 64-bit operating systems https://support.microsoft.com/default.aspx?scid=kb;EN-US;906892

SQL Server 2000 IO basics :

Learn the I/O requirements for Microsoft SQL Server database file operations. This will help you increase system performance and avoid I/O environment errors. Applicable to SQL 2005 and 2008

SQL Server I/O Basics https://technet.microsoft.com/en-us/library/cc966500.aspx

SQL Server I/O Basics, Chapter 2 https://technet.microsoft.com/en-us/library/cc917726.aspx

PERFORMANCE TOOLS FOR SQL SERVER:

SQL Nexus is a tool that helps you identify the root cause of SQL Server performance issues https://www.codeplex.com/sqlnexus

RML Utilities/ReadTrace :This article describes one utility suite that is called the Replay Markup Language (RML) Utilities for Microsoft SQL Server https://support.microsoft.com/kb/944837

SQL Server Performance Dashboard:

The SQL Server Performance Dashboard is an invaluable tool for monitoring your server's performance. It can be installed on any SQL Server 2005 machine with SP2 that you want to monitor. Just run the msi package and then run the setup.sql script that comes with it on any instance that you want to monitor. It monitors the instance on the local machine. The setup.sql script is located in C:\Program Files (x86)\Microsoft SQL Server\90\Tools\Performance Dashboard after running the msi script.

After you install the Performance dashboard and run setup.sql, just right-click on the server in SQL Management Studio. Choose 'Reports' -> 'Custom Reports'. The first time you do this you'll have to navigate to the same Performance Dashboard directory to find the performance_dashboard_main.rdl file. Choose this file and the dashboard will open to show you the activity on your SQL Server, using the native Distributed Management Views from SQL 2005.

Get the SQL Server 2005 Performance Dashboard at https://www.microsoft.com/downloads/details.aspx?FamilyId=1D3A4A0D-7E0C-4730-8204-E419218C1EFC&displaylang=en

Get the SQL Server 2008 Performance Dashboard at https://blogs.technet.com/rob/archive/2009/02/18/performance-dashboard-reports-for-sql-server-2008.aspx

SQL Server Performance Blogs

The folks who wrote the code in SQL Server have blogs of their own. These blogs provide in-depth knowledge about SQL Server internals -  like the query optimizer, the SQL OS etc. - stuff that is not there either in Books Online or at MSDN. I would strongly encourage you to read these blogs, if you really want to learn about the esoteric internals of SQL Server.

Slava Oks Blog on SQL OS and Memory https://blogs.msdn.com/slavao/

Blog on Query Optimizer written by the folks who wrote the query optimizer https://blogs.msdn.com/queryoptteam/

SQL Tips and Tricks Blog - handy tips and tricks to do mundane tasks in SQL 2005 https://blogs.msdn.com/sqltips/default.aspx

Craig Freedman's SQL Server blog : A discussion of query processing, query execution, and query plans in SQL Server https://blogs.msdn.com/craigfr/

Tips, Tricks, and Advice from the SQL Server Query Processing Team : Provides tips, tricks, advice and answers to frequently-asked questions in a continued effort to make your queries run faster and smoother in SQL Server https://blogs.msdn.com/sqlqueryprocessing/

Using DMVs to find out the index usage history

Over a period of time, you could create a lot of indexes on your tables and modify existing ones. However, in SQL 2000, you couldn't estimate how effective were each of these indexes. Poorly design indexes could lead to performance overhead instead of enhancing performance.

In SQL 2005, you can query the sys.dm_db_index_usage_stats DMV to find out the indexes that have NEVER been used since the last start of SQL Server. You can use the following query to find that out:

select object_name(i.object_id) as ObjectName,

i.name as IndexName, s.user_updates,  s.user_seeks, s.user_scans, s.user_lookups

from sys.indexes i 

            left join sys.dm_db_index_usage_stats s

on s.object_id = i.object_id and  i.index_id = s.index_id and s.database_id = <dbid>

where objectproperty(i.object_id, 'IsIndexable') = 1 and

-- index_usage_stats has no reference to this index (not being used)

s.index_id is null or

-- index is being updated, but not used by seeks/scans/lookups

(s.user_updates > 0 and s.user_seeks = 0

and s.user_scans = 0 and s.user_lookups = 0)

order by object_name(i.object_id) asc\

In the output, you will ALL the indexes that have never been used by any sort of workload on your server, since the last start of SQL Server.

• For indexes that have NEVER been used (either for a SELECT or a DML statement), all columns will be NULL
• For indexes that have NEVER been used (for a SELECT), but had to be updated due to a DML statement, the user_updates column will be >0, while other columns will be 0. It is these indexes that could cause severe performance overhead for your DML statements and might be worth dropping.

Give ample time for SQL Server to get exposed to all the workload after a restart, before running this query.

Using DMVs to find out missing indexes

When the query optimizer generates a query plan, it analyzes what are the best indexes for a particular filter condition. If the best indexes do not exist, the query optimizer generates a suboptimal query plan, but still stores information about these indexes. The missing indexes feature enables you to access information about these indexes so you can decide whether they should be implemented.

For more information on how to use this feature, please visit the following link

https://msdn2.microsoft.com/en-us/library/ms345417.aspx

Using DMVs to find out index fragmentation

The sys.dm_db_index_physical_stats dynamic management function replaces the DBCC SHOWCONTIG statement.

You can learn more about using this DMV to identify fragmentation, correcting it and possibly automating this activity for your server by visiting the following link:

https://msdn2.microsoft.com/en-us/library/ms188917.aspx

Online Indexing Operations in SQL Server 2005 - Whitepaper
https://www.microsoft.com/technet/prodtechnol/sql/2005/onlineindex.mspx

Comparing Tables Organized with Clustered Indexes versus Heaps - Best Practices article
https://technet.microsoft.com/en-us/library/cc917672.aspx]]> https://docs.microsoft.com/archive/blogs/pradipta/deadlock-identification-and-resolution-sql-2000-and-2005 Tue, 27 Apr 2010 06:09:19 GMT https://blogs.msdn.microsoft.com/pradipta/2010/04/27/deadlock-identification-and-resolution-sql-2000-and-2005/ Deadlocking - what is it and why does it happen?

A deadlock occurs when two or more tasks permanently block each other by each task having a lock on a resource which the other tasks are trying to lock. Refer to this article which talks in detail about it.

https://msdn2.microsoft.com/en-us/library/ms177433.aspx

Identifying a deadlock

SQL Server provides different ways to identify deadlocks - through profiler trace or by enabling a traceflag. If you enable the traceflag, you can see the deadlock written in the errorlogs.

This article sheds some light on the process of identifying a deadlock and reading the graph.

https://msdn2.microsoft.com/en-us/library/ms178104(SQL.90).aspx

Resolving deadlocks

After having identified a deadlock, it is crucial to understand the sequence of events that lead to it. Refer to these article for troubleshooting steps and some of the best practices recommendations for avoiding deadlocks.

https://msdn.microsoft.com/library/default.asp?url=/library/en-us/trblsql/tr_servdatabse_5xrn.asp

https://support.microsoft.com/kb/832524/en-us

Special considerations for SQL 2005

SQL Server 2005 provides better concurrency control than SQL 2000 by way of Snapshot Isolation. You might want to review this webcast to learn more about it and see if it can be used in your application design.

https://msevents.microsoft.com/cui/WebCastEventDetails.aspx?EventID=1032270011&EventCategory=3&culture=en-US&CountryCode=US

Deadlock Troubleshooting - Bart Duncan

Deadlock Troubleshooting, Part 1 https://blogs.msdn.com/bartd/archive/2006/09/09/747119.aspx

Deadlock Troubleshooting, Part 2 https://blogs.msdn.com/bartd/archive/2006/09/13/751343.aspx

Deadlock Troubleshooting, Part 3 https://blogs.msdn.com/bartd/archive/2006/09/25/770928.aspx