SQL Server DB objects Lower to Upper case conversion - Issues/validation criteria @data migration.
As part of the data migration project (Using Pega Data Mover Utility) from MSSQL to Oracle,we were asked to convert the SQL Server DB objects from Lower to Upper case followed by kick starting the Data Migration process.
We would like to know the list of known application or DB related issues/validation criteria to be taken into account for this implementation.
@PradeepChowdaryP Hi Pradeep, You will most likely find some issues. Particularly syntax for SP and SQL etc each has some unique dialect quirks. The catalog data for the MS/SQL is mixed case. ORACLE is upper case... These compatibility issues are not within the scope of Pega expertise per se.
I would recommend not doing anything with OOTB programming objects like functions and stored procedures. You can use generate DDL against the target ORACLE DB. I would also check property mappings before committing to a particular run of whatever you're doing to convert the data. Note again that these issues are external to Pega somewhat and you should rely on experts who do these sorts of conversions on a regular basis. Converting from MS/SQL to ORACLE is not in our collective wheelhouse. You will most likely find issues.