From: | Pavan Pusuluri <pavan(dot)pusuluri(at)gmail(dot)com> |
---|---|
To: | aditya desai <admad123(at)gmail(dot)com> |
Cc: | mustafa(dot)pekgoz(at)forenda(dot)com(dot)tr, Pgsql Performance <pgsql-performance(at)lists(dot)postgresql(dot)org> |
Subject: | Re: OLEDB for PostgreSQL |
Date: | 2021-04-21 01:45:16 |
Message-ID: | CAOLHn8a7114hUi-TH4NwxOnP_BO_W6hmCf_Tm=EOHafsSa0H8Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-performance |
I have been using SSIS for migrating data only for non-aws stuff.
If your target is on AWS, you can use SCT nd DMS.
You might also want to look into the link....https://youtu.be/YKJub0zVztE
Regards
Pavan
On Mon, Apr 19, 2021, 8:10 AM aditya desai <admad123(at)gmail(dot)com> wrote:
> Hi Mustafa,
> You can look into the SQLine tool. We recently used to migrate MSSQL to
> PostgreSQL. For procedures/functions etc you need to have good amount of
> understanding of TSQL and PL-PGSQL. SQLine will convert 60-80% of you TSQL
> code. Some manual effort is required at the end.
>
> Regards,
> Aditya.
>
> On Fri, Apr 16, 2021 at 4:03 PM <mustafa(dot)pekgoz(at)forenda(dot)com(dot)tr> wrote:
>
>> Hello,
>>
>>
>>
>> We want to start migration to POSTGRESQL13 from MSSQL SERVER but we
>> couldnt find any solution for oledb drivers. Please help us to find a
>> solution or any workaround if possible.
>>
>>
>>
>>
>>
>>
>>
>> Thanks.
>>
>> Mustafa
>>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Wells Oliver | 2021-04-21 20:06:09 | Diagnosing outdated auto analyze dates... |
Previous Message | Yambu | 2021-04-20 11:37:34 | get metadata after hardware failure |
From | Date | Subject | |
---|---|---|---|
Next Message | David Rowley | 2021-04-21 14:14:21 | Re: Planning performance problem (67626.278ms) |
Previous Message | Jeremy Schneider | 2021-04-20 21:00:33 | Re: Planning performance problem (67626.278ms) |