Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue #1904 Change RAISERROR 'severity' to 16 for those that should throw an error… #1911

Merged
merged 1 commit into from
Jan 4, 2019

Conversation

RonMacNeil
Copy link
Contributor

… and error.

Fixes # 1904.

Changes proposed in this pull request:

  • Changed the severity value from 0 to 16 for RAISERROR call that should throw an error.

How to test this code:

  • Execute this: EXEC sp_BlitzBackups @PushBackupHistoryToListener = 1, @WriteBackupsToListenerName = 'BIG-AG', @WriteBackupsToDatabaseName = 'Backups-AG', @WriteBackupsLastHours = 3000
  • It should terminate with an error that looks like this:
    Pushing backup history to listener Msg 50000, Level 16, State 1, Procedure sp_BlitzBackupsR, Line 1187 [Batch Start Line 0] We need a linked server to write data across. Please set one up for BIG-AG.

Has been tested on (remove any that don't apply):

  • SQL Server 2016

@BrentOzar BrentOzar merged commit d1eadd8 into BrentOzarULTD:dev Jan 4, 2019
@BrentOzar
Copy link
Member

Great work!

@RonMacNeil RonMacNeil deleted the issue_1904 branch May 6, 2021 19:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants