Repository navigation
Test | Add test coverage for #3857 : NullReferenceException issue when using SqlDataAdapter with Always Encrypted and UpdateBatchSize > 1 #3876
Description
Activity
- addedRepro Available ✔️Issues that are reproducible with repro provided.Issues that are reproducible with repro provided.
on Jan 12, 2026 - addedArea\TestsIssues that are targeted to tests or test projectsIssues that are targeted to tests or test projects
on Jan 12, 2026 - changed the title
[-]Add test coverage for #3857 : NullReferenceException issue when using SqlDataAdapter with Always Encrypted and UpdateBatchSize > 1[/-][+]Test | Add test coverage for #3857 : NullReferenceException issue when using SqlDataAdapter with Always Encrypted and UpdateBatchSize > 1[/+]on Mar 31, 2026 /triage
🔍 Triage Summary (on-demand re-triage)
Check Result Issue type Task Environment Not applicable — this is a test-coverage task, not a bug report Area Area\Tests(already applied)Duplicates None found — related (not duplicate) work: #3716, #3857, #3848, #3845, #3849 Regression Not applicable Analysis
This is a test-coverage task requesting that the repro from #3716 be adapted into permanent automated test coverage for the fix landed in #3857 (NullReferenceException in
SqlDataAdapterwith Always Encrypted andUpdateBatchSize > 1). The issue also notes that adding this coverage surfaced pre-existing gaps in the existing Always Encrypted test suite that should be addressed alongside it, and that the resulting tests need to be backported torelease/6.1. Since this is process/engineering work rather than a customer-facing defect, it is a routine P2 task — useful for closing a coverage gap but not urgent or blocking.Next Steps
- Assign to Copilot coding agent (or a contributor) to: (1) port the NullReferenceException when using SqlDataAdapter with Always Encrypted and UpdateBatchSize > 1 #3716 repro into
src/Microsoft.Data.SqlClient/tests/ManualTests/Always Encrypted test project(s), covering both sync and asyncSqlDataAdapter.Update/Fillpaths withUpdateBatchSize > 1; (2) audit and fix the pre-existing Always Encrypted test issues mentioned in the description before merging new coverage; (3) open a follow-up PR targetingrelease/6.1to backport the new tests, consistent with the backport pattern already used in Backport to MDS v6.1 || NullReferenceException issue when using SqlDataAdapter with Always Encrypted and UpdateBatchSize > 1 #3845/Backport to MDS v6.0 || NullReferenceException issue when using SqlDataAdapter with Always Encrypted and UpdateBatchSize > 1 #3848/Backport to MDS v5.2 || NullReferenceException issue when using SqlDataAdapter with Always Encrypted and UpdateBatchSize > 1 #3849. - Link the new test PR back to Fixing NullReferenceException issue with SqlDataAdapter #3857 and this issue when opened.
- No duplicate issues found; the referenced issues (NullReferenceException when using SqlDataAdapter with Always Encrypted and UpdateBatchSize > 1 #3716, Backport to MDS v6.0 || NullReferenceException issue when using SqlDataAdapter with Always Encrypted and UpdateBatchSize > 1 #3848, Backport to MDS v6.1 || NullReferenceException issue when using SqlDataAdapter with Always Encrypted and UpdateBatchSize > 1 #3845, Backport to MDS v5.2 || NullReferenceException issue when using SqlDataAdapter with Always Encrypted and UpdateBatchSize > 1 #3849) are prior fix/backport work, not overlapping test-coverage tasks.
Note: This triage summary is auto-generated by an AI agent. The analysis and suggestions above have not been verified by a human maintainer. Please treat as preliminary guidance only.
Generated by SqlClient Issue Auto-Triage for #3876 · copilot · auto · 57.3 AIC · ⌖ 16.1 AIC · ⊞ 11.9K · ◷
- Assign to Copilot coding agent (or a contributor) to: (1) port the NullReferenceException when using SqlDataAdapter with Always Encrypted and UpdateBatchSize > 1 #3716 repro into
Metadata
Metadata
Assignees
Labels
Type
Projects
- StatusShow more project fieldsBacklog
We need to use the repro mentioned in #3716 for adding test coverage for fix introduced through #3857.
The earlier test coverage has identified some issues in existing always encrypted test cases which also need to be addressed while adding this test coverage.
Additionally this needs to be backported to release/6.1.