Workload scope
Stored procedure and UDF migration covers procedural control flow, custom functions, dynamic SQL, error handling, side effects, and test harnesses for converted routines.
Shared migration method
Treat routines as executable application logic. Inventory parameters, return types, dependencies, temporary objects, transactional assumptions, dynamic SQL, error paths, schedules, and callers. Decide whether each routine should become a target-native routine, a tested SQL model, or an external service or orchestration step; do not hide a runtime dependency inside a syntax conversion claim.
The accepted conversion includes test fixtures for normal, boundary, invalid, and retry paths, plus a clear ownership and deployment sequence for every dependent object.
Routine controls
- Make input/output contracts and side effects explicit before rewriting control flow.
- Replace implicit session state and temporary-object assumptions with durable, observable target patterns.
- Parameterise dynamic SQL and validate identifiers, types, and failure paths.
- Run deterministic tests before integration, reconciliation, and cutover rehearsal.
When to use a pair-specific guide
Use a retained pair-specific page when the source runtime creates a specific decision—for example notebook macros, Hive-style scripts, Oracle packages, or target routine limitations. The shared guide owns the common assessment and test method.
Review points
- Routine boundaries and side effects
- Input/output typing and error behavior
- Dynamic SQL and transaction assumptions
- Replayable tests for converted functions and procedures
Acceptance criteria
A stored procedure / udf migration page is complete when the migration team can identify source assets, understand conversion assumptions, review unsupported or ambiguous constructs, run validation checks, and decide whether the workload is ready for cutover.
For each related path, confirm that the child page explains what changes, how conversion works, which patterns are supported, what can drift, and which evidence is required before production traffic moves to the target platform.