# Renewal worksheet — stay, Babelfish, or convert

Use with [Oracle and SQL Server to Aurora PostgreSQL](https://www.factualminds.com/blog/oracle-sql-server-to-aurora-postgresql-decision/). Fill counts from Babelfish Compass (SQL Server) or a DMS Schema Conversion assessment. Do not estimate them.

Babelfish is SQL Server only (TDS 7.1–7.4, port 1433, PostgreSQL on port 5432). Oracle has no Babelfish fork. Identifiers longer than 63 characters are rewritten. Linked servers need the `tds_fdw` extension from Babelfish 3.1.0. They are not a blanket "unsupported."

| Question | Oracle | SQL Server |
| --- | --- | --- |
| Engine today (RDS, EC2, or other) | | |
| License end date | | |
| Is the database the product? (yes / no) | | |
| Fork you are actually considering: stay / Babelfish / convert | stay or convert | stay, Babelfish, or convert |
| Compass report attached? (SQL Server, Babelfish only) | n/a | |
| Unsupported features you will fund (name them) | | |
| CLR, updatable cursors, or contained databases present? | | |
| Linked servers, and is `tds_fdw` acceptable? | | |
| Identifiers over 63 characters? | | |
| DMS Schema Conversion CRITICAL count (not converted) | | |
| SQL that lives in the application, not in the schema report | | |
| Who staffs the residue before cutover? | | |

## Fork

- Database is the product, or the residue is the project: stay.
- SQL Server, Compass unsupported list is one you will fund, PostgreSQL underneath is acceptable: Babelfish.
- CRITICAL items and application SQL are staffed: convert, then follow the DMS to Aurora playbook for cutover. This sheet is not the cutover runbook.

Do not enter a savings figure on this sheet.