Skip to content

Latest commit

 

History

History

Preventing SQL Server Performance Problems Before They Hit Production

SentryOne Deployment Pipeline Demo

  • Open the DeploymentSchedule.sql in SSMS and change the USE statement to point to the correct database.
  • Execute the DeploymentSchedule.sql script.
  • Monitor the SQL Server instance with SentryOne.
  • In SentryOne open Advisory Conditions list from Navigator.
  • Right click any current Condition and click Import, Select each SabinIO Condition to import.
    • If a Different database than WideWorldImporters is used, right click the SabinIO Deployment Advisory Condition in SentryOne and select Edit. Change the Database Name from WideWorldImporters to the desired database name.
  • Test SabinIO Deployment Advisory Condition by inserting a record into the DeploymentSchedule table using the sp_DeploymentSchedule_i stored procedure, then execute the sp_DeploymentSchedule_u with the same ReleaseName to enter and end time for the release.
    • EXEC sp_DeploymentSchedule_i @ReleaseDefinitionName = 'TestDefinition', @ReleaseName = 'TestRelease', @ReleaseDescription = 'Code Change', @ReleaseEnv = 'PreProd'
    • EXEC sp_DeploymentSchedule_u @ReleaseName = 'TestRelease'
  • Check the SentryOne Performance Advisor dashboard for any Alerts.