Ssis-668 Jun 2026

| # | Requirement | Target | |---|-------------|--------| | | Performance | Mapping resolution adds < 5 ms overhead per component at runtime (benchmark on a 4‑core VM). | | NFR‑2 | Scalability | UI must handle components with > 200 properties without lag (load time < 1 s). | | NFR‑3 | Security | Parameter values are treated like any other SSIS parameter – no additional exposure. | | NFR‑4 | Usability | The mapping UI follows the same Visual Studio theme and accessibility guidelines (keyboard navigation, screen‑reader labels). | | NFR‑5 | Reliability | No regression in existing integration tests (≥ 2000 automated package runs). | | NFR‑6 | Internationalization | All UI strings externalized; support EN, FR, DE, JP out‑of‑the‑box. | | NFR‑7 | Documentation | Updated help file (CHM/online) with a new “Dynamic Property Mapping” chapter; 2‑page quick‑start guide. | | NFR‑8 | Versioning | The feature is introduced in SQL Server 2025 (15.x) , with a compatibility level flag for earlier versions. |

Enable package developers to without having to edit the component’s XML manually or rely on the “Expression” UI hack. SSIS-668

Insufficient permissions or access rights to execute the package or access certain resources can also trigger this error. | # | Requirement | Target | |---|-------------|--------|