Activity overview
Latest activity by graded
SQL Monitor doesn’t expose the T-SQL behind its built-in alerts. You can view and adjust alert conditions under Configuration > Alert settings. To see or modify the SQL directly, you’d need to recreate the alert as a custom one. The Redgate documentation also outlines the logic for each default alert. / comments
SQL Monitor doesn’t expose the T-SQL behind its built-in alerts. You can view and adjust alert conditions under Configuration > Alert settings. To see or modify the SQL directly, you’d need to recr...
Yeah, working across different databases can be a headache sometimes. The biggest thing I notice is how each one handles syntax and performance tuning differently, so you can’t always carry over the same approach. Migrations especially highlight the gaps, like data types not lining up or certain functions not existing in another system. Definitely interested to see what common issues your survey brings up. / comments
Yeah, working across different databases can be a headache sometimes. The biggest thing I notice is how each one handles syntax and performance tuning differently, so you can’t always carry over th...
Hi Luca, I’m seeing the same issue after updating to version 11.0.1.16766. The logs show an issue IndexOutOfRangeException in the parameter extraction logic, specifically when processing single-line comments. This suggests the auto-complete issue might be related to how the new version handles comments within stored procedure definitions. If your procedures contain inline comments near the parameters, that could be causing the failure. Until there’s a fix, reverting to the previous version might be the most stable workaround. / comments
Hi Luca, I’m seeing the same issue after updating to version 11.0.1.16766. The logs show an issue IndexOutOfRangeException in the parameter extraction logic, specifically when processing single-lin...
Thanks for pointing that out, Cathy. That makes sense. If dynamic SQL is involved, then the normal ownership chaining rules wouldn’t apply, and you’d need explicit permissions on the referenced objects. I’m running into a similar issue on Azure SQL DB where a stored proc works fine on SQL Server but throws a SELECT permission error on Azure. I’ll double-check whether there’s any dynamic SQL in the proc that's causing the break in the chain. Appreciate the insight! / comments
Thanks for pointing that out, Cathy. That makes sense. If dynamic SQL is involved, then the normal ownership chaining rules wouldn’t apply, and you’d need explicit permissions on the referenced obj...
Thanks, Eddie, appreciate the detailed response. The breakdown of Classify → Map → Mask helps wrap our heads around the process. We’ll dig into the CLI options too since automation is a big part of what we’re aiming for. If we run into anything specific during setup, we’ll reach out through support. Thanks again! / comments
Thanks, Eddie, appreciate the detailed response. The breakdown of Classify → Map → Mask helps wrap our heads around the process. We’ll dig into the CLI options too since automation is a big part of...
You might want to check if the profiler has the right permissions to attach to the service process. Since background services often run under different user accounts (like Local System), the profiler may not be able to hook into them properly. Try running the profiler as an administrator and double-check that your service is running in the same session or user context. Also, make sure any antivirus or security software isn't interfering with the attachment process. / comments
You might want to check if the profiler has the right permissions to attach to the service process. Since background services often run under different user accounts (like Local System), the profil...
That error usually points to a mismatch or conflict between what's in your local folder and what source control expects. If the folder already has data, it might not fully align with what Azure DevOps is tracking. You could try disconnecting source control, cleaning or re-cloning the repo, then reattaching to ensure everything’s synced properly. Also worth checking is if any of the objects in the “locked” tab are still marked as checked out or modified. / comments
That error usually points to a mismatch or conflict between what's in your local folder and what source control expects. If the folder already has data, it might not fully align with what Azure Dev...
I’ve run into the same limitation. Since -locations scans everything recursively, the only real workaround I’ve found is either restructuring the folders or being very specific with your location paths using wildcards. Not ideal, but it helps avoid including stuff you don’t want Flyway to process. / comments
I’ve run into the same limitation. Since -locations scans everything recursively, the only real workaround I’ve found is either restructuring the folders or being very specific with your location p...
Mapped drives definitely complicate things. I’ve run into similar issues where add-ins lose track of their paths after a reboot or network hiccup. A proper installer with path control would make setups way less fragile, especially in environments like ours. / comments
Mapped drives definitely complicate things. I’ve run into similar issues where add-ins lose track of their paths after a reboot or network hiccup. A proper installer with path control would make se...
So if we're using the standard 14-day trial, the API access won't be available unless we specifically request the enterprise trial, good to know. / comments
So if we're using the standard 14-day trial, the API access won't be available unless we specifically request the enterprise trial, good to know.