Share via

VacuumSchedule Class

  • Article

Define the vacuuming (data removal) schedule for the Notification ServicesApplication.

Espace de noms: Microsoft.SqlServer.Management.Nmo
Assembly: Microsoft.SqlServer.Smo (in microsoft.sqlserver.smo.dll)

Syntaxe

'Déclaration
Public NotInheritable Class VacuumSchedule
    Inherits NamedSmoObject

public sealed class VacuumSchedule : NamedSmoObject

public ref class VacuumSchedule sealed : public NamedSmoObject

public final class VacuumSchedule extends NamedSmoObject

public final class VacuumSchedule extends NamedSmoObject

Notes

Vacuuming removes older event and notification data from the application database. For more information about the vacuuming process, see Configuration de la suppression de données.

The vacuuming process runs daily at the specified times for the specified duration.

Vacuuming schedules cannot overlap. If schedules overlap, Notification Services stops the earlier vacuuming process before the later one starts.

Vacuuming schedules are optional, and an application can have multiple vacuum schedules. If you do not specify at least one vacuum schedule, obsolete data is not removed from the application database.

Inheritance Hierarchy

System.Object
   Microsoft.SqlServer.Management.Smo.SmoObjectBase
     Microsoft.SqlServer.Management.Smo.SqlSmoObject
       Microsoft.SqlServer.Management.Smo.NamedSmoObject
        Microsoft.SqlServer.Management.Nmo.VacuumSchedule

Exemple

The following examples show how to create a schedule for removing obsolete data and then add the schedule to the collection of vacuum schedules for the application:

VacuumSchedule vacuumSchedule1 = new VacuumSchedule(
    myApplication, "1");
vacuumSchedule1.StartTime = new TimeSpan(23, 0, 0);
myApplication.VacuumSchedules.Add(vacuumSchedule1);

Dim vacuumSchedule1 As VacuumSchedule = _
    New VacuumSchedule(myApplication, "1")
vacuumSchedule1.StartTime = New TimeSpan(23, 0, 0)
myApplication.VacuumSchedules.Add(vacuumSchedule1)

Sécurité des threads

Any public static (Shared in Microsoft Visual Basic) members of this type are thread safe. Any instance members are not guaranteed to be thread safe.

Plateformes

Plateformes de développement

Pour obtenir la liste des plateformes prises en charge, consultez Configuration matérielle et logicielle requise pour l'installation de SQL Server 2005.

Plateformes cibles

Pour obtenir la liste des plateformes prises en charge, consultez Configuration matérielle et logicielle requise pour l'installation de SQL Server 2005.

Voir aussi

Référence

VacuumSchedule Members
Microsoft.SqlServer.Management.Nmo Namespace

Autres ressources

Suppression des données d'application obsolètes
VacuumSchedule Element (ADF)