Distributed Transaction Processing

A distributed database (data) environment is a connected set of datasources that might or might not need to be accessed together. The Distributed Transaction Processing breadth is illustrated in Figure 32.1.

Figure 32.1. Distributed Transaction Processing breadth.


That distributed access could be read only (as with Distributed Queries) or contain updates (as with Distributed Transactions). You might have data distributed for a variety of reasons, some of which might include the following:

  • Physically partition data within your company (by geographic regions or by business function) for performance and integrity reasons. You can see physically partitioned data sources in Figure 32.2.

    Figure 32.2. Physically partitioned data sources.


  • Disparate data containers on numerous separate computer systems within your company (some datasources in Excel, Access, DB2, Oracle, MS SQL Server, and so on) because of operational necessity. This is shown in Figure 32.3.

    Figure 32.3. Disparate and distributed data sources.


  • Different company datasources due to company merges and acquisitions (parent company datasources versus subsidiary company datasources?these might always remain different). Datasource partitioning is shown in Figure 32.4.

    Figure 32.4. Parent and Subsidiary Company datasource partitioning.


Regardless of the reasons of the distributed data or the types of access required against this data, the Microsoft SQL Server 2000 environment along with the Distributed Transaction Coordinator can readily address most of your needs.

    Part III: SQL Server Administration
    Part IV: Transact-SQL
    Part V: SQL Server Internals and Performance Tuning
    Part VI: Additional SQL Server Features