Comments
Sort by recent activity
I think there was a slight miss here. I know I stated specifically PDF, but you should probably also fix the XML export as it doesn't respect the hidden objects either. It includes everything as well and should only include the hidden ones as well. I am not sure if you want to track this as a separate bug, or open a new one? I would confirm that the PDF export is working as expected now though. Thanks! / comments
I think there was a slight miss here. I know I stated specifically PDF, but you should probably also fix the XML export as it doesn't respect the hidden objects either. It includes everything as ...
@Jon_Kirkwood sorry, I previously said at the beginning of this issue that I was running 20.2.30.0 which is the most current release. What do you want to do now since I am already on the latest SSMS version and it's not working. / comments
@Jon_Kirkwood sorry, I previously said at the beginning of this issue that I was running 20.2.30.0 which is the most current release. What do you want to do now since I am already on the latest SS...
@Jon_Kirkwood I did the uninstall and reinstall and it still has the same error. I can probably patch SSMS if needed. You would just need to provide me with instructions on how to patch it and where to get the patches from. / comments
@Jon_Kirkwood I did the uninstall and reinstall and it still has the same error. I can probably patch SSMS if needed. You would just need to provide me with instructions on how to patch it and wh...
@JoshH I have not, but what I did find out is that it randomly came back. I haven't seen it disappear since, but for whatever reason it is back and working again. / comments
@JoshH I have not, but what I did find out is that it randomly came back. I haven't seen it disappear since, but for whatever reason it is back and working again.
@Dan_J well, I updated to 4.2.0.3722 recently and now I am unable to recreate the issue. I am guessing it was directly or indirectly fixed by whatever changed in the recent release. / comments
@Dan_J well, I updated to 4.2.0.3722 recently and now I am unable to recreate the issue. I am guessing it was directly or indirectly fixed by whatever changed in the recent release.
@Jon_Kirkwood, @Dan_J Can either of you find out when this issue will be resolved? This doesn't seem like it should be a complicated issue to fix to resolve since it has happened in the past and was fixed quickly. Thanks! / comments
@Jon_Kirkwood, @Dan_J Can either of you find out when this issue will be resolved? This doesn't seem like it should be a complicated issue to fix to resolve since it has happened in the past and w...
@Jon_Kirkwood I updated SQL Test to 4.2.0.3722 that was released today, but I am still getting the same Code Coverage error. Any idea when this can be corrected? / comments
@Jon_Kirkwood I updated SQL Test to 4.2.0.3722 that was released today, but I am still getting the same Code Coverage error. Any idea when this can be corrected?
@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 Would you be able to provide some instructions on how you were able to import this into Excel? I tried something similar, but it was not intuitive and I couldn't get anything that was very useful without a lot of effort. So if there's something I was overlooking, I am open to suggestions for a workaround until an Excel output could be possible. Thanks! --Adam / comments
@Jon_Kirkwood Would you be able to provide some instructions on how you were able to import this into Excel? I tried something similar, but it was not intuitive and I couldn't get anything that w...
@Jon_Kirkwood We would use this information when trying to determine the impact of deprecating a field in table, view, stored procedure, etc or implementing breaking changes to a field. Using the previous example, if I was going to remove the Attribute field from Table A, currently all I know is what objects depend on Table A, but I have to do further analysis to see if any of the dependent objects actually use the Attribute field in order to remove it. Same thing goes if I were to change the field definition for the Attribute field. This takes dependency tracking a step deeper to get a better picture into what exact fields do things depend on within an object. Let me know if you have other questions. Thanks! --Adam / comments
@Jon_Kirkwood We would use this information when trying to determine the impact of deprecating a field in table, view, stored procedure, etc or implementing breaking changes to a field. Using the ...