Can also verify the actual system tables in MSDB if they show run duration greater than 26 hours

use msdb

/* Below script will give job name and description if any which...

Thanks for sharing the information , will need to test it further to confirm

-Sat 🙂

Try customizing the results of system stored procedure run against master database

use master

sp_helpdb

-:-)

can provide the hardware specification for both systems ?

RAM , CPU, etc...

Also the sp_configure server settings for both systems ?

-:-)

If you are restoring from SQL 2005 back up on SQL 2008 , have you tried the restore copy script instead of GUI as well ?

If not suggest you to...

Not able to reproduce the message you are getting script is executing fine in my environment.

Can you check if you can perform basic queries on MSDB databases ?

-:-)

Are reorganizing indexes or rebuilding them ?

Also can you post some part of script to make things clearer.

-Puzzled 🙂

Please test the script in UAT environement given in the link

http://support.microsoft.com/kb/889696/en-us

-:-)

While you are logging it tonight , here something to chew on if you have not already read it.

http://blogs.solidq.com/EN/rdyess/Lists/Posts/Post.aspx?ID=13

Microsoft article infact does not want users to change the...

Window functions in SQL Server 2005 have nothing to do with Microsoft Windows; rather, they create data windows. Window functions enable you to look at different levels of aggregation all...

Does CPU consumed on PROD when the tasks is executed using perfmon significantly greater then DEV envrionment and if both CPU are from same vendor probably check with hardware...

Is there any way I can use say 6 or 7 of these machines to run one version of SQL Server instead of buying another new server?

If I understood your...

Your approach of updating in batches is right method and following it up with Shrink means you have limited disk space.

Is when you do date range does the rows split...

Please check size in terms of data present and available free space on the distribution database.

In SMS you can do it by right clicking on database --> Properties ,...

This behaviour is observed if the recovery mode of your database is SIMPLE instead of FULL. Try altering the database recovery mode to FULL and try the backup wizard.

-Sat