Comments
Sort by recent activity
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 ...
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...