How can we help you today? How can we help you today?
Jon Kirkwood

Activity overview

Latest activity by Jon Kirkwood

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
Hi Murali,    Thank you for contacting Redgate support regarding your code coverage concern, I suspect this is related to our SQL Test product and have moved this post into a new location on our forums to better represent that.   SQL Test provides a UI wrapper around the tSQLt framework, it doesn’t change or extend the tSQLt functionality itself.  In other words, SQL Test runs whatever tSQLt syntax you provide, but the underlying behavior (such as how tSQLt.ExpectException or tSQLt.ExpectNoException works) comes from the tSQLt framework, not from SQL Test.   Because of this, issues with exception handling or coverage inside tSQLt tests are usually best addressed by checking the tSQLt documentation or raising the question with the tSQLt community. https://tsqlt.org/join-the-conversation We’re happy to help confirm that SQL Test is running the tests correctly, but troubleshooting tSQLt specific logic is outside the scope of our product support.   That said, some general guidance we’ve seen work for other users: tSQLt.ExpectException only detects errors that escape the procedure — if your CATCH block swallows the error without THROW /RAISERROR , nothing reaches the test framework. For coverage, you may need to either rethrow the error or assert side-effects (like rows in a log table) instead of expecting an exception. You can find more details here: tSQLt Documentation – ExpectException If you’re not sure whether SQL Test itself is working correctly or if this is purely a tSQLt logic issue, we can potentially help you confirm that. / comments Official comment
Hi Murali,  Thank you for contacting Redgate support regarding your code coverage concern, I suspect this is related to our SQL Test product and have moved this post into a new location on our foru...
0 votes