RE: Substitute for table variable and data migration approach

From: Avadhut Narayan Joshi <AJoshi7(at)sensiaglobal(dot)com>
To: "pgsql-admin(at)lists(dot)postgresql(dot)org" <pgsql-admin(at)lists(dot)postgresql(dot)org>
Subject: RE: Substitute for table variable and data migration approach
Date: 2021-07-05 10:11:09
Message-ID: PH0PR18MB4608A2856F03A3AE38A428A39C1C9@PH0PR18MB4608.namprd18.prod.outlook.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Hello Geeks ,

Any suggestions / recommendations for below questions ?

Regards
Avadhut

Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10

From: Avadhut Narayan Joshi<mailto:AJoshi7(at)sensiaglobal(dot)com>
Sent: 02 July 2021 19:51
To: pgsql-admin(at)lists(dot)postgresql(dot)org<mailto:pgsql-admin(at)lists(dot)postgresql(dot)org>
Subject: Substitute for table variable and data migration approach

Hello Geeks ,

As in SQL Server we have table variable and it can be passed as a parameter to a stored procedure . Which is the best alternative for it in PostgreSQL ?

Also any advice / suggestions on tool which can be used to migrate data from SQL Server / Oracle to PostgreSQL ?
Solution should be

1. Performant on large DB size > 500 GB
2. Should have re-start logic
3. Should have error logging capabilities
4. Easy to deploy/use in Prod environment

Please give Suggestions / recommendations .

Regards
Avadhut

Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Yambu 2021-07-05 12:48:19 logical replication in high volume transactions
Previous Message Rui DeSousa 2021-07-04 21:32:46 Re: The trap when using pg_dumpall