Forgive me, I was a beginner when I first wrote it.

It's a cleanup function. Use it just before running EXEC().

-- Concatenate your sql statement

SET @sql = <<snip>>

-- Print for troubleshooting

PRINT @sql

-- Remove non-printing characters

SET

I have found that carriage return line feeds work okay in the editor, but there is a problem during execution. So, I use a cleanup function before running the EXEC()....

Open the MSSQLSERVER service on your desktop and change the login to "This account", then enter your domain login.

You can also create an instance of SQL Server on your desktop, run distributed transactions to the production server to gather job failure information, then shoot out emails from your desktop.

Why not create a job history table in your user database and populate it off of a trigger on the system table?

I just had this. Your sysindexes table may be out of sync. Running "DBCC UPDATEUSAGE (0)" cleaned things up for us.

The DTC may need to be reconfigured. We just migrated to Windows 2003 when this problem cropped up.

Microsoft has a fix:

http://support.microsoft.com/kb/839279

Ray: The poll setting is just fine. It still works with other sql instantiations living on other windows servers in the network, just not the new one; so it's not that.

David:...

Why make life hard for yourself? Don't script the jobs and packages, just backup and restore msdb along with your user databases.

I got around this by instantiating SQL Server on my desktop (which does have Outlook) then linking servers. Then you have to root around in the jobs tables to get...