> For the complete documentation index, see [llms.txt](https://docs.ovaledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ovaledge.com/release7.2/hotfix-releases/release7.2.4.x/release7.2.4.10.md). # Release7.2.4.10 This release introduces key enhancements across Connectors and Data Access Management, improving crawl stability, profiling performance, and the accuracy of permission synchronization. **Key Highlights** * **Connectors (Azure Synapse RDAM)**: Fixed an SQL error that caused Remote Access schema crawl jobs to fail during permission synchronization. The corrected query now allows RDAM object permissions to sync successfully. * **Connectors (Azure MySQL)**: Optimized profiling performance to resolve long-running jobs that previously extended beyond five days. Profiling now completes within expected timeframes and is more stable. * **Data Access Management (Synapse DAM)**: Fixed a permission synchronization issue where DB\_ROLE-inherited permissions were not reflected for existing external accounts. The sync process now includes inherited DB\_ROLE permissions, ensuring accurate access visibility in Security.
**Release Details:**
Release TypeRelease VersionBuild <Release. Build Number. Release Stamp>Build Date
Hotfix ReleaseRelease7.2.4.10Release7.2.4.10.72410736b30a18th Feb 2026
## Connectors ### Fixed **Fixed SQL Error in RDAM Remote Access Crawl** In Azure Synapse RDAM, an issue where the “Crawling Remote Access of Schema” job failed for certain schemas has been resolved. The job encountered an SQL error while syncing remote object permissions. The logs showed an “Unknown column ‘rdam\_db\_role.id’ in ‘on clause’” error during permission synchronization. As a result, the crawl process did not complete successfully for affected schemas. The SQL query used for syncing RDAM object permissions has been corrected. The schema access crawl job now runs successfully and processes permissions without errors. **Optimized Profiling Performance for Azure MySQL Schemas** In Azure MySQL Connector, an issue in which profiling jobs continued to run for more than five days without completing has been resolved. Two profiling jobs for Azure MySQL schemas in the UAT environment ran for an extended period. The jobs intermittently became inactive and then resumed automatically. Even small tables, such as one with 73 columns and approximately 3,500 rows, took over 10 hours to process. This issue resulted in significant delays and prevented log downloads while the job was active. The profiling process has been optimized to improve performance and stability. Profiling jobs will now complete within an expected timeframe. ## Data Access Management ### Fixed **Fixed DB\_ROLE Permission Synchronization Issue** In Synapse DAM, an issue where permissions inherited through a DB\_ROLE were not synchronized to Security when the external account already existed has been resolved. During permission sync, only permissions granted directly to the external account were reflected. Permissions granted to a DB\_ROLE and then assigned to that account were not synchronized. As a result, inherited access did not appear in Security. The permission sync process has been updated to include permissions inherited through DB\_ROLE assignments. All applicable permissions are now correctly reflected in Security. *** Copyright © 2026, OvalEdge LLC, Peachtree Corners, GA, USA. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.ovaledge.com/release7.2/hotfix-releases/release7.2.4.x/release7.2.4.10.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.