How can we help you today? How can we help you today?
Christian Perez

Activity overview

Latest activity by Christian Perez

Hi Adrian,   Thanks for reaching out to Redgate Support, sorry to hear you are having a little trouble with your SQL Clone installation. Given your description, this sounds like a potential file-lock/sharing violation on the VHD.   To clear the current stuck image/clone: 1. Identify the machine that created the image/clone. 2. Open Disk Management on that machine. 3. Find the row for the Database VHD matching the stuck image/clone (it'll be in the image folder, with a sanitized version of the image name, ending in .vhd). 4. Right-click it and select Detach VHD. 5. Retry the delete via the GUI or PowerShell module. - If you can't locate it in Disk Management, restarting the machine that stores or created the image will also release the lock.   When you are deleting the images, are you utilizing Remove-SqlCloneImage -Soft  or what powershell syntax are you utilizing? Remove-SqlCloneImage -Soft should remove the image from SQL Clones internal tracking without touching the file, you can then queue the leftover file for manual deletion. For clones however, there is no soft-delete, so you would have to do the steps above.   Give the above steps a shot and let me know if you still cannot remove the images/clones from your application.       / comments Official comment
Hi Adrian, Thanks for reaching out to Redgate Support, sorry to hear you are having a little trouble with your SQL Clone installation. Given your description, this sounds like a potential file-lock...
0 votes
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...
0 votes