The Schema Changes History report shows who created, altered or dropped a table. This post reads the same default trace with T-SQL, tests it on a table and a database drop, and explains the limits: file rollover and shared logins. It ends with ways to keep the history longer.
SQL SERVER – CLONEDATABASE: Generate Statistics and Schema Only Copy of the Database
CLONEDATABASE can Generate Statistics and schema-only diagnostic copies without copying table rows. I use that distinction when investigating optimizer behavior.
Putting a Database Under Source Control
Putting a database under source control starts with state or migration scripts, consistent object files, and a reviewable first commit.
A Custom db_executor Role for Stored Procedure Access
The app gets a permission error while it works for you as a sysadmin. Here is how a db_executor role fixes it without opening everything.
Stale Views: Why SELECT * Breaks After ALTER TABLE
Reproduce stale views after SELECT star and ALTER TABLE, find candidate definitions, refresh with sp_refreshview, and prevent the pattern.
The SQL Server Permission Hierarchy
Understand the SQL Server permission hierarchy from server to database, schema, and object, including GRANT, DENY, and role paths.
Comparing Two Schemas With sys.columns and a FULL OUTER JOIN
Use read-only queries for comparing two schemas, finding missing columns, checking type details, and reviewing indexes and modules.