This is an extended stored procedure for Microsoft SQL Server 2000 that implements an optimized MD5 hash algorithm. It is intended to work much like the MySQL MD5() function. The algorithm was taken from here. I only added the md5_string() function. The DLL should work for older versions of SQL Server too, although I have not tested that.

Installation

Extract or build the DLL file xp_md5.dll and place it in C:\Program Files\Microsoft SQL Server\MSSQL\Binn (or wherever appropriate). A precompiled DLL is in the Release directory of the source distribution.

Create an Extended Stored Procedure called xp_md5 in the "master" database. Right-click "Extended Stored Procedures" under the master database in the Server Manager and click "New Extended Stored Procedure...". Enter xp_md5 for the "Name" and for the "Path", enter the full path to xp_md5.dll.

Instructions on using SQL Server 2005 SP1 in the FIPS 140-2 compliant mode
SQL Server 2000 and MSDE will not be supported on Windows Vista
SQL Server Health and History Tool (SQLH2)

A Microsoft Distributed Transaction Coordinator (MS DTC) transaction commit operation may cause a blocking scenario on itself. In the SQL Server sysprocesses table output, the SQL Server process ID number (SPID) is less than 50 and shows a self...

When Microsoft Data Access Components (MDAC) version 2.6 is installed, each attempt to connect to a SQL Server 7.0 or SQL Server 2000 database using an IP address (rather than the server name) may take longer than anticipated. "In certain reported...

Lakeside SQL Trace Analyzer ™ is a tool that analyzes data collected by Microsoft SQL Profiler to pinpoint performance problems. Trace Analyzer ™ generates statistics and identifies problem areas to give a clear picture of what goes on inside your system – from CPU health to procedural statistics to errors.

The tool displays findings such as most resource intensive lines of code or longest running queries in easy-to-read reports that can be shared with the development team so that problems can be addressed.

A trigger can be created on a table which will fire whenever the data in that table is updated (insert, update, delete). There are two types of trigger available 1. After triggers - these were the only type avaiable pre v2000 and are the default. These triggers fire after the data is updated - hence if the data violates a constraint then the error will occur before the trigger fires. It is possible to define multiple after triggeres on a table. These will all fire. The first and last trigger to firs can be set by sp_settriggerorder. 2. Instead of triggers. These triggers fire instead of the update taking place and can be applied to updateable views. This means that the trigger can alter the data to fit in with database integrity but has the added complication that the trigger must apply the updates itself. Of course only one instead of trigger is allowed on a table.