Comments
Sort by recent activity
@Jon_Kirkwood any update on when this can be fixed so that the Coverage tab doesn't throw errors? I have been waiting but haven't seen any updates. Thanks! --Adam / comments
@Jon_Kirkwood any update on when this can be fixed so that the Coverage tab doesn't throw errors? I have been waiting but haven't seen any updates.Thanks!--Adam
@Jon_Kirkwood Thanks for the response. That being said, SQL Cover is not part of tSQLt, it is a library that is solely used by the application itself, so this doesn't seem like it would have anything to do with the maintainers of tSQLt. Also, have you heard anything in regards to fixing the code coverage error I was receiving? I know you said you escalated it, but I haven't heard back. Thanks! --Adam / comments
@Jon_Kirkwood Thanks for the response. That being said, SQL Cover is not part of tSQLt, it is a library that is solely used by the application itself, so this doesn't seem like it would have anyth...
@Jon_Kirkwood has there been any discussion internally regarding the future use of SQL Cover for performing the coverage analysis? If you look at the github repo for SQL Cover (https://github.com/GoEddie/SQLCover) it hasn't been updated since 2019. This seems concerning as there have been enhancements and such to other products that consume the output of SQL Cover that probably should be implemented. Also, there have been a few forks from this repo to address enhancements and bug fixes that were done purely because this doesn't seem to be maintained anymore. Here is one of the forks (https://github.com/sayantandey/SQLServerCoverage) / comments
@Jon_Kirkwood has there been any discussion internally regarding the future use of SQL Cover for performing the coverage analysis? If you look at the github repo for SQL Cover (https://github.com/...
@Jon_Kirkwood I just updated to 4.1.21 and it's still throwing the same error message for coverage in SQL Test. Can you escalate to your team to investigate? Thanks! / comments
@Jon_Kirkwood I just updated to 4.1.21 and it's still throwing the same error message for coverage in SQL Test. Can you escalate to your team to investigate? Thanks!
@Jon_Kirkwood thanks for the response. That answered my question. I think I overlooked it because I thought it was already enabled. As you can see from the screenshot below the radio button looks active but the checkbox isn't checked. Could you have your team correct it so that it appears like the `Add/remove square brackets` when it isn't checked so that the radio buttons are disabled? It's not a huge thing, but would make it look consistent. Thanks again for your help! --Adam [image] / comments
@Jon_Kirkwood thanks for the response. That answered my question. I think I overlooked it because I thought it was already enabled. As you can see from the screenshot below the radio button look...
Who have you been working with at Redgate? / comments
Who have you been working with at Redgate?
@jduval, were you able to get this resolved? / comments
@jduval, were you able to get this resolved?
@rferraton, it looks like they added the ability to filter out those extended properties in SQL Compare 13.6.14.9174, but that version of the compare engine wasn't incorporated until the 7.0.10.8879 build of SQL Source Control. If you upgrade to 7.0.10.8879 or above it should respect those settings. Hope that helps! / comments
@rferraton, it looks like they added the ability to filter out those extended properties in SQL Compare 13.6.14.9174, but that version of the compare engine wasn't incorporated until the 7.0.10.887...
@Ozzie , Can you clarify if you are trying to install it in SSMS or Visual Studio? If you are trying to install it in SSMS 2008, it won't work as that is no longer supported, but you can access it via SSMS 2012/2017 and connect to your 2008 server. Here is a link to the requirements page for SQL Prompt to show you which versions are supported: https://documentation.red-gate.com/sp9/getting-started/requirements / comments
@Ozzie , Can you clarify if you are trying to install it in SSMS or Visual Studio? If you are trying to install it in SSMS 2008, it won't work as that is no longer supported, but you can access it...
@JayVEE, If you are doing this in an automated fashion, like your post suggests (TC/OD) I would then assume you would use DLM Automation plugins to capture the changes and build the deployments that would get promoted to your upstream environments. I believe that is the piece you are missing, if I am understanding your question correctly. If not, please expand on your question. Thanks! / comments
@JayVEE, If you are doing this in an automated fashion, like your post suggests (TC/OD) I would then assume you would use DLM Automation plugins to capture the changes and build the deployments tha...