Background
When you create a new class and offer it to your clients, the
first client to report the new inventory information to the site
server will start a process that creates two tables, two stored
procedures, and three WMI classes. If you may even have a view
of that table created if you're running Web Reports! All information
from other clients will be fed into these tables.
Certainly there has to be a way to clean all of these up...right?
RIGHT? Well, Microsoft provided DELGRP.EXE. This is a tool that
must be copied onto the site server, run from a command prompt,
and you have to enter the class ID for each class you want to
delete, one by one, until they're all gone.
Or are they? Well, DELGRP only drops the tables and removes
references to that table from other tables. The stored procedures,
views, and WMI classes remain. What does that mean? Well, if
you've ever cleaned your site, and then done a query only to
find that there are three classes that still remain for each
of the classes you thought you deleted! And what about those
repetitive classes? You know, the three classes that have the
same name as the three classes above them, but they both have
different data.
In order to clean your entire site, you not only have to use
DELGRP to drop the tables and delete the table references, but
you also have to manually drop the two stored procedures, any
associated views, and then manually delete the three WMI classes
for that table.
These steps must be repeated for EVERY CLASS that you want to