Little Love Lost for SMO

Question

Little Love Lost for SMO

Phil Factor

SSC-Insane

Points: 20244
More actions
November 26, 2011 at 12:51 am

#146147

Comments posted to this topic are about the item Little Love Lost for SMO
Best wishes,
Phil Factor

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply

TomThomson SSC Guru Points: 104773 More actions · Answer 1

An excellent little item.

This is one of those areas where MS documentation is almost completely useless. It also appears to be an area where the interfaces is a convoluted mess. I imagine these two factors together discourage most people from using it. I wish I believed there was some chance of Microsoft's providing decent documentation for it and/or (preferably 'and') cleaning up the interface. DMO I could live with - SMO I can't, and I have no intention of even trying to learn to use this appalling mess.

Tom

jasona.work SSC Guru Points: 50117 More actions · Answer 2

I've thus far not used either (hey, I still a noob...) But I have run into the exact situation as far as finding answers to problems goes...

I think this is completely appropriate, and accurate: XKCD 979[/url]

Jason

Jeff Moden SSC Guru Points: 1004356 More actions · Answer 3

BWAA-HAAA!!! I love it. Powershell... deprecation warning. Yeah... let me run out an learn how to use that!:-P

The more things change, the more they stay the same. What stays the same? The level of effort necessary to use the next version of SQL Server. :hehe:

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

Peter Schott SSCrazy Eights Points: 9675 More actions · Answer 4

SQLPS really should be deprecated. It's a really limited version of Powershell designed to just run the SQL modules. Making that into a module to use with Powershell makes a lot more sense. Add this new module to Powershell and you'll have the full functionality of Powershell along with the SQL functionality. I remember being somewhat frustrated trying to use the full functionality of Powershell w/ SQLPS and searching for the instructions to just add that to the native Powershell within my profile. I did that and have been pretty content since. There's a learning curve, but it can be really useful for automating some DBA tasks, doing audits, and even to semi-easily mix database calls with DLL calls in one interface. (If I can do it, it must be somewhat easy 🙂 )

I will admit that the SMO docs and examples have been shaky, but I have found a little more help with Powershell calling SMO. While it doesn't necessarily make it easier to use, the examples have been a bit more stable and have been written by people who needed a solution so generally work.

And Jeff, MS is trying to give us job security again. Remember when SQL Server was so easy it didn't need a DBA? 😉

Phil Factor SSC-Insane Points: 20244 More actions · Answer 5

I hope that everyone has seen Michael Wories blog post 'SQL Server Powershell is here!' http://blogs.msdn.com/b/mwories/archive/2008/06/14/sql2008_5f00_powershell.aspx which tells you how to have the SQLPS functionality in ordinary PowerShell. Actually, with SQLPSX, the need for all this has rather gone away! However, this blog tells you far more than is in the hopeless MSDN documentation about the good design intentions for SQLPS

Best wishes,
Phil Factor

Jeff Moden SSC Guru Points: 1004356 More actions · Answer 6

Peter Schott (11/28/2011)
And Jeff, MS is trying to give us job security again. Remember when SQL Server was so easy it didn't need a DBA? 😉

Heh... yup. Now you need an expert in BI, an expert in T-SQL, and expert in data warehousing, a multi-lingual script expert, a Ninja DBA, a separate OPs department to run Windows, a couple of SAN experts, and someone who can write CLRs that work better than cursors. :-):-D

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)