by Paul Bertucci
IN THIS CHAPTER
Building an MTS Component
Installing an MTS Component
Running an MTS Application
Using Database Connection Pooling
Microsoft Transaction Server (MTS) is an important foundation of the Microsoft server offerings. MTS is intended to simplify the development and deployment of multitiered applications built using Microsoft Component Object Model (COM) technologies. This is what Enterprise Java Beans (EJB and J2EE) set out to do.
MTS has truly evolved into an architecture, rather than just a transaction server. The name MTS is really a mislabeling of what comes with this feature. As MTS is integrated deeper into COM+ in the future, MTS will probably lose its current name in favor of something more accurate. In fact, MTS has rapidly been folded into the COM+ environment and is becoming the choice of developers for developing scalable, multitiered, production-quality applications with distributed object technologies. And, if you haven't noticed yet, the .NET framework is using the COM+ functionality for much of its capabilities.
One thing that might get a little blurred in this chapter is that SQL Server 2000 is just a companion to MTS (using MS DTC as a cross-server coordinator and SQL Server 2000 as just another resource manager). It is my hope that this will not diminish the essential position of SQL Server 2000 as an important part of the MTS architecture.