Activity overview
Latest activity by TonyD
Yes, true. This is more designed as a way to help you catch the changes you didn't know were coming. Setting up the Agent alert and job step is a little tricky, but it's (hopefully) plain sailing after that. / comments
Yes, true. This is more designed as a way to help you catch the changes you didn't know were coming. Setting up the Agent alert and job step is a little tricky, but it's (hopefully) plain sailing a...
Hi @lmacdonald. We just published an article on our Product learning website that may well suit your requirements. The idea, in brief, is that you include a simple RAISERROR() statement in the SQL batch that makes the change. A SQL Agent alerts detects it, and runs a job that uses the new API to send a message to SQL Monitor and annotate the Overview graph for the server affected by the change. Here's the link to the article: https://www.red-gate.com/hub/product-learning/sql-monitor/tagging-sql-server-changes-in-sql-monitor. Yes, I confess, I 'borrowed' your forum post title and used it for the article! It would be great to know if this works for you, or what you'd need instead. Best, Tony. / comments
Hi @lmacdonald. We just published an article on our Product learning website that may well suit your requirements. The idea, in brief, is that you include a simple RAISERROR() statement in the SQL ...
@Nick_Foster - if you need a scripted solution, we just published a 'how-to' article on Product Learning that might help. It uses SQL Change Automation pre-deployment scripts to create 'stubs' of any cross-database references where the objects don't yet exist. It doesn't require any changes to the source scripts themselves. See: Database Build Blockers: Mutually Dependent Databases / comments
@Nick_Foster - if you need a scripted solution, we just published a 'how-to' article on Product Learning that might help. It uses SQL Change Automation pre-deployment scripts to create 'stubs' of a...