Remote Database Server Configuration
A common configuration for medium to large Microsoft SQL Server Notification Services applications uses one server to run the event provider, the generator, and the distributor, and another server to host the Notification Services instance database and application databases. The following illustration shows an example of a remote database server configuration.
A System with a Remote Database Server
The following diagram shows a Notification Services system that has Notification Services on one server and databases on another server.
.gif "Remote-server configuration")
The number of CPUs and the required amount of disk space depend on the volume of events, subscriptions, and notifications. Each Notification Services server and the database server should have from two to four CPUs. The database server should have enough disk space to store event, notification, subscription, and subscriber data until the data removal process removes the data. Additionally, place the database files, log files, and the tempdb database on separate physical disks.
See Also
Tasks
Walkthrough: Remote Database Server Deployment
Concepts
Hardware Configurations
Notification Services Considerations
Database Considerations
Database Resource Planning