TechEd '04: DAT322 SQL Server 2005 (code named "Yukon"): SQL Server Management Object (SMO), Next Generation SQL-DMO
Mouthful of a title. About 15 bodies in the room.
- SMO is the replacement for DMO. DMO is depreciated. SMO is managed code.
Most DMO applications should port smoothly.
- SMO will be feature compatible with DMO. Not exactly 1-to-1, but
anything you did with DMO, you should be able to do with SMO.
- SMO will be an MSI if you need to redist it. Must have SQL native client
and framework 2.x
- Design goals
- Fully cover Yukon's features
- Improve scalability and performance
- Simple but rich object model
- Friendly towards scripted use
- What's new
- All server features covered
- Cached object means that changes are committed immediately
- Capture of T-SQL
- Real-Time server ends
- WMI Wrappers
- Why used: its a lowered barrier to entry, integrates with applications,
isolation from metadata and DDL changes.
- Team had a goal of avoiding T-SQL
- Demo of building an application
- Cool little app to integrate tables. Kind of blows me away how
little code that it really takes to make this work out.
- There are a few tricks that will help you tweak out the performance.
The goal remains, however, get just the data you need.
- Interesting demo of doing index management.
- With DMO, the root object is the server, not the application. This leads
to a releasable state.
- SMO fully supports scripting and the SMO Scripter is a stand-alone
object.
- 2-way dependency filtering
- Dependency pruning
- Progress events
- Covered exceptions. They are chained, but they usually thrown as close
as possible to the event that raised them (rather than bubbling up.)
Jumped out of the session early to fetch a Latte. Informative session, I
thought.