<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://sqlblog.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Behind the scenes of PowerShell and SQL</title><link>http://sqlblog.com/blogs/rob_farley/archive/2013/02/12/behind-the-scenes-of-powershell-and-sql.aspx</link><description>Every year, PowerShell increases its stranglehold on the Windows Server system and the applications that run upon it – with good reason too. Its consistent mechanisms for interaction between its scripting interface and the underlying systems make it easy</description><dc:language>en</dc:language><generator>CommunityServer 2.1 SP2 (Build: 61129.1)</generator><item><title>re: Behind the scenes of PowerShell and SQL</title><link>http://sqlblog.com/blogs/rob_farley/archive/2013/02/12/behind-the-scenes-of-powershell-and-sql.aspx#47659</link><pubDate>Tue, 12 Feb 2013 10:17:42 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:47659</guid><dc:creator>Phil Factor</dc:creator><description>&lt;p&gt;This is all interesting, but, at the risk of being a bit pedantic, I ought to say that your criticisms of PowerShell should really be aimed at SMO. You'd hit the same problem whatever language you use to drive the SMO .NET library. SMO is doing an object/relational mapping for the SQL Server metadata which is never going to be fast. If you really want performance, you can get the best of both worlds by using SMO for the things it is good for, and use SMO's connection (usually the ExecuteWithResults method but you can do a lot more) to use TSQL to get the more complex information you need. This hybrid approach is dead fast, and as efficient as your TSQL.&lt;/p&gt;
&lt;p&gt;Examples? Of course! Here &lt;a rel="nofollow" target="_new" href="http://www.simple-talk.com/sql/database-administration/powershell-smo-just-writing-things-once/"&gt;http://www.simple-talk.com/sql/database-administration/powershell-smo-just-writing-things-once/&lt;/a&gt; &lt;/p&gt;</description></item><item><title>re: Behind the scenes of PowerShell and SQL</title><link>http://sqlblog.com/blogs/rob_farley/archive/2013/02/12/behind-the-scenes-of-powershell-and-sql.aspx#47660</link><pubDate>Tue, 12 Feb 2013 10:29:55 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:47660</guid><dc:creator>Rob Farley</dc:creator><description>&lt;p&gt;I'm not meaning to criticise PowerShell or SMO - I find them very useful tools. I find PowerShell extremely handy for getting a wide variety of things done - particularly when T-SQL is just plain clunky (although I think PowerShell can be clunky too, such as in that code for creating Defaults). This post is primarily addressing those people who wonder if PowerShell has access to some secret ability behind the scenes, but I hope doesn't come across as being negative.&lt;/p&gt;
</description></item><item><title>re: Behind the scenes of PowerShell and SQL</title><link>http://sqlblog.com/blogs/rob_farley/archive/2013/02/12/behind-the-scenes-of-powershell-and-sql.aspx#48316</link><pubDate>Tue, 19 Mar 2013 18:01:19 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:48316</guid><dc:creator>tobi</dc:creator><description>&lt;p&gt;SMO uses deprected stuff all the time as it seem. For example Table.RebuildAllIndexes used DBCC REINDEX&lt;/p&gt;</description></item></channel></rss>