How can we help you today? How can we help you today?
Jon Kirkwood
Hi huey    Thank you for reaching out on the Redgate forums with your bulk-scripting request. You can absolutely mass-deploy SQL instances into Redgate Monitor without clicking through the UI.   On the Configuration > Example Scripts page of your Monitor installation (https://<your-monitor-server>/Configuration/ExampleScripts ), there’s a full PowerShell example showing how to add: Windows SQL instances Linux SQL instances PostgreSQL Azure SQL / Managed Instance RDS / Aurora Flexible Postgres [image] Once you’ve reviewed the examples, you can add in a loop through your server list; something like this: $servers = @( "ServerA\SQL2019", "ServerB\SQL2017", "ServerC" ) foreach ($name in $servers) { Write-Host "Adding $name..." $instance = New-RedgateMonitorSqlServer ` -FullName $name ` -BaseMonitor $BaseMonitor $instance | Add-RedgateMonitorMonitoredObject } That’s usually the fastest way to bulk-register dozens or hundreds of instances.   If you haven't used the Powershell API before - I would recommend starting here: https://documentation.red-gate.com/monitor14/api-239668740.html to get the necessary info on how to download the Powershell cmdlets from your Monitor instance, generate a token and create your connection to the API to add your instances. / comments Official comment
Hi huey  Thank you for reaching out on the Redgate forums with your bulk-scripting request.You can absolutely mass-deploy SQL instances into Redgate Monitor without clicking through the UI. On the ...
0 votes
Hi Henry Winkler  Thank you for reaching out via the Redgate forum regarding your bulk validation inquiry. If you’re looking to validate a large number of SQL scripts at once, SQL Prompt does include a Bulk Code Analysis feature.   This lets you select a folder of SQL files and run all of SQL Prompt’s code analysis rules over them in one go. This can be run through SSMS or via a CLI process. It’s useful for spotting syntax issues, rule violations, and potential problems across a wide codebase without having to open each file individually. [image] That said, it’s worth noting a couple of limitations for your scenario: Bulk Code Analysis works on SQL files, not directly against database objects in a live database. If your custom objects exist only inside a database, you’d need to script them out first. The analysis is static, so while it can catch many issues, it won’t always identify broken dependencies caused by schema changes (e.g. views/stored procedures referencing dropped or renamed columns). For that, you’d typically supplement with SQL Server’s system views (like sys.sql_expression_dependencies) or test recompiling objects against the upgraded schema.   Bulk operations in SQL Prompt, including Bulk Code Analysis, require either a SQL Toolbelt Essentials or SQL Toolbelt license. You can find more details here: https://documentation.red-gate.com/sp/features-requiring-a-specific-license/bulk-operations/bulk-operations-in-ssms/bulk-code-analysis  / comments Official comment
Hi Henry Winkler Thank you for reaching out via the Redgate forum regarding your bulk validation inquiry.If you’re looking to validate a large number of SQL scripts at once, SQL Prompt does include...
0 votes
Hi Don,  Sorry to hear this is repeating for you. Up until now I was only aware of this being an initial concern when first installing SQL Prompt into SSMS21.  Does it reoccur after patching SQL Prompt, or at different times?   / comments
Hi Don, Sorry to hear this is repeating for you. Up until now I was only aware of this being an initial concern when first installing SQL Prompt into SSMS21. Does it reoccur after patching SQL Prom...
0 votes