﻿<?xml version='1.0' encoding='UTF-8'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>SQLServerCentral / Article Discussions / Article Discussions by Author / Discuss content posted by Richard Waymire  / Stairway to SQL Server Agent - Level 8: Using External programs with SQL Server Agent / Latest Posts</title><generator>InstantForum.NET v2.9.0</generator><description>SQLServerCentral</description><link>http://www.sqlservercentral.com/Forums/</link><webMaster>notifications@sqlservercentral.com</webMaster><lastBuildDate>Wed, 22 May 2013 05:56:38 GMT</lastBuildDate><ttl>20</ttl><item><title>RE: Stairway to SQL Server Agent - Level 8: Using External programs with SQL Server Agent</title><link>http://www.sqlservercentral.com/Forums/Topic1190969-2905-1.aspx</link><description>Thanks Richar. I'll try it.</description><pubDate>Tue, 03 Jan 2012 10:07:42 GMT</pubDate><dc:creator>mario.granzella</dc:creator></item><item><title>RE: Stairway to SQL Server Agent - Level 8: Using External programs with SQL Server Agent</title><link>http://www.sqlservercentral.com/Forums/Topic1190969-2905-1.aspx</link><description>By default the output in SQL Server Agent goes to the msdb.dbo.sysjobhistory table (that's what you see when you ask to view history from the job).  To get the output somewhere else, there are a number of possibilities, for example you could do this:$server = new-object( 'Microsoft.SqlServer.Management.Smo.Server' ) “(local)”foreach ($database in $server.databases) {$dbName = $database.NameWrite-Output "Database: $dbName" | Out-File c:\temp\temp.txt -append}Which will create and then append results to teh file c:\temp\temp.txt with the list of database names.</description><pubDate>Tue, 03 Jan 2012 10:05:16 GMT</pubDate><dc:creator>Richard Waymire</dc:creator></item><item><title>RE: Stairway to SQL Server Agent - Level 8: Using External programs with SQL Server Agent</title><link>http://www.sqlservercentral.com/Forums/Topic1190969-2905-1.aspx</link><description>Agree and disagree: :-) :("repetitive tasks, or as in the case of CmdExec, any task that leaves the SQL Server environment is much simpler from the PowerShell subsystem.Disagree:Any repetitive SQL Server task can be easily done using t-sql inside SQL Server - that's what you have SQL Server Agent for!Agree:Tasks that leave the SQL Server environment - here PowerShell might be worth exploring.</description><pubDate>Tue, 03 Jan 2012 09:19:30 GMT</pubDate><dc:creator>pkrudysz</dc:creator></item><item><title>RE: Stairway to SQL Server Agent - Level 8: Using External programs with SQL Server Agent</title><link>http://www.sqlservercentral.com/Forums/Topic1190969-2905-1.aspx</link><description>Hi Richard,              I'm new with PowerShell. I'm doing some test and I have a question about the step 2 of this job. Where is the output of the PowerShell script?              Best regards and happy new year!MARIO</description><pubDate>Thu, 29 Dec 2011 07:25:02 GMT</pubDate><dc:creator>mario.granzella</dc:creator></item><item><title>Stairway to SQL Server Agent - Level 8: Using External programs with SQL Server Agent</title><link>http://www.sqlservercentral.com/Forums/Topic1190969-2905-1.aspx</link><description>Comments posted to this topic are about the item [B]&lt;A HREF="/articles/Stairway+Series/72459/"&gt;Stairway to SQL Server Agent - Level 8: Using External programs with SQL Server Agent&lt;/A&gt;[/B]</description><pubDate>Sat, 15 Oct 2011 15:07:11 GMT</pubDate><dc:creator>Richard Waymire</dc:creator></item></channel></rss>