SQL-Server-First-Responder-Kit

SQL-Server-First-Responder-Kit copied to clipboard

Insert statement column order don't appear correct for the URL column

1

The URL column doesn't end up with an URL - which makes me think that the field order and value order has become incorrect

garyhuntddn

**Version of the script** dev branch **What is the current behavior?** Spelling mistakes: paritions vs partitions sequental vs sequential partioned vs partitioned **If the current behavior is a bug, please...

garyhuntddn

Corrected 3 typos paritions vs partitions sequental vs sequential partioned vs partitioned

garyhuntddn

**Version of the script** dev branch **What is the current behavior?** One query uses DB_NAME(), and another uses sys.databases.name and these two results are used for exclusions. It's unlikely that...

garyhuntddn

**Version of the script** dev branch **What is the current behavior?** The numebr of databases reported excludes those identified for exclusion, but does not exclude those which are classified with...

garyhuntddn

**Version of the script** dev branch **What is the current behavior?** minor mistakes in the code - see the insert statements around the max number of databases ``` INSERT #BlitzIndexResults...

garyhuntddn

**Version of the script** dev branch **What is the current behavior?** Query uses ```NAME``` column rather than ```name``` See the fix in #3513 - it's a simple typo that can...

garyhuntddn

This will fail on a case-sensitive database

garyhuntddn

Use of DB_NAME()

1

For consistency with the INSERT query above - DB_NAME should be used in both places

garyhuntddn

NumDatabases includes those already marked as unreachable

1

There is code to identify databases which can't be analysed that results in secondary_role_allow_connections_desc = 'NO', but these aren't excluded from the NumDatabases count

garyhuntddn