microsoft / microsoft/sql-server-samples
SQL Assessment: FnNaming is triggered for msdb functions used by managed backup
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 11.2k
- Forks
- 9.1k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 14
Description
Getting this warning in msdb:
Rename the following functions to eliminate 'fn_ prefix': managed_backup.fn_backup_db_config, managed_backup.fn_backup_instance_config, managed_backup.fn_get_parameter,
managed_backup.fn_available_backups, managed_backup.fn_get_current_xevent_settings, managed_backup.fn_get_health_status, smart_admin.fn_backup_db_config, smart_admin.fn_backup_instance_config,
smart_admin.fn_get_parameter, smart_admin.fn_available_backups, smart_admin.fn_get_current_xevent_settings, smart_admin.fn_get_health_status, dbo.fn_sysutility_ucp_get_policy_violations
These are Microsoft shipped functions used by various features like managed backup and UCP.
Can we avoid flagging them?
@ebruersan
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the SQL Assessment FnNaming rule that reports the listed Microsoft-shipped functions in msdb. Verify how managed_backup, smart_admin, and dbo.fn_sysutility_ucp_get_policy_violations are identified, then confirm that these functions no longer produce the warning while other fn_ names remain checked.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sql
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100