Cleaning Up the Instance and ApplicationWhen you're finished examining the instance and application created in this chapter, you can use the following steps to remove them from your system. These steps clean up the databases, Registry keys, and other settings associated with the instance and application.
Note In all the following instructions, when you are instructed to right-click the instance in the Object Explorer, make sure you right-click the StockBroker instance in the Notification Services folder, not the StockBroker database in the Databases folder.
|
Summary
In the SQL-NS application model, both events and subscriptions are just data. SQL-NS uses SQL joins to match the events and subscriptions, and because SQL Server can usually execute these
Building an application on SQL-NS involves writing an ADF: an XML document that describes the schemas, logic, and component configuration of the application. This chapter described the ADF for a sample application: one that sends stock price updates to subscribers. The information in this chapter should give you a feel for SQL-NS applications and what's involved in building them. Later chapters provide the details and teach you how to build your own applications. |
Chapter 4. Working with SQL-NS InstancesIN THIS CHAPTER
This chapter examines SQL Notification Services instances: the fundamental units of isolation, deployment, and administration in SQL-NS. Every SQL-NS application you build will be part of some instance, so it's important to understand what an instance is and how it operates. This chapter covers the basic concepts behind instances and describes how to create one. Chapter 13, "Deploying a SQL-NS Instance," and Chapter 14, "Administering a SQL-NS Instance," describe instance operations, security, and deployment configuration.
Note Before we begin, a word of warning: This chapter teaches a number of mechanical details and manual steps that might seem laborious. Don't be discouraged by this: Most of what you learn in this chapter you'll only do manually once. After you get through and understand this material, you'll likely automate all these steps and never have to think about them again. But, it's important to go through and understand them once so that you know what's going on behind the scenes. It's important to know what each step is doing and why it's necessary to do it; it's not important, however, that you memorize the exact syntax of each command or the precise sequence of steps. |