David Wiseman

This issue can occur on Enterprise edition if you have performed an **edition upgrade from Standard edition.** This occurs on SQL 2019 with CU 17. Running the DBCC command manually...

Global.json has been removed #220. Project is still built with 6.0.101 on the github action for wider compatibility.

It looks like the backward compatibility might be broken now? The action is still targeting 6.0.101 - not sure when/how this got broken. It might be useful to investigate. Maybe...

This was first broken in 2.22.9. Most likely it was introduced by [this commit](https://github.com/trimble-oss/dba-dash/commit/a8bf819289da106e41744ea84a1402a499fa2bd5) to bump the setup-dotnet action.

Changing actions/setup-dotnet@v3 to actions/setup-dotnet@v2 fixes the issue. It might be time to move to the new version though and run a check in the upgrade script.

[This](https://github.com/marketplace/actions/mssql-suite) might be useful

Now uses https://github.com/potatoqualitee/mssqlsuite to add SQL Instance to Windows runner. Checks that DBA Dash can be deployed Checks table counts to ensure service is working as expected Checks error log...

#results table should change object_name column to NVARCHAR(257). This combines schema name (nvarchar 128) + period char + object name (nvarchar 128). 128+1+128 = max length 257.

Consider #214 - tooltip issue when replacing charting components.

Cool. That might be something I could add to [this collection](https://github.com/trimble-oss/dba-dash/blob/main/DBADash/SQL/SQLServerExtraProperties.sql). It already pulls a couple of things out of registry keys if it has access to.