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 1s4Vys-004knZ-F8 for pgsql-general@arkaria.postgresql.org; Wed, 08 May 2024 01:20:26 +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 1s4Vyp-006Lj9-SN for pgsql-general@arkaria.postgresql.org; Wed, 08 May 2024 01:20:24 +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 1s4Vyp-006Lj0-HB for pgsql-general@lists.postgresql.org; Wed, 08 May 2024 01:20:24 +0000 Received: from mail-yw1-x1133.google.com ([2607:f8b0:4864:20::1133]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1s4Vyj-001xOK-Ht for pgsql-general@lists.postgresql.org; Wed, 08 May 2024 01:20:23 +0000 Received: by mail-yw1-x1133.google.com with SMTP id 00721157ae682-61df903aa05so41085447b3.3 for ; Tue, 07 May 2024 18:20:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1715131217; x=1715736017; 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=pL47TcCRT43+585ydN1rgc9I0672qG8UDNtw2JSS/z4=; b=LfqXPbHii6wFzDumMZjbK/ioTO89/4Z+UUe0DHj96rXFD6mquZkWnVLolqH8ecbVgp 04OjzRASsmjHGiHsQ1WmSyG1PPQ94l0Yaovbltfkxat3bqDWKl8dC/AH0ffxgkJSKkqS jc3lgpHEiC7nIWmuDqgxUgJKP8QewlMRITVFF4DB6FXPBP3B88uq5cFpM2QIE9zQN1fl zAJ9gW3dt/b6JVv66yKhadW6V0hDxZ7lYWDeNTCWVACfw5Ia3KQG8PdG/nklZdiAv45d ijHmIRc5uUAHu2i6mESnGoq9eQWxbt0Rci2pOgzOtvzc+gh8yhAWkradOtEB2lkvEFjF bXdA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1715131217; x=1715736017; 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=pL47TcCRT43+585ydN1rgc9I0672qG8UDNtw2JSS/z4=; b=lv+g8xosJV6s5dj7EmziWnqDIWdedMaC/Bx2mARKLiriOjNC+Rl2kupPm94sh6xO2Q MEgbI3EMhMMFo4WO286IJeUF4/cGdHcag1IxSGJ0Qf5m8UCEMG3TEQRrSFHDXqDP5FWF xzwvAe+JDnNbbnOBuWdYZQdf6TmPBxvSW+iaaIIiX0vJxxkqsQDvqC2xwDThP2C1/mvb 7Yq8wIr/hwPcJjNswuhVhiYn62rZ2xTpzKYu2oXXfN9iyKzTo9IduJrMspC6AG0r40mE cxm4rmrvZ1Wd/u9k00GA+qb19/AuFbIQ4a+I6bo1mUFIqnU9TT84Girr+1ORZznP0ADD Hm8A== X-Gm-Message-State: AOJu0YxYGs8CZATuUJ5B2pUbk+34h+vYbUsDMSXa7h6cvFuLgF013VzC du2KzCrTTjpE8FVv3t8/nBHMvHnGloKXT76vZJhw5kdQDVG5DlQcAlxln23MzdBZZRU2PfpV0sI 8zi7uvh8OePYaqWt/A0I+FJfMd8yMfTxx X-Google-Smtp-Source: AGHT+IGNIfDP3En59VHQ5pzN0T4EF3E4yrMas20BlWInJrFR38B34hKiTcCcn68nBb6TY9HPpgDKjPt8DNxKEjaIgwM= X-Received: by 2002:a0d:cb87:0:b0:617:cc94:31bf with SMTP id 00721157ae682-62085f0f094mr17215147b3.50.1715131216566; Tue, 07 May 2024 18:20:16 -0700 (PDT) MIME-Version: 1.0 References: <6f7520e512dcacd47eecb5b37b40554c@riseup.net> In-Reply-To: <6f7520e512dcacd47eecb5b37b40554c@riseup.net> From: Greenhorn Date: Wed, 8 May 2024 11:20:05 +1000 Message-ID: Subject: Re: Need help migrating MSSQL2008R2 tables into PGSQL & make PGSQL mimic MSSQL behaviour. To: buggedme@riseup.net Cc: pgsql-general@lists.postgresql.org Content-Type: multipart/alternative; boundary="000000000000e827d50617e71ac5" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000e827d50617e71ac5 Content-Type: text/plain; charset="UTF-8" How many tables do you have, and what are their sizes? I'm asking because if you're considering migrating to PostgreSQL, starting from scratch might be cleaner. This approach will also help you gain a deeper understanding of how data types are handled in PostgreSQL compared to MSSQL. On Wed, 8 May 2024 at 10:20, wrote: > I heard PGSQL can act like MSSQL behaviour so I'm trying to migrating > tables to try it myself, but I really > have hard time to migrating them. > > I already looked > > https://wiki.postgresql.org/wiki/Microsoft_SQL_Server_to_PostgreSQL_Migration_by_Ian_Harding > but > nothing is useful. For example, "Extension Links" section links are all > PAID links. > > I have *.MDF and *.ldf MSSQL2008R2 DATA files. > > Can anyone please give me a command to how to migrate those data? I do > not have MS' graphic studio GUI but I can > access this database using "Navicat Lite"(IP:Port login). > > > --000000000000e827d50617e71ac5 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
How many tables do you have, and what are= their sizes? I'm asking because if you're considering migrating to= PostgreSQL, starting from scratch might be cleaner. This approach will als= o help you gain a deeper understanding of how data types are handled in Pos= tgreSQL compared to MSSQL.

On Wed, 8 May 2024 at 10:20, <buggedme@riseup.net> wrote:
I heard PGSQL can act like MS= SQL behaviour so I'm trying to migrating
tables to try it myself, but I really
have hard time to migrating them.

I already looked
https://= wiki.postgresql.org/wiki/Microsoft_SQL_Server_to_PostgreSQL_Migration_by_Ia= n_Harding
but
nothing is useful. For example, "Extension Links" section links a= re all
PAID links.

I have *.MDF and *.ldf MSSQL2008R2 DATA files.

Can anyone please give me a command to how to migrate those data? I do
not have MS' graphic studio GUI but I can
access this database using "Navicat Lite"(IP:Port login).


--000000000000e827d50617e71ac5--