Microsoft KB Archive/914191

= BUG: The vacuuming process stops running when you configure the generator to run on a different computer in SQL Server 2000 Notification Services =

Article ID: 914191

Article Last Modified on 11/21/2006

-

APPLIES TO


 * Microsoft SQL Server Notification Services 2.0

-



BUG #: 406573 (SQLBUDT)



SYMPTOMS
Consider the following scenario:
 * An existing instance of Microsoft SQL Server 2000 Notification Services is running.
 * You configure the generator to run on a different computer.
 * You use the NSControl Update command to update the instance database and the application database.

In this scenario, the vacuuming process stops running.



CAUSE
This problem occurs because the NSControl Update command does not update the SystemName column in the NSVacuumState table when the SystemName column in the NSGenerators table is updated.



WORKAROUND
To work around this problem, follow these steps after you use the NSControl Update command to update the instance database and the application database:  Open SQL Query Analyzer, and connect to the instance of SQL Server 2000.  Run the following code in the query editor. USE  is a placeholder for the name of the application database.

You must run this code for each application database that belongs to the instance of Notification Services. 



STATUS
Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the &quot;Applies to&quot; section.



MORE INFORMATION
In Notification Services, the vacuuming process removes obsolete event and notification data from the application database. If the vacuuming process stops running, the size of the application database keeps increasing.

