Activity overview
Latest activity by Jon Kirkwood
Hi lilly44 Thank you for reaching out on the Redgate forums regarding your inquiry for script creation & management. I noted you have posted in an Oracle forum so assuming you are using Oracle and possibly a mix of other database types. A good approach is to use a migrations-based workflow; so every database change is captured as a script, versioned, and deployed in a controlled way. Redgate Flyway is designed specifically for this. It allows you to: • Create versioned migration scripts (for example: V1__create_tables.sql , V2__add_indexes.sql ) • Store scripts in source control (Git, Azure DevOps, etc.) alongside your application code • Automatically track which scripts have been applied using a schema history table • Deploy changes consistently across dev, test, and production environments • Integrate into CI/CD pipelines to reduce manual deployment risk A typical workflow example might be similar to this:
Developer creates a new migration script for the required change
Script is committed to source control
Flyway runs during build/release and applies any pending migrations
Flyway records the change so it won’t run again
This ensures changes are traceable, repeatable, and reduces deployment errors. You can learn more about Flyway here: https://www.red-gate.com/products/flyway/ This page includes additional information on features, supported databases (including Oracle), and the option to download a free trial so you can test it within your own environment and workflows. / comments
Official comment
Hi lilly44 Thank you for reaching out on the Redgate forums regarding your inquiry for script creation & management. I noted you have posted in an Oracle forum so assuming you are using Oracle and ...
Hi SeannM Thank you for reaching out on the Redgate forums regarding your DLM Dashboard question. As you've confirmed, DLM is a retired product so suggestions are made at a risk. Unfortunately, DLM Dashboard doesn’t provide any supported way to edit or amend an acknowledged comment once it’s been saved. Those comments are written directly into the Dashboard’s internal data store, which is based on a RavenDB, and there is no UI or API exposed for safely modifying them after the fact. While it is technically possible to change the data by editing the RavenDB database directly, this is not something we recommend. It’s complex, undocumented, and carries a real risk of corrupting the Dashboard’s state or audit history; especially since the product has been retired and is no longer maintained. In practice, the safest options are:
Leave the original comment as-is and add a new comment clarifying or correcting the typo
Or, if this is for audit or compliance purposes, document the correction externally (for example in your ticketing or change-management system)
I know it’s not ideal for small typos, but this approach preserves the integrity of the audit trail and avoids risking the underlying data store. Hope that helps. / comments
Official comment
Hi SeannM Thank you for reaching out on the Redgate forums regarding your DLM Dashboard question. As you've confirmed, DLM is a retired product so suggestions are made at a risk. Unfortunately, DL...
Hi Patrick Ortuso Thank you for reaching out via the Redgate forums regarding your SQL Prompt formatting inquiry. You could potentially do this using the SQL Prompt bulk-formatter formatter, which lets you apply formatting styles to SQL inside or outside of SSMS before it’s executed. This is the supported way to format dynamically generated SQL, as there’s no API or T-SQL function to apply SQL Prompt styles directly in memory. How it could work in your case:
Your process generates the stored procedure SQL
Write it out to a .sql file
Run the SQL Prompt command-line formatter on that file
Alternatively run the bulk-formatter from within SSMS
It rewrites the file using your chosen SQL Prompt style
Execute the formatted SQL to create the procedure
Licensing note: The bulk formatting / command-line operations requires either a SQL Toolbelt Essentials or SQL Toolbelt license. It’s not included with standalone SQL Prompt. Here are some documentation links if you would like to learn more about this: Within SSMS: https://documentation.red-gate.com/sp/features-requiring-a-specific-license/bulk-operations/bulk-operations-in-ssms/bulk-formatting Via Command-Line: https://documentation.red-gate.com/sp/features-requiring-a-specific-license/bulk-operations/bulk-operations-via-the-command-line / comments
Official comment
Hi Patrick Ortuso Thank you for reaching out via the Redgate forums regarding your SQL Prompt formatting inquiry. You could potentially do this using the SQL Prompt bulk-formatter formatter, which ...
Thank you for your patience whilst this has been escalated with our developers. A fix has been included in V16.0.2 for the displaying of leap day values. Can I ask you patch at your earliest convenience and verify this has been resolved for you. Download link: https://download.red-gate.com/checkforupdates/SQLDataCompare/SQLDataCompare_16.0.2.28399.exe [image] / comments
Thank you for your patience whilst this has been escalated with our developers.A fix has been included in V16.0.2 for the displaying of leap day values.Can I ask you patch at your earliest convenie...
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 ...
Hi devtrading Thank you for reaching out via the Redgate forums regarding you SQL Data Compare I have replicated this using the latest version v15.4.28 and can find that the datetimeoffset on a leap year day at midnight does roll over to the next day. I also found that Data Compare changes the source date but not on the target which is certainly an odd behaviour. This will be escalated to our development team to investigate as a potential bug; I will update this forum post with any workaround/fixes as they are made available. [image] / comments
Official comment
Hi devtrading Thank you for reaching out via the Redgate forums regarding you SQL Data Compare I have replicated this using the latest version v15.4.28 and can find that the datetimeoffset on a lea...
Hi emmar00 Thank you for reaching out on the Redgate forum. You’re right in that flyway_schema_history is just a regular table, so anyone with write access can modify it. The simplest protection is to lock down permissions so only the Flyway service account can perform DML on the table and everyone else gets read-only access. This table can be dropped as part of a Flyway process so sometimes expected that this table may be dropped and recreated e.g. flyway clean If you want extra assurance, we'd suggest enabling SQL Audit or Extended Event to log any writes to that table. This should provide some extra tracking if records are changed and you can trace who made the changes. Triggers could work too, but they’re visible and can interfere with Flyway operations, so generally these are recommended to be avoided unless tampering is a known issue. / comments
Official comment
Hi emmar00 Thank you for reaching out on the Redgate forum.You’re right in that flyway_schema_history is just a regular table, so anyone with write access can modify it. The simplest protection is ...
Hi Koray Thank you for reaching out via the Redgate forums and sorry to hear about your problem. Can you please confirm the full version of your ANTS program; this can be found in Help > About ANTS Performance Profiler I am looking for specifically the patch number after 11.4.* Looking at our releases there were two releases in the last couple of weeks and one of them has been pulled - if you are on version V11.4.5 can I request you patch into the latest version V11.4.6 and verify if this slowness is still being found Download link available here: https://download.red-gate.com/checkforupdates/ANTSPerformanceProfiler/ANTSPerformanceProfiler_11.4.6.4353.exe / comments
Official comment
Hi Koray Thank you for reaching out via the Redgate forums and sorry to hear about your problem.Can you please confirm the full version of your ANTS program; this can be found in Help > About ANTS ...
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...
If git works fine from the command line but Flyway Desktop still shows Permission denied (publickey,password), it can mean that the Git client isn’t picking up your SSH setup. A few things you can try:
Force the key at repo level Run this inside your repo folder:
git config --local core.sshCommand "ssh -i C:/Users/<you>/.ssh/id_rsa -o IdentitiesOnly=yes"
Start Flyway Desktop with verbose SSH From the cmdline:
set GIT_TRACE=1
set GIT_SSH_COMMAND=ssh -vvv -i C:\Users\<you>\.ssh\id_rsa -o IdentitiesOnly=yes
Then launch Flyway Desktop from the same CMD and try Fetch. The -vvv verbose level 3 log will show whether your key is being offered.
Use an SSH config alias Create C:\Users\<you>\.ssh\config with:
Host mygit
HostName <ip-or-host>
User <ssh-user>
IdentityFile C:/Users/<you>/.ssh/id_rsa
IdentitiesOnly yes
Then set your remote to that alias:
git remote set-url origin <ssh-user>@mygit:/path/to/repo.git
Check your agent Make sure the key is loaded:
ssh-add -l
ssh -T <ssh-user>@<ip>
Hopefully one of these steps helps you get some traction with your Flyway project pulling from your git server / comments
If git works fine from the command line but Flyway Desktop still shows Permission denied (publickey,password), it can mean that the Git client isn’t picking up your SSH setup. A few things you can ...