Technical Article

Report table and column-level extended properties

SQL Server 2000's extended properties provide an easy way to store your data dictionary documentation within the database itself. This stored proc provides an easy way to extract all the table and column-level descriptions from those system tables for reporting purposes. This procedure can easily be modified to provide additional information to suite your needs. […]

You rated this post out of 5. Change rating

2002-04-22

237 reads

Blogs

A Basic Update Trigger: #SQLNewBlogger

By

I had someone ask me about using triggers to detect changes in their tables....

Apply for a 2025 PASS Summit Scholarship

By

Redgate is offering 13 PASS Summit scholarships which not only includes the 3-day ticket...

SQL Server TempDB: The Most Overlooked Bottleneck

By

Configuration, Performance, and Unnecessary Usage TempDB is the SQL Server equivalent of a junk...

Read the latest Blogs

Forums

Best/easiest way to import an SSIS package...

By jellybean

Folks, Looking for advice on the best way to import a package. I hope...

Measure duplicating its value when non-conformed dimension attribute is included

By stiej1977

Hi,   I have two fact tables (say FactA, and FactB), that are joined/shared...

balancing numa nodes

By PearlJammer1

Can anybody advise on how i go about balancing threads to each node. As...

Visit the forum

Question of the Day

How Many Nested Triggers?

I have DDL trigger code that I'm working on in SQL Server 2022, but I am concerned that we might end up with multiple triggers firing and the response to the user is delayed. If I want to check how many triggers have fired, or are nested, how can I do this in my code?

See possible answers