SQL Server 2005: What's New? - SQL Management Objects (SMO)
(Page 4 of 5 )
The SMO model is the management object model for SQL Server 2005. It is based on .NET Framework managed code. It's the primary tool for creating database management applications using the .NET Framework, and is used by every dialog box in the SQL Management Studio.
SMO replaces SQL-DMO but, where possible, implements similar objects for ease of use. SMO has a much larger array of features, however, adding over 150 classes. Microsoft says the big advantages of using SMO are its performance and scalability. It uses a cached object model, meaning you can change multiple object properties before a call to the server is made. This is a nice management feature that will definitely be useful for developers of custom database tools.
New Application Framework - Notifications, Reporting and Mobile Services
I chose to sum these up in one section because the objectives are all similar - to provide enhanced BI and reporting services. The big feature add for notifications and messaging is the SQL Service Broker, built specifically to provide a scalable architecture for building asynchronous message routing. It allows an internal or external process to send and receive streams of reliable, asynchronous messages by using the extensions to normal TSQL data manipulation.
The new reporting services are based on the recently acquired ActiveViews technology to provide developers with a complete set of tools for creating, managing, and viewing reports. They also provide an engine for hosting and processing reports and an open interface based architecture for embedding reports.
The new mobile services allow use of objects similar to the core ADO.NET objects for CE environments, as well as use of DTS and parameterized queries. All together, these make a nice foundation for building business applications - but once again, they don't necessarily belong in the database.
Next: CLR Integration >>
More MS SQL Server Articles
More By David Fells
/ 33 
