Take a basic table create statement
|
1 2 3 4 5 6 |
CREATE TABLE [dbo].[EatSomeBoogers]( [ID] [int] NOT NULL, [BgType] [varchar](20) NOT NULL, [Size] [smallint] NULL, [Viscosity] [tinyint] NULL ) ON [PRIMARY] |
Pretty simple and we can infer a lot of the information about the table, but we mention size, are we measuring in inches, feet, yards?
We can add extended properties that will help to provide that sort of guidance for someone to reference later on.
|
1 2 3 4 5 6 |
EXEC sys.sp_addextendedproperty @name = N'Details', @value = N'Size is measured in mm', @level0type = N'SCHEMA', @level0name = N'dbo', @level1type = N'TABLE', @level1name = N'EatSomeBoogers', @level2type = N'COLUMN', @level2name = N'Size' GO |
We can also add properties at the table level:
|
1 2 3 4 5 |
EXEC sys.sp_addextendedproperty @name = N'Purpose', @value = N'Holds information about all the gold digging’, @level0type = N'SCHEMA', @level0name = N'dbo', @level1type = N'TABLE', @level1name = N'EatSomeBoogers' GO |
And at the database level:
|
1 2 3 |
EXEC [MyDB].sys.sp_addextendedproperty @name = N'Usage', @value = N'Will handle all information as relates to digging' GO |
You can even add extended properties to other objects, like stored procedures:
Continue reading on SirSQL.net.