Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1smPtp-005Xsn-Vz for pgsql-admin@arkaria.postgresql.org; Fri, 06 Sep 2024 03:44:42 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1smPto-005j1N-2F for pgsql-admin@arkaria.postgresql.org; Fri, 06 Sep 2024 03:44:40 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1smPtn-005iyD-LR for pgsql-admin@lists.postgresql.org; Fri, 06 Sep 2024 03:44:40 +0000 Received: from mail-pj1-x1031.google.com ([2607:f8b0:4864:20::1031]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1smPtg-000NNr-OS for pgsql-admin@lists.postgresql.org; Fri, 06 Sep 2024 03:44:37 +0000 Received: by mail-pj1-x1031.google.com with SMTP id 98e67ed59e1d1-2d8b96c18f0so1191054a91.2 for ; Thu, 05 Sep 2024 20:44:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bitnine-net.20230601.gappssmtp.com; s=20230601; t=1725594272; x=1726199072; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=MraearJiOEhDO32FIlwaSK0Ujkw1BwaVS5XU/iezq7E=; b=Vg3torXm8Gh6+4qrFtaIJ6oKHRxeXRWmfVyOUT2UVPXiMLSA45NkHN8kIAU1UfLQB+ g/vL05En4lckGoq7wdT2oxZYrh+EvcWl/y9+9BRy5ZtI86hYS9qh1zpGxV3MkVklyUey V/Rs4n++tlzqjnDUnvJvQ1tenp8cl9N59aLrRlZ4yK9mNR0PDG1WK4Yum2OacrtFAJAb NwZ7tUblamxjbEK8XL6xSgDEMOxJS1Ns8iiTD7b52I62GDl1/FViciYGbFVeg57xAsmb Jzu+njARHcFkwFMUoAwJG3mCOxEZqDXqZd+SH8aeBxNtJ5M0Gpw043pkuhEprLWypTOk CwHA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1725594272; x=1726199072; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=MraearJiOEhDO32FIlwaSK0Ujkw1BwaVS5XU/iezq7E=; b=w75F/NG66X/7oBJC3fc0k6vNeFH/tyOljXgw4nFnidcd5a8u3jMH/FjG/b1bukD5JK 5XUSYmBnrdrGi3CeakH2wDXlEheDOWlqcytPO0XZB7ofxtYxehELcSzKf5XUrXUuUOJl cdEaUEocjR0omHXHsWbHfu3GG1dW21g7wq7wOo2BylUtQ03vpE0qmlcK8no6mRlKhXax b/JaDk3XeCM6FnmSm4TVzo3c8v+S51adkdRHCtwtCIXLrdMQsZCUrsXGkf6ZNsA4x5lz AlN8b/FEL/+Yd5NR9p07o7MKpHkLceTmlJSY7z5kPH+bcmUlPkcXzLgQRJMS4dZ3V7cn VsGg== X-Gm-Message-State: AOJu0Yx6e0YMSnSNcZXHKBIvdEoX0AiZgBdt/rPzXp72UUsGYaE1bzfr P0WYd/K5MgEneGMrYUM9vPtcNJtOiqO/zmM6k0xc3bgh5+a5MQ3tQG7hqjs9Nb6oNb9Kr65Zmtf oAnu7dn2siAnp8mKP5Uie0AhZeoXqUzOAAxMiA3sQbV1C3NuUbl9/3g== X-Google-Smtp-Source: AGHT+IETcbWfkS67TRidRF00z8H/3SUCYD1k33Y3bgKjtEZKhq+iPIXp3uNf5Cd6pAcl/8DYnYhhQfoJkVQPU/wWYLs= X-Received: by 2002:a17:90a:668b:b0:2c9:7ebd:b957 with SMTP id 98e67ed59e1d1-2dad4ef2364mr1782385a91.11.1725594271667; Thu, 05 Sep 2024 20:44:31 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Muhammad Usman Khan Date: Fri, 6 Sep 2024 08:44:20 +0500 Message-ID: Subject: Re: Incremental load from SQL server DB to postgressql To: Sabyasachi Mukherjee Cc: "pgsql-admin@lists.postgresql.org" Content-Type: multipart/alternative; boundary="00000000000096f8d906216b394e" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000096f8d906216b394e Content-Type: text/plain; charset="UTF-8" Hi, You can use pgloader. It is a powerful tool that can migrate data from SQL Server to PostgreSQL efficiently, and it supports incremental loads or the other option is to use file_fdw, it allows PostgreSQL to directly query flat files as if they were tables, without importing the data into PostgreSQL. It can be useful if you can periodically export data from SQL Server into flat files and then query them from PostgreSQL. On Thu, 5 Sept 2024 at 18:54, Sabyasachi Mukherjee < mukherjee.sabyasachi@outlook.com> wrote: > Hello All, > > I have to implement an incremental load from a SQL server DB to a > postgresql DB. I would prefer it to be pull from postgres. > SSIS is not the preferred option. Can you please advise about the > possibilities? > > Sabyasachi Mukherjee > --00000000000096f8d906216b394e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

=
Hi,

You can use=C2=A0 pgloader. It is a powerful tool that can migrate data from SQL Server to Po= stgreSQL efficiently, and it supports incremental loads or the other option= is to use=C2=A0file_fdw, it=C2=A0allows PostgreSQL= to directly query flat files=C2=A0 as if they were tables, without importi= ng the data into PostgreSQL. It can be useful if you can periodically expor= t data from SQL Server into flat files and then query them from PostgreSQL.=

On Thu, 5 Sept 2024 at 18:54, Sabyasachi Muk= herjee <mukherjee.sa= byasachi@outlook.com> wrote:
Hello All,

I have to implement an incremental load from a SQL server DB to a postgresq= l DB. I=C2=A0would prefer it to be pull from postgres.
SSIS is not the preferred option. Can you please advise about the possibili= ties?

Sabyasachi Mukherjee
--00000000000096f8d906216b394e--