Activity overview
Latest activity by Christian Perez
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...
Hello Will BD4 & Jeff, Sorry to hear you are having continued issues with SQL Prompt, in this case, most of our users have cleared this error, so if you are still crashing after updating to the latest SQL Toolbelt Essential versions, we will need to troubleshoot normally and look at your Logs as well as what Redgate Products you have installed. I suspect that you might have an errant old Redgate Product installed somewhere that maybe was not updated in Toolbelt Essentials, but let me know what you see. If SSMS is crashing, is there a corresponding event viewer entry? / comments
Official comment
Hello Will BD4 & Jeff,Sorry to hear you are having continued issues with SQL Prompt, in this case, most of our users have cleared this error, so if you are still crashing after updating to the late...
Hi Patrick, Thanks for reaching out to Redgate Support with your SQL Search inquiry. Unfortunately SQL Search does not use case sensitivity in its search results. This means that when you search for a term like “VAT”, SQL Search will return any result containing those letters in any casing, regardless of where the letters appear in the word. For example, this can include objects like VAT_Rate, Group_VAT, but also words such as activated, deactivated, and reactivated, because the tool matches the substring “vat” without considering case. Currently the ‘Match whole words only’ option will be the best manner to restrict search results to only direct matches of the substring VAT, however, Redgate has received customer feedback requesting true case‑sensitive searching, and this has been logged as a feature suggestion for potential future improvement. Let me know if you have any remaining questions. Christian Perez Product Support Engineer / comments
Official comment
Hi Patrick,Thanks for reaching out to Redgate Support with your SQL Search inquiry. Unfortunately SQL Search does not use case sensitivity in its search results. This means that when you search for...
Hi Bob, Hope you are doing well today, thanks for reaching out to Redgate Support regarding your question on loading SSMS without any Redgate Extensions being present. To answer your question, there is not a direct way to run two SSMS instances with only opne loading Redgate extension as SSMS loads all installed extensions per user profile at startup. That being said, you might be able to achive this by using a workaround, if you attempt to load SSMS in Safe Mode, that should load SSMS without any add-ons including SQL Prompt. If you open a normal SSMS instance and then for the second instance open a Command Prompt window and run “ssms.exe -safemode” that should open another SSMS instance without any addons as it will be in safe mode. Give the above a shot and let me know if you run into further issues or if that is a functional workaround. / comments
Official comment
Hi Bob,Hope you are doing well today, thanks for reaching out to Redgate Support regarding your question on loading SSMS without any Redgate Extensions being present. To answer your question, there...
Hi David, Redgate Monitor doesn’t currently offer a built‑in feature to export blocking data across the entire estate. However, you may be able to retrieve this information using Redgate Monitors Rest API feature. Try reviewing through this page: https://documentation.red-gate.com/monitor14/rest-api-in-monitor-enterprise-240976357.html https://documentation.red-gate.com/monitor14/alerts-240976373.html Alternatively: You can try to query the Data Repository directly, however, all monitoring and alert data—including blocking alerts—is stored in the Redgate Monitor Data Repository database. You can query the underlying tables to retrieve historical blocking information. However, Redgate does not publish this schema, and it may change between versions, so direct SQL access is considered an advanced and unsupported method. Typically we do not share custom scripts to query the Redgate Monitor dbs unless it is for troubleshooting purposes and at developments discretion. Let me know if the above is unclear. / comments
Official comment
Hi David, Redgate Monitor doesn’t currently offer a built‑in feature to export blocking data across the entire estate. However, you may be able to retrieve this information using Redgate Monitors R...
Good Morning Piotr Żychski , Thanks for reaching out to Redgate Support, sorry to hear you are having a little trouble with your Prompt installation in SSMS 2022. In this case I would like to confirm we did not deselect any Prompt settings when uprading to SSMS 2022 could you check if you have:
SQL Prompt ▸ Options ▸ Inserted code ▸ Objects & statements
Under INSERT statements, enable the option to insert column names (and any desired defaults/data types).
As well as the more basic suggestion option: SQL Prompt ▸ Options ▸ Behavior ▸ Enable code suggestions is checked. Lets try the above and see if that fixes your behavior. Best, Christian Perez Product Support Engineer / comments
Official comment
Good Morning Piotr Żychski ,Thanks for reaching out to Redgate Support, sorry to hear you are having a little trouble with your Prompt installation in SSMS 2022. In this case I would like to confir...