25.8. Summary
Well, all I can say is "Wow!" Okay, so, in a way, this is nothing all that new — after all, DMO used to do a lot of this stuff (indeed, most everything we've looked at with actual code). SMO has, however, made things simpler. The "Wow!" is about thinking of the possibilities.
Imagine issuing commands asynchronously.
Imagine still being able to monitor the progress of those commands by receiving events as progress continues.
Imagine being able to generate script code to support most anything you might want to do.nitor the progress of those commands by receiving events as progress continues.
Imagine being able to register event handlers on your SQL Server and being notified when custom events occur on the server.
The list goes on an on.
Most of the concepts in this chapter are nothing new. We've already looked at ways to createtables, as well as create, back up, and drop databases. The power, then, is in how discretely you can manage those tasks using SMO. We have the prospect for very robust event and error handling. We can far more easily receive configuration information about objects already in the server in a form that yields separate properties as opposed to trying to parse those values out of system stored procedures.
This chapter truly just scratches the surface of what you can do. If I've piqued your interest at all, I encourage you to consider the use of SMO in your design work, and, of course, go get a book specific to SMO if you need one (you probably will!). ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access