Very similar to my mantra (different meaning of course): "Just because you CAN do something in T-SQL, doesn't mean it's a good idea!"

I have to disagree with you on Powershell though.

Because of issues with SCOM, I created a whole suite of powershell scripts for my monitoring and admin needs.

Allowed me to have a single set of scripts that I run from one place, and all I have to do when i set up a new server is add it to my server list tables and set up the login that runs the scripts.

Now I am even monitoring AWS MySQL instances with my scripts.

This is very similar to what i used to do with shell and perl in my previous life as a Sybase DBA.

The one gotcha I have come across with powershell is memory issues, particularly related with how it reads files.