Comments
Sort by recent activity
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...
Okay Brian, I will standby then while we wait for the .toml file and to see if this issue continues to replicate now that you have nuked the project and started over. Let me know if you continue having issues on the new project. Best, Christian Perez / comments
Okay Brian,I will standby then while we wait for the .toml file and to see if this issue continues to replicate now that you have nuked the project and started over. Let me know if you continue hav...
Hi Karl, the compatability issues with SSMS 22.3 were not isolated to only SQL Prompt but also impacted SQL Search and I believe Source Control, so when you updated SQL Doc and SQL Search, you likely cleared the compatibility issue for 22.3. Jeff + Will: Apologies, you are totally correct I should have included a new installer bundle link in my response as those have been getting updated very frequently as a result of what I told Karl above with this defect targeting multiple Redgate Products. That being said, I am glad that both of you are up and running now. / comments
Hi Karl, the compatability issues with SSMS 22.3 were not isolated to only SQL Prompt but also impacted SQL Search and I believe Source Control, so when you updated SQL Doc and SQL Search, you lik...
Hi Brian, Thanks for reaching out to Redgate Support, I understand you are having a little trouble with your Flyway Desktop Project, lets see if we cannot get that remediated for you. How are you running the Flyway Diff in this case, is this occurring in the GUI when saving to schema model or are you running a CLI command? If the latter, could I have you share the command syntax you are currently utilizing? Additionally, if this is from the CLI, you can add a -X flag to the command to output in debug/verbose, which may tell you exactly when we are failing to read the schema parameter. It would also likely be helpful to get a copy of your .toml or .conf file depending on what version of Flyway you have so we can see if schemas are properly configured there. Best, Christian Perez Product Support Engineer / comments
Official comment
Hi Brian, Thanks for reaching out to Redgate Support, I understand you are having a little trouble with your Flyway Desktop Project, lets see if we cannot get that remediated for you.How are you ru...