Clear all user objects
This procedure will drop (with care) all user-defined objects: constraints, procedures, functions, triggers, views and tables. Used for re-creating database schema without drop and create database.
2003-04-07
121 reads
This procedure will drop (with care) all user-defined objects: constraints, procedures, functions, triggers, views and tables. Used for re-creating database schema without drop and create database.
2003-04-07
121 reads
This is a sp_password enhanced by Dmitri Bobkov (see http://www.sqlservercentral.com/scripts/contributions/718.asp) and re-enhanced with a small changes from SQL2kSP3.For SQL Server in Mixed Authentication mode this stored procedure helps to validate users password. Currently this procedure checks for the next requrements: password must have length at least 8 characters plus among them at least one digit […]
2003-03-27
456 reads
I recently had to copy an Azure SQL database (SQL db) from one subscription...
Ivan Jelić, Group CEO at Joyful Craftsmen, reflects on what separates AI success from...
By Chris Yates
AI is no longer a niche capability – it is a leadership catalyst. As...
Comments posted to this topic are about the item How a Legacy Logic Choked...
Comments posted to this topic are about the item SQL Server Columnstore Index Fragmentation
Hi i was surprised to see the approach my coworkers used to sunset talend...
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