I'm no TSQL expert, so someone could probably write a much better script than I could, but you want to look into joining these two tables:

[msdb].[dbo].[sysjobhistory]

[msdb].[dbo].[sysjobs]

You could try checking this link:

Link

From the original post, it wasn't clear that you were referring to upgrading a database itself. So in essence, I suppose during the logshipping restore process you are essentially...

I believe you need to combine the 'use '+@dbname with the rest of your @sql variable and execute it all at once with only one exec(@sql) statement.

As it...

Log Shipping copies logs to a different server for DR purposes. It has nothing to do with updating SQL Server binaries.

Since Express does not come with the Agent, you need to use a work around with Task Scheduler, if you want this to be automated.

Please see here:

http://code.msdn.microsoft.com/SQLExamples/Wiki/View.aspx?title=ExpressBackups&referringTitle=Home

Cross Post...

Please see this post instead:

http://www.sqlservercentral.com/Forums/Topic511237-357-1.aspx

If your end-goal is to essentially have a copy of the Prod DB as a TestDB, you should use backup/restore instead of copy or bulk insert.

Did this database already exist on SQL 2005 before you tried attaching it in 2000?

Actually, just as a first question, is this database "Adventure Works", or a "real" database?

A good first step would be to run the 2005 upgrade advisor and review the output report from that.

This made me curious, so I checked it out. I have a feeling this feature might be bugged.

- I checked the flag, hit ok, and closed. Checkbox was...

From reading that link, it sounds like you have it right - they would have to be a sysadmin in order to reset a password via the GUI (article mentions...

To the best of my knowledge, you can not administer SQL 7.0 databases from Management Studio. You can manage SQL 2000, but not 7.0.

My understanding is that Express only comes with 32-bit reporting services.

It looks like some tweaking would need to be done (not sure if this applies here):

http://technet.microsoft.com/en-us/library/ms143293.aspx

You might also look here...

You can't create a group per se, but you could create a role and assign individual sql logins to be members of that role, coming "close" to the desired effect...