Server Backup History Report (Full DB Backups only) 1. lists all databases with no backup history 2. lists last backup for other databases includes Date, User, Size, Duration, Age, Finish Date & Location Includes system databases Excludes TempDB Excludes backup history data where backupmediafamily.device_type = 7 these are typically created by Veritas BackupExec Tested on […]
2006-04-28 (first published: 2006-03-23)
4,587 reads
Useful in dev environments when you need to periodically assign execute permissions on all procs in a db (drop/create scripts may have been run without re-assigning permissions)Accepts DB name, ProcLike for matching 'starts with' pattern against proc names in DB, revoke (optional - defaults to 0/True) specifies wheter to GRANT or REVOKE permissions
2002-11-21
394 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