This documentation is archived and is not being maintained.

Hardware Configurations

Hardware configuration depends on three factors: how much processing power your deployment requires, how much delivery throughput you need, and where you are deploying the instance. If you have a small notification application that is completely located behind a firewall, you might decide to run Microsoft SQL Server Notification Services, databases, and subscription management applications on one server. However, most medium to large applications benefit from multi-server configurations. Very large applications can be scaled out across several servers, and applications that require very high availability can use failover clustering.

Because you can deploy Notification Services in several ways, you might find some sample hardware configurations useful to examine. This section illustrates several hardware configurations: single server, remote database server, scaled out, and high availability using clustering.

The topics that this section covers are described in the following table.

Topic Description

Single-Server Configurations

Shows the simplest configuration for a Notification Services system.

Remote Database Server Configuration

Shows a common configuration with Notification Services on one server and the databases on a second server.

Scale-Out Configurations

Shows how to scale out an application for non-hosted event providers, subscription management applications, and to provide more power for processing and distributing notifications.

High-Availability Configurations

Shows how to manage availability for databases and for Notification Services.

Show: