http://blogs.msdn.com/jenss/archive/tags/SQL+Server+Agent/default.aspxTags: SQL Server Agenten-USCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/jenss/archive/2009/01/27/script-out-jobs-in-sql-server.aspxTue, 27 Jan 2009 23:45:00 GMT91d46819-8472-40ad-a661-2c78acb4018c:9377236Jens K. Suessmeyer3http://blogs.msdn.com/jenss/comments/9377236.aspxhttp://blogs.msdn.com/jenss/commentrss.aspx?PostID=9377236Do you want to script out the jobs available in SQL Server Agent ? There a many ways to skin the cat. The probably easiest one is to us the built in functionality of SSMS. Simply select all the jobs (doing a STRG+A on the Object Explorer list) and choose...(<a href="http://blogs.msdn.com/jenss/archive/2009/01/27/script-out-jobs-in-sql-server.aspx">read more</a>)<img src="http://blogs.msdn.com/aggbug.aspx?PostID=9377236" width="1" height="1">SQL Server 2008SQL Server 2005SQL Server 2000SMOSQL Server Agenthttp://blogs.msdn.com/jenss/archive/2009/01/08/determine-the-current-status-of-a-sql-server-agent-job.aspxFri, 09 Jan 2009 00:36:00 GMT91d46819-8472-40ad-a661-2c78acb4018c:9300607Jens K. Suessmeyer1http://blogs.msdn.com/jenss/comments/9300607.aspxhttp://blogs.msdn.com/jenss/commentrss.aspx?PostID=9300607Due to the problem that there is no definite table for getting information about the current status of jobs, I created a small procedure grabbing the information from parts of the internal procedures used to extract the very relevant information. As an...(<a href="http://blogs.msdn.com/jenss/archive/2009/01/08/determine-the-current-status-of-a-sql-server-agent-job.aspx">read more</a>)<img src="http://blogs.msdn.com/aggbug.aspx?PostID=9300607" width="1" height="1">SQL Server 2008SQL Server 2005SQL Server 2000T-SQLSQL Server Agent