Well, it might also depend on your hardware and the processes on the server, when you are attempting the restore.

Take a look here: http://support.microsoft.com/kb/924807

General Suggestion: DTS object model is not supported in SSIS like Dim packageind= DTSGlobalVariables.Parent and replace all NULL values with " " in the script for 2005.

did you check filter by table_schema in information_Schema.columns.

Check out PAUL RANDAL's BLOG at sqlskills.com, Lots of info about Disaster Recovery and internals

Are you running some huge Reports/Queries.

Are you connecting to another HOST(Remote Login/Linked Server)

are you making connections to other RDBMS systems. ORACLE etc.

If Linked Server Check the Provider Properties and Uncheck...

Other Options:

SELECT state_desc FROM sys.databases WHERE name = 'dbname';

SELECT DATABASEPROPERTYEX ('dbname', 'STATUS');

ALTER DATABASE dbname SET EMERGENCY (This will only be available to members of SYSADMIN role)

Oops i missed on a value in youe opening post.

This suggeste you have a heap table. Right? a table without indexes.

So a Heap table can be more fragmented under lots...

Well no gains without pains.

Best option will be to error check with the object_id exists againsts each object lookup in the script or redo the script to serialize the steps.

Was the job created through maint Plan, if yes did you change the job outside of the maint plan, i.e. did u make changes to the job without the maint...

Check on the SQL Server 2005 upgrade Advisor.

QuickTips:

Are you having the same Drive/path structure on SQL 2005 Server.

you can Detach-Attach your Databases.

Restore from backups.

Check for Paths if you get...

But Does that give you what you want? you mentioned something about the detailed description about what each role is about right.. and this function only extends the roles like...

since it is a BLOG Type format, you can store it in the Database, if this is a frequent exercise and you have big Images, better to have a link...

Ok here is what i exactly figured out.. check this out:

http://sql-server-performance.com/Community/forums/p/13952/80618.aspx

is it giving frequent Dumps. as form your configuration it looks like Memory pressure.. read about Memory Leaks and Memory pressure on BOl or Google around for more info...I will...

Here is a good old article check ths out:

http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/ss2kidbp.mspx#EJKAC