Technical Article

Delete constraints - SQL Server 2005

This script will DELETE ALL constraints within the database that you define and in the following order: Foreign Key, Primary Key and then Unique Key.CAUTION:This script does not print out the ALTER TABLE statements, it drop the constraints immediately, therefore backup your database before testing or using this script. I ran the script below and […]

5 (3)

You rated this post out of 5. Change rating

2007-09-19 (first published: )

4,080 reads

Technical Article

Data Dictionary - SQL 2005

I know there are several scripts out there showing you on how to create a data dictionary... I created this script for creating a data dictionary for SQL 2005. It stores the data into a table in the database that you choose. The script only stores the table name, column name, default value of the […]

5 (1)

You rated this post out of 5. Change rating

2006-10-24 (first published: )

3,123 reads

Blogs

The PASS Summit on Tour in the Netherlands

By

The PASS Summit goes on tour this year, with the final date the first...

Azure SQL Managed Instance: Boost Performance with Read-Scale Out

By

The Business Critical tier of Azure SQL Managed Instance offers the read-scale out feature...

Free Cloud Environment Setup: A Beginner’s Guide

By

Cloud computing is essential for modern development, data storage, and scalable applications. Setting up...

Read the latest Blogs

Forums

How a Legacy Logic Choked SQL Server in a 30-Year-Old Factory

By Chandan Shukla

Comments posted to this topic are about the item How a Legacy Logic Choked...

SQL Server Columnstore Index Fragmentation

By Grant Fritchey

Comments posted to this topic are about the item SQL Server Columnstore Index Fragmentation

do i lose "what this object depends on" etc when moving sprocs to etl server

By stan

Hi i was surprised to see the approach my coworkers used to sunset talend...

Visit the forum

Question of the Day

SQL Server Columnstore Index Fragmentation

The columnstore index is absolutely different than the traditional rowstore b-tree index. Because of this, it doesn't suffer from the same kind of fragmentation across pages as the b-tree index. Yet, it does suffer from a type of fragmentation brought about by an excess of deleted rows in a rowgroup and a lack of compression of storage because more things are in the delta store. While b-tree indexes use dm_db_index_physical_stats to show fragmentation, which system tables or DMVs can be used in SQL Server (prior to SQL Server 2025) to determine columnstore fragmentation?

See possible answers