Author: Peter Whyte

  • DBA Scripts: Get Active XE Sessions

    ,

    🔧Part of the DBA-Tools Project, copy/paste SQL Server scripts and health checks.In: Performance & Troubleshooting › Extended Events & Tracing Extended Events sessions have a way of quietly accumulating on a busy instance. Someone stood up a trace for a specific investigation six months ago, and it’s still running, still writing files, and nobody remembers…

  • DBA Scripts: Create SP Execution Session

    ,

    🔧Part of the DBA-Tools Project, copy/paste SQL Server scripts and health checks.In: Performance & Troubleshooting › Extended Events & Tracing Query Store and the plan cache tell you what’s expensive. Neither tells you what’s actually called, by what, how often. Before a migration, you need to know which stored procedures matter in practice, not which…

  • DBA Scripts: Create Decommission Audit Session

    ,

    🔧Part of the DBA-Tools Project, copy/paste SQL Server scripts and health checks.In: Performance & Troubleshooting › Extended Events & Tracing “I think nothing uses this database anymore” is not evidence. It is a guess, and it is the kind of guess that turns into an incident report when the thing you dropped turns out to…

  • DBA Scripts: Create Login Activity Session

    ,

    🔧Part of the DBA-Tools Project, copy/paste SQL Server scripts and health checks.In: Performance & Troubleshooting › Extended Events & Tracing “Who actually connects to this server?” is a question you can’t answer from documentation. Not who’s supposed to connect, who is. Ownership changes, connection strings get copied into three other applications nobody told you about,…

  • DBA Scripts: Get Heaps

    ,

    🔧Part of the DBA-Tools Project, copy/paste SQL Server scripts and health checks.In: Maintenance & Automation › Index Maintenance Heaps in SQL Server Explained A surprising amount of SQL Server performance pain comes from tables that were never given a clustered index. These heaps often start life as quick prototypes, staging tables, or legacy leftovers —…

  • DBA Scripts: Get SQL Server Database File Details

    ,

    🔧Part of the DBA-Tools Project, copy/paste SQL Server scripts and health checks.In: Storage & Capacity Understanding SQL Server Database File Layout SQL Server database files are one of those areas where small configuration issues can become large operational problems. A database may be running perfectly today, but poor file placement, incorrect growth settings, or uncontrolled…

  • DBA Scripts: Get Sysadmin Members

    ,

    🔧Part of the DBA-Tools Project, copy/paste SQL Server scripts and health checks.In: Security Identify SQL Server Logins With Sysadmin Access The sysadmin fixed server role provides unrestricted access to a SQL Server instance. Members of this role can perform any operation on the server, including creating databases, changing security settings, accessing all data, and modifying…

  • DBA Scripts: Get Database Sizes and Free Space

    ,

    🔧Part of the DBA-Tools Project, copy/paste SQL Server scripts and health checks.In: Storage & Capacity Get SQL Server Database Sizes and Free Space Database size checks are one of the first things I review when assessing a SQL Server environment. The goal is simple: understand where storage is being consumed, identify databases that need attention,…

  • DBA Scripts: Get VLF Counts

    ,

    🔧Part of the DBA-Tools Project, copy/paste SQL Server scripts and health checks.In: Storage & Capacity VLFs – The Hidden Log Performance Problem Virtual Log File (VLF) count is one of those SQL Server health checks that is often overlooked. It rarely generates alerts, doesn’t usually slow down a single query, and most users never know…

  • CREATE FILE Encountered Operating System Error (Error 5123)

    🚨Part of the SQL Server Errors series, the exact messages and what actually causes them. Msg 5123  ·  Level 16  ·  State 1 CREATE FILE encountered operating system error 5(Access is denied.) while attempting to open or create the physical file ‘C:\t5123.mdf’. ⚡The denial is aimed at the SQL Server service account, not at you.…