Single-Server Configurations
For development systems and for small to medium applications that do not require the availability that clustering provides, you can run Microsoft SQL Server Notification Services and the Database Engine on a single server. If you are not placing the subscription management applications on the Internet, you can also install the subscription management applications on this server.
A Single-Server System
The following diagram shows a single-server configuration.
.gif "Single-server configuration")
Single-server installations are relatively simple to configure; however, we do not recommend running Notification Services, the databases, and subscription management applications on a single server for critical systems or for systems that are expected to support high volumes of notifications.
The recommended number of CPUs and amount of disk space depend on the processing and storage requirements of the system. A development system might have only one CPU and enough disk space for testing; a production server should have from two to four CPUs and enough disk space to store event, notification, subscription, and subscriber data until the data removal process (vacuumer) removes the data. Additionally, on production servers, it is best to place the database files, log files, and the tempdb database on separate physical disks.
Important
The data removal process (vacuumer) removes obsolete event and notification data from an application database. To save disk space and to maintain performance, it is important to provide a data removal schedule when you define each application. For more information, see Configuring Data Removal.
It is important to monitor the CPU usage, memory usage, and disk usage of the production servers to watch for bottlenecks or contention problems. If the single server cannot support the processing requirements, consider using a remote database server configuration. For more information, see Remote Database Server Configuration.
See Also
Tasks
Walkthrough: Single-Server Deployment
Concepts
Hardware Configurations
Notification Services Considerations
Database Considerations
Database Resource Planning