Comments on: Behind the scenes of PowerShell and SQL

By: Vini

Vini — Mon, 12 Jun 2017 12:46:47 +0000

Hi Rob,
I am looking for PowerShell script to script out the objects from PDW. Could you please help me with this.
Thanks,
Vini

By: Rob Farley

Rob Farley — Thu, 03 Sep 2015 00:46:06 +0000

Sireesh – I’ll have to work that out. PowerShell can’t hook into PDW in the same way.

By: Sireesh

Sireesh — Thu, 03 Sep 2015 00:40:29 +0000

How can we script out a pdw/APS table in powershell?

By: tobi

tobi — Tue, 19 Mar 2013 21:01:19 +0000

SMO uses deprected stuff all the time as it seem. For example Table.RebuildAllIndexes used DBCC REINDEX

By: Rob Farley

Rob Farley — Tue, 12 Feb 2013 13:29:55 +0000

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.

By: Phil Factor

Phil Factor — Tue, 12 Feb 2013 13:17:42 +0000

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. Examples? Of course! Here http://www.simple-talk.com/sql/database-administration/powershell-smo-just-writing-things-once/