Jay Hollingum - Works in IT

Finally I've updated my own little piece of internet real estate. It's only taken 7 years to get round to it. As fun a project as it was, developing my own ActionScript 1.0 3D engine all those years ago, the old site ( www.uk79.com ) is a little dated now to say the least, with an entrance page, recommendations for processors and screen resolution, total neglect for accessibility and search engines, so on and so forth. It was all so cutting edge in the early 21st century, at a time when Flash and animation was going to rule the www, but it was definitely time to revamp and update. jayhollingum.com still needs a bit of work and a few tweaks to it, but it's going to be a hell of a lot easier to maintain and develop further.

A bit of old school SQL Server 2000 stuff that I had to delve in to, to resuscitate a dying database using sp_who2. Running the command sp_who2 gives details of the current sessions, users and processes running in an instance of SQL Server. It's an undocumented version of the sp_who command ( http://msdn.microsoft.com/en-us/library/ms174313.aspx ) but sp_who2 gives a bit more info as to what certain processes are doing. From this, you can get a feel for what sessions and processes are hanging the database, or are being blocked, or just generally causing problems in the current running sessions of the instance of SQL Server. Once the SPID (Server Process ID) is known that is causing issues, this can be used to get the sql_handle from sysprocesses. The sql_handle is a binary key that references queries in the procedure cache. After getting the sql_handle, the function fn_get_sql can be used to reveal the SQL statement that seems to be causing issues. DECLARE @Handle varbinary