April 5, 2019 at 11:59 am
I'm on board with learning both. T-SQL is vital, there's no question. However, automation is vital and you can't, in fact shouldn't, do some things within the OS with T-SQL.[/quote]
Heh... ahhhh... there it is. The ol' "Just because you can do something in T-SQL, doesn't mean you should" adage. I wouldn't have guessed that would come from you, though. Grant 😉
I'll do my normal play on words of that... "Just because you can do something in T-SQL, DOESN'T mean you SHOULDN'T". 😀 I find that the reason a lot of people do things in PoSh is because they simply don't know either T-SQL or the OS well enough.
Heh... in a similar discussion with my boss a while back, my comment above absolutely exasperated him and he finally said, "Dammit Jeff! SQL Server is NOT the center of the bloody universe"! My comment was, "Cool... let's turn it off and find out if that's true". :D:D:D
Yes, I DO agree that PowerShell is a wonderful and powerful tool and I do encourage learning it and using it. But what do a lot of people do? Then end up doing things like calling the actual or equivalent of old DOS/WMIC commands and calling stored procedures and then having to write additional code to use the output of all that, etc, etc, when a rather simple run in T-SQL would have done the job in it's entirety. In other word, many people end up writing PoSh code to solve problems that have already stable solutions in T-SQL and the OS itself.
And, that's my only point. In other words, "Just because you can do something in PowerShell, doesn't mean you should". 😉 To coin another phrase, "When you're trying to pound nails, use a hammer"! :D:D:D
--Jeff Moden
Change is inevitable... Change for the better is not.
Viewing post 16 (of 16 total)
You must be logged in to reply to this topic. Login to reply