Activity overview
Latest activity by Christian Perez
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...
Hi Chris, Thanks for the update, let me test your code and see if I can reproduce this behavior locally. / comments
Hi Chris, Thanks for the update, let me test your code and see if I can reproduce this behavior locally.
Hi Chris, Hope you are doing well, sorry to hear you are having a little trouble with your SQL Prompt install with respect to aliases. There should be a setting SQL Prompt > Options > Inserted Code > Aliases that should allow you to either stop Prompt from automatically generating alias names, or to let you manually define an alias to use for a particular object. Would the above work for you as a solution or are you frequently running into this issue where the alias is identical? / comments
Official comment
Hi Chris, Hope you are doing well, sorry to hear you are having a little trouble with your SQL Prompt install with respect to aliases. There should be a setting SQL Prompt > Options > Inserted Code...
Hi Seth, Thanks for reaching out to Redgate Support, sorry to hear you are having a little trouble with your SQL Compare install in this case. I suspect what may be happening is that since we are adding a column to the parent (YesDepts) table that has a trigger-maintained history table (YesDepts_History), we may be running into a dependency chain issue. I suspect SQL Compare may be tryting to drop and recreate the trigger because it references the new column, but the history table doesnt have the new columns yet or vice versa, leading to data loss. To start remediating this, I would first try using some of the Project/Comparison Options designed around triggers and see if if we get the wanted behavior. Have you already tried any of the below options to see if we can stop the trigger from being dropped and recreated?
Project Options > Ignore Tab > Consider Ignoring Triggers for initial comparison
Enable “Disable DDL triggeres during deployment”
Enable “Include transactions”This lets you rollback if a deployment fails midway through execution.
Options > Behavior > Use “Ignore trigger order” in case execution order is causing the problem
Options > Dependencies > Set :Include dependencies" to include triggers, history tables, parent tables are all considered together.
Besides the above, other options include manually disabling the trigger at the beginning of the deployment script, making the schema changes, reenabling the trigger at the end. You could also consider using temporal tables instead of trigger-maintained history to eliminate the need for trigger maintenance and SQL Compare handles them naturally. / comments
Official comment
Hi Seth,Thanks for reaching out to Redgate Support, sorry to hear you are having a little trouble with your SQL Compare install in this case. I suspect what may be happening is that since we are ad...
Hi Luca, Hope you are doing well today, thanks for reaching out to Redgate Support. I was able to reproduce this issue in my local environment and as such, I am going to raise a dev ticket to get this remediated in a future version of Prompt. That being said, if you toggle your active style and configure Global > Casing > Reserved Keywords > "Leave as is" that will function as a temporary workaround so Prompt does not change the casing of the ::get portion of the query. Once I know more from development on the casing behavior, I will circle back here and let you know what shakes out. / comments
Official comment
Hi Luca, Hope you are doing well today, thanks for reaching out to Redgate Support. I was able to reproduce this issue in my local environment and as such, I am going to raise a dev ticket to get t...