Summary


After the application development phase is complete, a SQL-NS instance needs to be deployed on production hardware before it can be rolled out to users. This chapter covers the various aspects of the deployment process and describes the configuration options that SQL-NS supports. The choices you make when deploying a SQL-NS instance have a significant impact on its performance, reliability, and security.

SQL-NS supports several different machine configurations. In the simplest setup, all components of a SQL-NS instance, including the database, run on a single machine. For better performance and administrative flexibility, you can also separate the database from the SQL-NS engine by running them on different machines.

To provide increased processing power for running the application's core matching logic, you can scale up the SQL Server machine with additional processors, memory, and high-performance disk systems. You can also separate the components in the SQL-NS engine, as well as the SMI and standalone event providers, onto different machines. This allows you to provide them with dedicated hardware that can be tuned to the characteristics of their particular operations. To scale out the formatting and delivery work in the SQL-NS pipeline, an application can have multiple distributors, each running on a dedicated machine.

The database system is obviously a key part of any SQL-NS deployment. SQL Server allows you to control the way databases are mapped to physical files and to distribute those files optimally on the database machine's disks. For best performance, the data files, log files, and tempdb should be located on separate physical disks. The files should be created with sufficient capacity for the expected data volumes in the applications so that SQL Server does not have to perform costly file expansion operations often. This chapter describes the ADF elements used to specify the mapping of the SQL-NS database objects to physical files. In addition to physical storage, you can also specify a recovery model for the databases, which controls how much logging information is written for each transaction. This chapter provides a brief overview of the supported recovery models.

Over time, old event and notification data accumulates in SQL-NS application databases. SQL-NS removes old data by using a process called vacuuming. This chapter describes the ADF elements used to control vacuuming and provides guidance on how to choose an appropriate vacuuming schedule for your applications.

Security is critical in a deployed SQL-NS application. You should assume that your SQL-NS applications are potential targets for malicious users trying to gain unauthorized access to your systems. This chapter describes some basic security practices that can reduce the risk of a SQL-NS application being compromised and covers techniques for guarding sensitive data. The practices described here can minimize the potential damage that could result from a security breach. This chapter also describes event, subscription, and notification throttles, the features of SQL-NS that allow you to limit the volumes of data an application processes. Throttles can be an effective failsafe mechanism to alert you when an application's behavior deviates from expected patterns.

The final section of this chapter provides an overview of the deployment process. Deploying a SQL-NS application involves installing SQL-NS components on the required machines, updating the ICF and ADFs to reflect the chosen deployment configuration, deploying custom components, creating the instance and application databases, registering the instance, and granting database and filesystem permissions. Also, the SMI and any standalone event providers need to be deployed. When these deployment steps are complete, you can enable the instance and make it run by starting the SQL-NS engine on the required machines.

Using the information in this chapter, you can get your SQL-NS instance running in the deployment environment. Chapter 14 covers the administration of running instances, including how to monitor and maintain them.




Microsoft SQL Server 2005 Notification Services
Microsoft SQL Server 2005 Notification Services
ISBN: 0672327791
EAN: 2147483647
Year: 2006
Pages: 166
Authors: Shyam Pather

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net