How can we help?
Wrong default schema name
When creating a new login, the default schema owner of the login can by mistake be set to the actual name of the login, e.g. login DEV\TestUser1 will have the default schema name DEV\TestUser1, which is not recommended. If the DEV\TestUser1 executes the following statement “create table table1 (id int)”, the new table will be created as DEV\TestUser1.table1 instead of e.g. dbo.table1.
To query the Performance Store database for logins with wrong default schema name:
select s.* from dbo.v_database_security s where s.member_name = s.default_schema_name and s.member_name like '%\%' and s.discovered = 1 and s.is_disabled = 0
The alert will be visible on the Latest stats dashboard.
To exclude specific servers from this alert, see how to use the dbo.team_alert_exclude table in Alerting.