Export (0) Print
Expand All
Expand Minimize

sp_dropextendedproperty

SQL Server 2000

Drops an existing extended property.

Syntax

sp_dropextendedproperty
    [ @name = ] { 'property_name' }
        [ , [ @level0type = ] { 'level0_object_type' }
        , [ @level0name = ] { 'level0_object_name' }
            [ , [ @level1type = ] { 'level1_object_type' }
            , [ @level1name = ] { 'level1_object_name' }
                [ , [ @level2type = ] { 'level2_object_type' }
                , [ @level2name = ] { 'level2_object_name' }
            ]
        ]
    ]

Arguments

[@name =]{'property_name'}

Is the name of the property to be dropped. property_name is sysname and cannot be NULL.

[@level0type =]{'level0_object_type'}

Is the user or user-defined type. level0_object_type is varchar(128), with a default of NULL. Valid inputs are USER, TYPE, and NULL.

[@level0name =]{'level0_object_name'}

Is the name of the level 1 object type specified. level0_object_name is sysname with a default of NULL.

[@level1type =]{'level1_object_type'}

Is the type of level 1 object. level1_object_type is varchar(128) with a default of NULL. Valid inputs are TABLE, VIEW, PROCEDURE, FUNCTION, DEFAULT, RULE, and NULL.

[@level1name =]{'level1_object_name'}

Is the name of the level 1 object type specified. level1_object_name is sysname with a default of NULL.

[@level2type =]{'level2_object_type'}

Is the type of level 2 object. level2_object_type is varchar(128) with a default of NULL. Valid inputs are COLUMN, PARAMETER, INDEX, CONSTRAINT, TRIGGER, and NULL.

[@level2name =]{'level2_object_name'}

Is the name of the level 2 object type specified. level2_object_name is sysname with a default of NULL.

Return Code Values

0 (success) or 1 (failure)

Remarks

Extended properties are not allowed on system objects.

The objects are distinguished according to levels, with level 0 as the highest and level 2 the lowest. When a user adds, updates, or deletes an extended property, that user must specify all higher level objects. For example, if the user adds an extended property to a level 1 object, that user must specify all level 0 information. If the user adds an extended property to a level 2 object, all information on levels 0 and 1 must be supplied.

At each level, object type and object name uniquely identify an object. If one part of the pair is specified, the other part must also be specified.

Given a valid property_name, if all object types and names are null and a current database property exists, that database property is deleted. If an object type and name are specified, then a parent object and type also must be specified. Otherwise, SQL Server raises an error.

Permissions

Members of the db_owner and db_ddladmin fixed database roles may drop extended properties of any object. Users may drop extended properties to objects they own. However, only db_owner may drop properties to user names.

Examples

This example removes the property 'caption' from column 'id' in table 'T1,' owned by the dbo.

CREATE   table T1 (id int , name char (20))
GO
EXEC   sp_addextendedproperty 'caption', 'Employee ID', 'user', dbo, 'table', 'T1', 'column', id
EXEC sp_dropextendedproperty 'caption', 'user', dbo, 'table', 'T1', 'column', id

See Also

fn_listextendedproperty

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft