Share via


Commands Collection

Note

  This feature will be removed in the next version of Microsoft SQL Server. Do not use this feature in new development work, and modify applications that currently use this feature as soon as possible.

A Command object encapsulates a user-defined command or sequence of commands that are automatically executed on the Microsoft® SQL Server™ 2000 Analysis Services client when the user accesses the cube or database. Such commands can include calculated members, named sets, library references, and so on.

Each of the following objects contains a Commands collection:

  • clsCube
  • clsMiningModelRole
  • clsCubeRole
  • clsDatabaseRole

Each Commands collection contains command objects of the same class type. The ContainedClassType property of a Commands collection specifies the class type of the contained objects.

Class type Contained class type

clsCube

clsCubeCommand

clsCubeRole

clsCubeCommand

clsDatabaseRole

clsDatabaseCommand

Remarks

The relative position of commands within a Commands collection determines the order in which the commands are executed. This is important because it is possible to write commands that depend on previous commands in the collection. For example, a named set can contain a previously defined calculated member.

As with other Decision Support Objects (DSO) collections, the Add, AddNew, Find, and Remove methods of Commands collections maintain all necessary parent-child relationships among the objects in the object model.

Note

  The Commands collection of objects of ClassType clsDatabase is reserved for future use.

See Also

Reference

Collections (DSO)
Methods, clsCollection
Properties, clsCollection

Help and Information

Getting SQL Server 2005 Assistance