Activity overview
Latest activity by Christian Perez
Hi Davraf, Thanks for reaching out to Redgate Support, apologies for the display issue you appear to be experiencing. I am including a screenshot below of what you should be able to do to fix this behavior: [image] If you click on the 6 dots in the bottom right-hand corner you should be able to re-size the suggestions window. This behavior is generally caused by the resolution of the screen you are working on, so if you can increase the resolution even temporarily, you should get around this behavior. If you cannot increase resolution or re-size the window, you may have to move your Windows taskbar to the left hand side of the screen, re-size the window, then move the taskbar back to the bottom. Should be as easy as drag and drop the toolbar. (might have to unlock it) Can you give the above steps a shot and let me know what the results are? / comments
Official comment
Hi Davraf,Thanks for reaching out to Redgate Support, apologies for the display issue you appear to be experiencing. I am including a screenshot below of what you should be able to do to fix this b...
Hi Dave P, Hope you are doing well today, sorry to hear you are having a little trouble with your Flyway CLI when trying to pass your own SQLFluff through. Could I trouble you for the full CLI syntax you are utilizing? Better yet, if we could get the relevant portion of your GitHub Actions workflow YAML, specifically the steps for setting up Flyway, Python/SQLFluff, and running the flyway check command, that should give us more context as to where to look next. Reviewing what you have provided thus far, setting the environment variable to FLYWAY_ENV_NATIVE_SQLFLUFF=false seems the correct step to take if you are utilizing your own SQL Fluff application. One thing to note on the environment variable, is to ensure that the environment variable is created in an environment that the GitHub Actions pipeline has access too. That being said, I am curious if perhaps we also need to pass in a check.code.sqlfluffEnabled parameter in the CLI syntax to get this to work. Including some documentation below in case its helpful. https://documentation.red-gate.com/flyway/reference/commands/check/check-code https://documentation.red-gate.com/fd/flyway-check-rules-config-setting-306940980.html https://documentation.red-gate.com/fd/flyway-check-sqlfluff-enabled-setting-296816565.html Lastly, if you add a -X to the Flyway check command, you can run the command in debug mode and it may give you better information as to what the exact cause is. Best, Christian Perez Product Support Engineer / comments
Official comment
Hi Dave P,Hope you are doing well today, sorry to hear you are having a little trouble with your Flyway CLI when trying to pass your own SQLFluff through. Could I trouble you for the full CLI synta...
Hello Abhinandan & brian.burge , thanks for your patience, I had to stand up a sample Databricks environment which took a little time. I have now confirmed the behavior and this indeed appears to be a limitation with how the Databricks parser is handling Scripts that have multiple statements delineated by ; symbols. I am escalating this behavior up the developers to be remediated. Thank you for bringing this to our attention. / comments
Hello Abhinandan & brian.burge , thanks for your patience, I had to stand up a sample Databricks environment which took a little time. I have now confirmed the behavior and this indeed appears to b...
Hi Huey, The information you are looking for should be able to be pulled if you utilize the REST API available with Redgate Monitor Enterprise, if you have the proper license of course. If you are a Standard Monitor Subscriber however, I would give Thomas Bishops sample script above a shot and see if it gets you those details, https://documentation.red-gate.com/monitor/rest-api-in-monitor-enterprise-240976357.html / comments
Official comment
Hi Huey,The information you are looking for should be able to be pulled if you utilize the REST API available with Redgate Monitor Enterprise, if you have the proper license of course. If you are a...
Hi Sean, Thanks for reaching out to Redgate Support regarding your SQL Doc inquiry. I did a search through the codebase repository and SQL Doc Documentation, but unfortunately I am not seeing a method to exclude grant/deny/revoke statements from the SQL Script section of documented objects outside of exluding SQL Scripts entirely from the documentation. I would recommend you consider creating an entry on our User Voice Forum here: https://redgate.uservoice.com/forums/936348-sql-toolbelt-essentials Our User Voice Forum allows Redgate End Users to create potential enhancement requests that are then voted on by the community, if other members vote on your topic, it can then be implemented by development in a future release. Let me know if you have any follow up questions. / comments
Official comment
Hi Sean,Thanks for reaching out to Redgate Support regarding your SQL Doc inquiry. I did a search through the codebase repository and SQL Doc Documentation, but unfortunately I am not seeing a meth...
Hi Bogdan, Thanks for performing those tests for us, throughout the time you were monitoring the GDI Objects level, did you see a crash behavior at any point? / comments
Hi Bogdan, Thanks for performing those tests for us, throughout the time you were monitoring the GDI Objects level, did you see a crash behavior at any point?
Hi Luca, Thanks for your patience on this while I finished working with development on the above reported behavior. At this time and after some back and forth with the developers, this behavior is being marked as won't fix as Redgate's Prompt Formatter would be unable to reliably format the .net CLR methods defined after the :: . The reasoning is because the :: prefix can be followed by any method name (basically any text) and cannot be explicitly formatted by the formatter as we cannot set any rules. Essentially it looks like we may not be able to reliably identify the .net CLR custom method defined in order to format it nominally with Prompts formatter. Given that the Global > Casing > Reserved Keywords > "Leave as is" is sufficient to prevent formatting from occurring in these scenarios, development has opted to not add additional complexity behind the scenes. Of course, let me know if you have any follow up concerns. / comments
Hi Luca, Thanks for your patience on this while I finished working with development on the above reported behavior. At this time and after some back and forth with the developers, this behavior is ...
Hi Bogdan, Thanks for letting us know those extra details. Based off that error message, I would tend to agree with you that this could potentially be caused by GDI+ resource exhaustion from the RDP session you are utilizing. There should be a way that we can test this to confirm on your end, if you open a Task Manager window and go to the Details tab you should be able to add a “GDI Objects” column and monitor ssms.exe over time to see if that number is growing prior to a crash. (there is also a GDIProcessHandleQuota registry value that tells you what the max quota is) Give the above a shot and if you see the GDI Objects value climbing throughout the session, consider restarting SSMS and seeing if that reclaims those handles. Of course let me know if you dont see an increase in GDI Objects and we can try troubleshooting elsewhere. / comments
Hi Bogdan, Thanks for letting us know those extra details. Based off that error message, I would tend to agree with you that this could potentially be caused by GDI+ resource exhaustion from the RD...
Hi Abhinandan, Thanks for reaching out to Redgate Support, sorry to hear you are having some trouble with your databricks migration in Flyway. I think that the parsing error that you are describing is potentially a defect, could I trouble you to attach a copy of the creation script for the stored procedure Flyway is erroring on upon migration? I should then be able to reproduce this behavior and get this escalated to development. / comments
Official comment
Hi Abhinandan, Thanks for reaching out to Redgate Support, sorry to hear you are having some trouble with your databricks migration in Flyway. I think that the parsing error that you are describing...
Hello Bogdan, Thanks for the write up, sorry you are having a little trouble with your SQL Prompt installation. I want to get a better understanding of what is occurring in your environment whenever this error is reproducing for you. You mentioned that you are just editing a sql script when the above behavior occurs and you get an entry in the Windows Event Viewer, is SSMS fully crashing in this case? If you click on SQL Prompt > Help > Locate Log Files and attach those files here, I can review a bit further as to what may be going on behind the scenes. Additionally, is this behavior/crash happening when you are working on particular script or does it reproduce regardless of what you are working on? Have you tested in other versions of SSMS besides version 19.3.4 Thanks for the clarification, lets see if we cant get this resolved for you. / comments
Official comment
Hello Bogdan, Thanks for the write up, sorry you are having a little trouble with your SQL Prompt installation. I want to get a better understanding of what is occurring in your environment wheneve...