OVERALL CONTROL / 0.6-customer-control
Grades and scoring
Data access
25% of the overall score before applicability adjustment.
Scored answers and evidence
Read interface 10.0/10
Queryable database or replicated schema
Customer-administered SQL Server 2025 database using native SQL, compatible native database backup/restore and separately enabled table CDC; Azure Synapse, Fabric and server-wide migration are excluded.
Authorized database clients query tables and views through native SQL.
SQL Server SELECT and permissions ↗
SELECT permissions · Checked 2026-10-16
Bulk delivery 10.0/10
Customer-initiated native snapshot or full scoped table export
Customer-administered SQL Server 2025 database using native SQL, compatible native database backup/restore and separately enabled table CDC; Azure Synapse, Fabric and server-wide migration are excluded.
Customer-initiated BACKUP creates a native database copy, subject to backup privileges.
SQL Server native BACKUP ↗
Database backup · Checked 2026-10-16
Query expressiveness 10.0/10
SQL or equivalent joins and aggregations against the operational system
Customer-administered SQL Server 2025 database using native SQL, compatible native database backup/restore and separately enabled table CDC; Azure Synapse, Fabric and server-wide migration are excluded.
SELECT supports joins, filters and grouping against the operational database.
SQL Server SELECT and permissions ↗
SELECT syntax · Checked 2026-10-16
Access cost barrier -
-
Customer-administered SQL Server 2025 database using native SQL, compatible native database backup/restore and separately enabled table CDC; Azure Synapse, Fabric and server-wide migration are excluded.
The complete fixed access entitlement and API fees relative to the lowest paid plan are not established by the reviewed technical documentation.
SQL Server native client connection ↗
SQL Server native client connection · Checked 2026-10-16
Third-party accessibility
20% of the overall score before applicability adjustment.
Scored answers and evidence
Third-party eligibility 10.0/10
Customer authorization without discretionary provider approval
Customer-administered SQL Server 2025 database using native SQL, compatible native database backup/restore and separately enabled table CDC; Azure Synapse, Fabric and server-wide migration are excluded.
The customer controls native server and database credentials for custom client applications.
SQL Server native client connection ↗
Connection examples · Checked 2026-10-16
Downstream permission -
-
Customer-administered SQL Server 2025 database using native SQL, compatible native database backup/restore and separately enabled table CDC; Azure Synapse, Fabric and server-wide migration are excluded.
Applicable downstream processing, redistribution and AI-use conditions remain unestablished for the declared route.
SQL Server native client connection ↗
SQL Server native client connection · Checked 2026-10-16
External action
15% of the overall score before applicability adjustment.
Scored answers and evidence
Write interface 10.0/10
Customer-configurable write interfaces with validation
Customer-administered SQL Server 2025 database using native SQL, compatible native database backup/restore and separately enabled table CDC; Azure Synapse, Fabric and server-wide migration are excluded.
Customer-defined tables and procedures expose DML under database authorization.
Transact-SQL statements ↗
INSERT, UPDATE, DELETE and execution statements · Checked 2026-10-16
Custom application path 10.0/10
Customer-configurable interfaces for custom applications
Customer-administered SQL Server 2025 database using native SQL, compatible native database backup/restore and separately enabled table CDC; Azure Synapse, Fabric and server-wide migration are excluded.
Customers can create stored procedures and grant applications database access.
SQL Server create stored procedures ↗
CREATE PROCEDURE and schema permissions · Checked 2026-10-16
Continuity
15% of the overall score before applicability adjustment.
Scored answers and evidence
Refresh mechanism 10.0/10
Database change-data capture
Customer-administered SQL Server 2025 database using native SQL, compatible native database backup/restore and separately enabled table CDC; Azure Synapse, Fabric and server-wide migration are excluded.
Separately enabled CDC captures DML for selected tables, with edition and administrative prerequisites.
SQL Server change tracking and CDC ↗
Change data capture · Checked 2026-10-16
Limit visibility -
-
Customer-administered SQL Server 2025 database using native SQL, compatible native database backup/restore and separately enabled table CDC; Azure Synapse, Fabric and server-wide migration are excluded.
The reviewed native database route does not establish a universal numeric extraction quota or API retry contract.
SQL Server native client connection ↗
Native connection route · Checked 2026-10-16
CDC and deletion capture 10.0/10
Scoped database/change log captures inserts, updates and deletes with identity requirements disclosed
Customer-administered SQL Server 2025 database using native SQL, compatible native database backup/restore and separately enabled table CDC; Azure Synapse, Fabric and server-wide migration are excluded.
CDC records inserted, updated and deleted table data. Consumer grants and capture configuration govern access.
SQL Server change tracking and CDC ↗
CDC and captured columns · Checked 2026-10-16
Replay and gap recovery 7.5/10
Replay/change queries within a documented retention window
Customer-administered SQL Server 2025 database using native SQL, compatible native database backup/restore and separately enabled table CDC; Azure Synapse, Fabric and server-wide migration are excluded.
Change queries must remain inside retained LSN bounds. Default cleanup retention is three days and can be changed; missing history cannot be replayed from an expired LSN.
SQL Server CDC cleanup and retention ↗
Cleanup job retention and low watermark · Checked 2026-10-16
Data exit
20% of the overall score before applicability adjustment.
Scored answers and evidence
Export custody 10.0/10
Database extract delivered to the customer
Customer-administered SQL Server 2025 database using native SQL, compatible native database backup/restore and separately enabled table CDC; Azure Synapse, Fabric and server-wide migration are excluded.
Native backup files can be held and restored by the customer.
SQL Server native BACKUP ↗
Backup devices and database backup · Checked 2026-10-16
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
Customer-administered SQL Server 2025 database using native SQL, compatible native database backup/restore and separately enabled table CDC; Azure Synapse, Fabric and server-wide migration are excluded.
The reviewed extraction documentation does not establish contractual retrieval rights after cancellation or license termination.
SQL Server native client connection ↗
SQL Server native client connection · Checked 2026-10-16
Planned migration fidelity 10.0/10
Original objects or native schema/data with a documented independent restore/use path
Customer-administered SQL Server 2025 database using native SQL, compatible native database backup/restore and separately enabled table CDC; Azure Synapse, Fabric and server-wide migration are excluded.
Native RESTORE rebuilds the scoped compatible database. Server-level dependencies and incompatible version downgrades are excluded.
SQL Server native RESTORE ↗
Restore database and compatibility · Checked 2026-10-16
Business logic and customization
5% of the overall score before applicability adjustment.
Scored answers and evidence
Logic authoring 7.5/10
Customer-authored native scripts or custom APIs
Customer-administered SQL Server 2025 database using native SQL, compatible native database backup/restore and separately enabled table CDC; Azure Synapse, Fabric and server-wide migration are excluded.
Customers create native stored procedure definitions under schema grants. Ownership and portability rights are separate.
SQL Server create stored procedures ↗
Create stored procedure · Checked 2026-10-16
Rights to custom logic -
-
Customer-administered SQL Server 2025 database using native SQL, compatible native database backup/restore and separately enabled table CDC; Azure Synapse, Fabric and server-wide migration are excluded.
Ownership, reusable export and independent execution rights for native workflow artifacts remain unestablished.
SQL Server native client connection ↗
SQL Server native client connection · Checked 2026-10-16
Scores are out of 10. * Incomplete evidence discounts verified capabilities (unknown answers stay unknown). Planned migration drives data exit. Scoring method ↗
CUSTOMER CHOICE
Third-party accessibility
A database administrator controls the login, database user and object grants. Native clients can use integrated authentication or SQL credentials; CDC configuration requires elevated administrative permissions.
Confirm who can connect, who owns the credentials and which uses are permitted. Customer consent and provider approval can be separate requirements; the selected plan and contract still matter.
READ / INTEGRATE
API and export routes
SQL supports table selection, joins and aggregates against the operational database. A native database backup has a documented compatible restore path, distinct from copying server logins or external jobs.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| Customer database login with separately enabled CDC | database | Customer | No | customer authorization | 2026-10-16 |
Availability depends on your product, plan and agreement. See the documentation below for the requirements of each route.
ECONOMIC ACCESS
Cost, authentication and limits
CDC availability depends on the deployed edition. The complete license, CAL and hosting costs are not established here; a supported edition alone does not prove a universal API surcharge.
Check API entitlement, credential ownership and rate limits for the route you intend to use. Include review fees, customer-plan upgrades and ongoing access charges in the total.
ACT FROM OUTSIDE
External action
SQL permissions govern customer-defined table writes and stored procedure execution. Enabling read extraction does not authorize arbitrary DML or administrative operations.
Validate the supported operation, acting identity and permission scope (read access does not imply write permission). Ambiguous retries and revoked credentials also affect whether an external workflow can run safely.
KEEP ACCESS USEFUL
Continuity
Enabled CDC records inserts, updates and deletes with LSN query bounds. Cleanup defaults to 4,320 minutes, or three days; it is configurable. Validate saved checkpoints against retained minimum LSN before consuming.
CDC, deletions and recovery
| Question | Answer / applicable route | Evidence |
|---|---|---|
| Can ongoing extraction identify updates and deleted records on the declared route? | Scoped database/change log captures inserts, updates and deletes with identity requirements disclosedCustomer-administered SQL Server 2025 database using native SQL, compatible native database backup/restore and separately enabled table CDC; Azure Synapse, Fabric and server-wide migration are excluded. CDC records inserted, updated and deleted table data. Consumer grants and capture configuration govern access. | SQL Server change tracking and CDC ↗CDC and captured columnsChecked 2026-10-16 |
| How can extraction recover after missed events or an interrupted consumer? | Replay/change queries within a documented retention windowCustomer-administered SQL Server 2025 database using native SQL, compatible native database backup/restore and separately enabled table CDC; Azure Synapse, Fabric and server-wide migration are excluded. Change queries must remain inside retained LSN bounds. Default cleanup retention is three days and can be changed; missing history cannot be replayed from an expired LSN. | SQL Server CDC cleanup and retention ↗Cleanup job retention and low watermarkChecked 2026-10-16 |
Useful ongoing access includes corrections and deletions, not only the first export. A failed request, changed filter or lost resource permission should not be interpreted as a deleted record.
LEAVE WITH YOUR DATA
Data exit and portability
A native database backup can restore data and database schema on a compatible SQL Server. Server logins, linked services, jobs and external dependencies need separate migration steps.
Test the output against the destination’s required fields and history. Check stable identifiers, relationships, attachments and extraction time; a sample file proves only the coverage of that sample.
BUILD / INSPECT / REUSE
Business logic and customization
Customers can author stored procedures in their database. The native backup preserves scoped database definitions, while ownership and independent reuse rights are not established by technical restore documentation (server-level dependencies remain separate).
Custom API access, ownership of workflows and the right to export their definitions are separate questions. A custom-app capability alone does not establish that business rules can move to another system.
AGREEMENTS / API DOCS / PROGRAM REQUIREMENTS
Documented conditions
Answers below come from public provider materials. Every answer retains its source check date, scope (a partner agreement does not describe every customer route). Customer contracts and live behavior still need verification.
| Question | Answer / applicable route | Evidence |
|---|---|---|
| What structured read interface is documented? | Queryable database or replicated schemaCustomer-administered SQL Server 2025 database using native SQL, compatible native database backup/restore and separately enabled table CDC; Azure Synapse, Fabric and server-wide migration are excluded. Authorized database clients query tables and views through native SQL. | SQL Server SELECT and permissions ↗SELECT permissionsChecked 2026-10-16 |
| How can customers retrieve data in bulk? | Customer-initiated native snapshot or full scoped table exportCustomer-administered SQL Server 2025 database using native SQL, compatible native database backup/restore and separately enabled table CDC; Azure Synapse, Fabric and server-wide migration are excluded. Customer-initiated BACKUP creates a native database copy, subject to backup privileges. | SQL Server native BACKUP ↗Database backupChecked 2026-10-16 |
| What queries can a customer issue outside the provider UI? | SQL or equivalent joins and aggregations against the operational systemCustomer-administered SQL Server 2025 database using native SQL, compatible native database backup/restore and separately enabled table CDC; Azure Synapse, Fabric and server-wide migration are excluded. SELECT supports joins, filters and grouping against the operational database. | SQL Server SELECT and permissions ↗SELECT syntaxChecked 2026-10-16 |
| Who decides whether a chosen third party may connect? | Customer authorization without discretionary provider approvalCustomer-administered SQL Server 2025 database using native SQL, compatible native database backup/restore and separately enabled table CDC; Azure Synapse, Fabric and server-wide migration are excluded. The customer controls native server and database credentials for custom client applications. | SQL Server native client connection ↗Connection examplesChecked 2026-10-16 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | -Customer-administered SQL Server 2025 database using native SQL, compatible native database backup/restore and separately enabled table CDC; Azure Synapse, Fabric and server-wide migration are excluded. The complete fixed access entitlement and API fees relative to the lowest paid plan are not established by the reviewed technical documentation. | SQL Server native client connection ↗SQL Server native client connectionChecked 2026-10-16 |
| What permission is needed for the documented downstream use? | -Customer-administered SQL Server 2025 database using native SQL, compatible native database backup/restore and separately enabled table CDC; Azure Synapse, Fabric and server-wide migration are excluded. Applicable downstream processing, redistribution and AI-use conditions remain unestablished for the declared route. | SQL Server native client connection ↗SQL Server native client connectionChecked 2026-10-16 |
| Which external write operations are documented? | Customer-configurable write interfaces with validationCustomer-administered SQL Server 2025 database using native SQL, compatible native database backup/restore and separately enabled table CDC; Azure Synapse, Fabric and server-wide migration are excluded. Customer-defined tables and procedures expose DML under database authorization. | Transact-SQL statements ↗INSERT, UPDATE, DELETE and execution statementsChecked 2026-10-16 |
| How can customers connect an application they build or choose? | Customer-configurable interfaces for custom applicationsCustomer-administered SQL Server 2025 database using native SQL, compatible native database backup/restore and separately enabled table CDC; Azure Synapse, Fabric and server-wide migration are excluded. Customers can create stored procedures and grant applications database access. | SQL Server create stored procedures ↗CREATE PROCEDURE and schema permissionsChecked 2026-10-16 |
| What mechanism supports repeatable extraction of changes? | Database change-data captureCustomer-administered SQL Server 2025 database using native SQL, compatible native database backup/restore and separately enabled table CDC; Azure Synapse, Fabric and server-wide migration are excluded. Separately enabled CDC captures DML for selected tables, with edition and administrative prerequisites. | SQL Server change tracking and CDC ↗Change data captureChecked 2026-10-16 |
| How are integration limits disclosed? | -Customer-administered SQL Server 2025 database using native SQL, compatible native database backup/restore and separately enabled table CDC; Azure Synapse, Fabric and server-wide migration are excluded. The reviewed native database route does not establish a universal numeric extraction quota or API retry contract. | SQL Server native client connection ↗Native connection routeChecked 2026-10-16 |
| Where can a usable data copy be delivered? | Database extract delivered to the customerCustomer-administered SQL Server 2025 database using native SQL, compatible native database backup/restore and separately enabled table CDC; Azure Synapse, Fabric and server-wide migration are excluded. Native backup files can be held and restored by the customer. | SQL Server native BACKUP ↗Backup devices and database backupChecked 2026-10-16 |
| What retrieval rights are documented at cancellation? | -Customer-administered SQL Server 2025 database using native SQL, compatible native database backup/restore and separately enabled table CDC; Azure Synapse, Fabric and server-wide migration are excluded. The reviewed extraction documentation does not establish contractual retrieval rights after cancellation or license termination. | SQL Server native client connection ↗SQL Server native client connectionChecked 2026-10-16 |
| How can customers define their own business logic? | Customer-authored native scripts or custom APIsCustomer-administered SQL Server 2025 database using native SQL, compatible native database backup/restore and separately enabled table CDC; Azure Synapse, Fabric and server-wide migration are excluded. Customers create native stored procedure definitions under schema grants. Ownership and portability rights are separate. | SQL Server create stored procedures ↗Create stored procedureChecked 2026-10-16 |
| What rights or portability are documented for custom workflow artifacts? | -Customer-administered SQL Server 2025 database using native SQL, compatible native database backup/restore and separately enabled table CDC; Azure Synapse, Fabric and server-wide migration are excluded. Ownership, reusable export and independent execution rights for native workflow artifacts remain unestablished. | SQL Server native client connection ↗SQL Server native client connectionChecked 2026-10-16 |
| What usable data or native definitions can leave before cancellation? | Original objects or native schema/data with a documented independent restore/use pathCustomer-administered SQL Server 2025 database using native SQL, compatible native database backup/restore and separately enabled table CDC; Azure Synapse, Fabric and server-wide migration are excluded. Native RESTORE rebuilds the scoped compatible database. Server-level dependencies and incompatible version downgrades are excluded. | SQL Server native RESTORE ↗Restore database and compatibilityChecked 2026-10-16 |
SOURCES / SCOPE / HISTORY
Sources and open questions
This review is based on the documentation below. Live account behavior and customer-specific agreements haven’t been tested.
Still to confirm
- Access cost barrier: The complete fixed access entitlement and API fees relative to the lowest paid plan are not established by the reviewed technical documentation.
- Downstream permission: Applicable downstream processing, redistribution and AI-use conditions remain unestablished for the declared route.
- Limit visibility: The reviewed native database route does not establish a universal numeric extraction quota or API retry contract.
- Post-cancellation access: The reviewed extraction documentation does not establish contractual retrieval rights after cancellation or license termination.
- Rights to custom logic: Ownership, reusable export and independent execution rights for native workflow artifacts remain unestablished.
Documentation
Assessment checked 2026-10-16. Each answer retains its source and applicable route; the check date does not establish live account behavior.