Migration Framework for Firebird

Migration Framework for Firebird: A Comprehensive Enterprise Solution

Utilization Scenarios for the Migration Framework

How Migration Framework for Firebird works?

1.  Metadata Analysis: The Framework conducts an automatic examination of database metadata backups, producing a comprehensive report that identifies issues. Detected problems are categorized into those that can be resolved automatically and those necessitating manual intervention.
2. Data Migration Execution: Following the verification and potential adjustment of metadata, the Framework facilitates an automated conversion process. This involves simply transferring a set of files, placing databases in the legacy format into the designated incoming folder, and subsequently retrieving the fully operational database from the outgoing folder

Examples of automatic changes

Incompatibilties in stored procedures, triggers, functions, packages, view

• SUSPEND without return (only procedures)
• Usage of CURRENT_TIMESTAMP (now with TIMEZONE)
• usage of LOCAL (reserved word)

create or alter procedure sp_sample
as
begin
  insert into tablex (start_time, user, local) values (current_timestamp, current_user, 1);
  suspend;
end

create or alter procedure sp_sample
as
begin
  insert into tablex (start_time, user, "LOCAL") values (localtimestamp, current_user, 1);
  --suspend;
end

Usage of CURRENT_TIMESTAMP in computed fields

alter table TABLEX alter column COLUMN1 computed by (CURRENT_TIMESTAMP)
alter table TABLEX alter column COLUMN1 computed by (CURRENT_TIME)

alter table TABLEX alter column COLUMN1 computed by (LOCALTIMESTAMP) alter table TABLEX alter column COLUMN1 computed by (LOCALTIME)

ALTER TABLE CLIENTE ALTER COLUMN DT SET DEFAULT CURRENT_TIMESTAMP
ALTER TABLE CLIENTE ALTER COLUMN DT SET DEFAULT CURRENT_TIME

ALTER TABLE CLIENTE ALTER COLUMN DT SET DEFAULT LOCALTIMESTAMP
ALTER TABLE CLIENTE ALTER COLUMN DT SET DEFAULT LOCALTIME