Stored procedures are often one of the hardest parts of database migration—not necessarily because they contain the most code, but because their dependencies and business logic can be difficult to estimate.
For teams migrating to GBase Database (GBase 8s), the better approach is to turn stored procedure migration into a measurable process.
1. Sample Before Estimating
Don't estimate the entire migration from total procedure count or lines of code.
Instead, select a representative sample—such as 30–50 procedures covering different complexity levels.
Use the Migration Toolkit (MTK) to assess and convert the sample, then record the actual effort required.
This gives you a data point based on your environment rather than a generic migration estimate.
2. Classify the Procedures
Put each procedure into three practical categories:
Auto-convertible
Requires little or no manual modification.
Rewrite-required
Contains syntax, packages, dependencies, or logic that needs manual adaptation.
Retire
Unused or obsolete code that does not need to be migrated.
This classification is often more useful than simply counting lines of PL/SQL.
3. Estimate from Measured Rates
Once the sample is classified, estimate the larger migration based on the measured effort for each category.
For example:
Estimated effort = Procedure volume × Measured effort per category
The important part is the measured rate.
A 10,000-line procedure isn't necessarily ten times harder than a 1,000-line procedure. Complexity, dependencies, cursor usage, and external packages can matter much more than line count.
4. Build Golden Tests
Before modifying production logic, capture representative inputs and expected outputs from the existing database.
Then run equivalent tests against the target environment and compare the results.
This is particularly important for procedures involving:
- Complex business rules
- Cursor-heavy logic
- Exception handling
- Database-specific packages
- Transaction behavior
Compatibility tools can automate much of the mechanical conversion, but business behavior still needs validation.
5. Find the Real Migration Risk
For GBase Database (GBase 8s) migrations, the hardest procedures are usually not simply the longest ones.
Pay particular attention to database-specific functionality, complex procedural logic, and dependencies on vendor-specific packages.
The key lesson is simple:
Don't estimate stored procedure migration from code volume. Estimate it from sampled conversion results, complexity, and measured remediation effort.
A two-week sampling exercise can be far more valuable than a two-month schedule built on assumptions.
