Postgres SQL is support in Hana Database ?

[Former Member]

Hi Expert,

I have existing PostgreSQL DB now our requirement to move the database to Hana ,

So can we directly used the PostgreSQL Script in Hana to create the same structure of database ?

Thanks,

Sumit

[lucas_oliveira]

Hi Sumit,

Well looks like you faced your first migration issue and an old classic: databases don't implement SQL standards only, they do their own thing. COPY function is an example which is not on the SQL Standard. HANA on the other hand, does not have that feature (it sure have other import/export features).

So for the COPY function, I'm sure you can verify on the Postgres documentation how generate insert statements instead of COPY. Of course, you can still bump into differences such as: data types, imperative logic, etc.

So what I see here is possibly a database migration project (unless you're dealing with a fairly simple database *and* you're not super tied to Postgres specifics) . If that's the case, then using a migration tool (like SAP Data Services) to support the process is a good idea (at least for the data migration). Procedures, functions and complex types defined will demand their migration time and effort accordingly.

BRs,

Lucas de Oliveira

[Former Member]

Hi Lucas,

Thanks for your reply .

Our PostgreSQL is not quit simple . As there are some predefined (Inbuild) Schema like information_schema is used to create function /Procedure or trigger , So my concern how we can handle that like to create the same in Hana?

Thanks,

Sumit

[lucas_oliveira]

Hi Sumit,

One thing that it's important to stress here is before going any further: db migrations are *not* straightforward. There's no magic button you can push to make it happen.

You'll need to evaluate exactly what you have on postgres that needs to go to HANA and specially how to adapt the current scenario to HANA. For example: maybe on your Postgres system you have many databases with many schemas on each database. In that case, it seems to fit into an MDC scenario where each HANA tenant would match to a specific Postgres database. Of course, this is an example not necessarily the reality.

Another detail here is to keep up with the application side expectations. In other words, application migration (or more likely adaptation). That's just as hard as a db migration and depends strongly on what you use at the front-end (how tied you are to postgres). In short, a successful migrated DB does not mean you can simply aim the application at the new database and hope it will work.

Again, this kind of study/preparation and decisions needs to be done by whoever is driving the migration taking into account the applications used therein. No magic.

As per schema information_schema is part of postgres architecture and I'm not sure what is its counter part on HANA (if exists).

BRs,

Lucas de Oliveira