How can I get AirByte to also create primary keys, foreign keys, and indexes when moving a SQL Server database to a Postgres database (or any other cross database conversion)? I have a few projects where I was attempting to use AirByte and the destination database is unusable without having all the relationships and keys copied along with the data. Also how can I handle differences in types like between SQL Server relative timestamps and Postgres timestamps, GUID and UUID, etc.?

@[DEPRECATED] Marcos Marx turned this message into Zendesk ticket 2831 to ensure timely resolution!

Hey could you create an github issue on this so that team can look and get back to you