regarding schema only migration from sqlserver to postgres with runmtk.sh

On Wed, Jun 15, 2016 at 8:31 AM, Durgamahesh Manne <
maheshpostgres9@gmail.com> wrote:

Running EnterpriseDB Migration Toolkit (Build 49.0.4) ...

​You should contact the supplier of this tool using their support
channels. The community is not responsible for this product.

I will note that by default PostgreSQL is not setup with a password on the
postgres (bootstrap) account. If the script in question isn't doing stuff
in the background to ensure PostgreSQL will accept a JDBC connection as the
postgres user with password you will need to do that manually. The
documentation covers how to go about setting up tcp/ip based access both on
the listening specification and within pg_hba.conf, as well as how to
assign a password to a user that does not have one.

David J.
​

---------- Forwarded message ----------
From: David G. Johnston <david.g.johnston@gmail.com>
Date: Wed, Jun 15, 2016 at 8:40 PM
Subject: Re: [GENERAL] regarding schema only migration from sqlserver to
postgres with runmtk.sh
To: Durgamahesh Manne <maheshpostgres9@gmail.com>

On Wed, Jun 15, 2016 at 11:00 AM, Durgamahesh Manne <
maheshpostgres9@gmail.com> wrote:

as per above discussion. i already enabled tcp/ip based access on which
the server to listen connections from client applications as well as
already set password for required user

may i know the recommended approach for migrate the tables from sql server
to postgesql

please let me know

​I've helped you all that I can, and I do not respond well to personal
emails asking for help. Direct all correspondence to the list: it is ok to
CC: people who have already replied. And, as I said, this is not the
correct forum for your question. You are using a third-party tool so they
are the ones you should be asking. In this case they do monitor these
lists and may chime in but as a matter of proper etiquette this discussion
is off-topic for this list. Specifically it is a request for help on how
to use a specific non-community-PostgreSQL product.

I suspect that "dnsname" is not actually the host name for your server...if
the URL is invalid and you've munged it for email it would be impossible
for us to point out to you how/if that is so.

David J.

sir as per above discussion

conn =jdbc:postgresql://archive.tf.com:5432/
<http://archive.trustfort.com:5432/edb&gt;edb

i earlier mentioned the host name of the server (archive.tf.com)

may i know recommended approach to migrate the tables from sql server to
postgresql instead of using 3rd party tools

thank you

---------- Forwarded message ----------
From: Durgamahesh Manne <maheshpostgres9@gmail.com>
Date: Wed, Jun 15, 2016 at 8:57 PM
Subject: Fwd: [GENERAL] regarding schema only migration from sqlserver to
postgres with runmtk.sh
To: pgsql-general@postgresql.org
Cc: "David G. Johnston" <david.g.johnston@gmail.com>

---------- Forwarded message ----------
From: David G. Johnston <david.g.johnston@gmail.com>
Date: Wed, Jun 15, 2016 at 8:40 PM
Subject: Re: [GENERAL] regarding schema only migration from sqlserver to
postgres with runmtk.sh
To: Durgamahesh Manne <maheshpostgres9@gmail.com>

On Wed, Jun 15, 2016 at 11:00 AM, Durgamahesh Manne <
maheshpostgres9@gmail.com> wrote:

as per above discussion. i already enabled tcp/ip based access on which
the server to listen connections from client applications as well as
already set password for required user

may i know the recommended approach for migrate the tables from sql server
to postgesql

please let me know

​I've helped you all that I can, and I do not respond well to personal
emails asking for help. Direct all correspondence to the list: it is ok to
CC: people who have already replied. And, as I said, this is not the
correct forum for your question. You are using a third-party tool so they
are the ones you should be asking. In this case they do monitor these
lists and may chime in but as a matter of proper etiquette this discussion
is off-topic for this list. Specifically it is a request for help on how
to use a specific non-community-PostgreSQL product.

I suspect that "dnsname" is not actually the host name for your server...if
the URL is invalid and you've munged it for email it would be impossible
for us to point out to you how/if that is so.

David J.

sir as per above discussion

conn =jdbc:postgresql://archive.tf.com:5432/
<http://archive.trustfort.com:5432/edb&gt;edb

i earlier mentioned the host name of the server (archive.tf.com)

may i know recommended approach to migrate the tables from sql server to
postgresql instead of using 3rd party tools

thank you

&& i already enabled the listen addresses '*' to listen all available ip
interfaces

thank you

On 06/15/2016 08:27 AM, Durgamahesh Manne wrote:

---------- Forwarded message ----------
From: *David G. Johnston* <david.g.johnston@gmail.com
<mailto:david.g.johnston@gmail.com>>
Date: Wed, Jun 15, 2016 at 8:40 PM
Subject: Re: [GENERAL] regarding schema only migration from sqlserver to
postgres with runmtk.sh
To: Durgamahesh Manne <maheshpostgres9@gmail.com
<mailto:maheshpostgres9@gmail.com>>

On Wed, Jun 15, 2016 at 11:00 AM, Durgamahesh Manne
<maheshpostgres9@gmail.com <mailto:maheshpostgres9@gmail.com>>wrote:

as per above discussion. i already enabled tcp/ip based access on
which the server to listen connections from client applications as
well as already set password for required user

may i know the recommended approach for migrate the tables from sql
server to postgesql

please let me know

​I've helped you all that I can, and I do not respond well to personal
emails asking for help. Direct all correspondence to the list: it is ok
to CC: people who have already replied. And, as I said, this is not the
correct forum for your question. You are using a third-party tool so
they are the ones you should be asking. In this case they do monitor
these lists and may chime in but as a matter of proper etiquette this
discussion is off-topic for this list. Specifically it is a request for
help on how to use a specific non-community-PostgreSQL product.

I suspect that "dnsname" is not actually the host name for your
server...if the URL is invalid and you've munged it for email it would
be impossible for us to point out to you how/if that is so.

David J.

sir as per above discussion

conn =jdbc:postgresql://archive.tf.com <http://archive.tf.com&gt;:5432/
<http://archive.trustfort.com:5432/edb&gt;edb

i earlier mentioned the host name of the server (archive.tf.com
<http://archive.tf.com&gt;)

Are you sure?

When I enter archive.tf.com or tf.com in a browser I get:

http://www.cyberfinder.com/

I would:

1) Verify the host name.

2) Then try connecting via a non-JDBC method, say using psql. If that
works go to 3), otherwise come back here with information on what you
did and how it failed.

3) Then try the migration tool. If that fails contact EDB.

may i know recommended approach to migrate the tables from sql server
to postgresql instead of using 3rd party tools

thank you

--
Adrian Klaver
adrian.klaver@aklaver.com

--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

On Wed, Jun 15, 2016 at 11:27 AM, Durgamahesh Manne <
maheshpostgres9@gmail.com> wrote:

may i know recommended approach to migrate the tables from sql server to
postgresql instead of using 3rd party tools

​Answering this specifically.

There are none. The community PostgreSQL project maintains no tools that
speak to SQL Server.

One possible option to use the PostgreSQL's FDW capabilities with a
suitable third-party extension that does talk to SQL Server.

The other is to dump plain SQL, hopefully standard-conforming, INSERT
statements from the SQL Server and load them into PostgreSQL via psql.

I suppose SQL Server has some means to export in TSV/CSV or other
row-oriented structured output. The \copy psql meta-command or COPY SQL
​command could load that data.

Depending on the table structures having SQL Server dump the DDL (i.e.,
CREATE TABLE) for the tables and loading them via psql might be possible as
well.

​One area that the commercial space ​helps fulfill is inter-vendor
inter-operability tools. While this is a boon to the PostgreSQL community
as matter of practicality support for those tools. Before using said tools
you should ensure that you can reliably connect, using the standard tools,
to the databases in question and perform general actions thereon. Failures
there should be resolved first and the communities can help you with that.

David J.

On Wed, Jun 15, 2016 at 11:27 AM, Durgamahesh Manne <
maheshpostgres9@gmail.com> wrote:

i earlier mentioned the host name of the server (archive.tf.com)

​No, you did not. And if you believe you did that may indeed be part of
the problem.

The log you showed has this:

conn =jdbc:postgresql://dnsname:5432/edb

If you didn't change that for the email then there is at least one of your
problems.

Maybe you stuck the name of the host in a variable named "dnsname" but it
didn't get properly dereferenced?

David J.
​

On 06/15/2016 01:30 PM, David G. Johnston wrote:

On Wed, Jun 15, 2016 at 11:27 AM, Durgamahesh Manne
<maheshpostgres9@gmail.com <mailto:maheshpostgres9@gmail.com>>wrote:

may i know recommended approach to migrate the tables from sql
server to postgresql instead of using 3rd party tools

​Answering this specifically.

There are none. The community PostgreSQL project maintains no tools
that speak to SQL Server.

That is true, but the external PostgreSQL community does:

https://github.com/tds-fdw/tds_fdw

One possible option to use the PostgreSQL's FDW capabilities with a
suitable third-party extension that does talk to SQL Server.

If you have access to MS Access, you can create linked tables between
MSSQL and PostgreSQL. You can then create queries to move the data
between the tables. Libreoffice may have similar functionality as well
(I don't know).

Sincerely,

JD

--
Command Prompt, Inc. http://the.postgres.company/
+1-503-667-4564
PostgreSQL Centered full stack support, consulting and development.
Everyone appreciates your honesty, until you are honest with them.

--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

On 6/15/2016 1:30 PM, David G. Johnston wrote:

One possible option to use the PostgreSQL's FDW capabilities with a
suitable third-party extension that does talk to SQL Server.

The other is to dump plain SQL, hopefully standard-conforming, INSERT
statements from the SQL Server and load them into PostgreSQL via psql.

last time I had to convert some MS SQL to another database (it was MySQL
but thats immaterial), I wrote a perl script to do it. there were
only 6 or 8 tables, so I manually created the schema, then my perl
script stepped through each table, for each row, fetching from the
source database and inserting into the destination.

--
john r pierce, recycling bits in santa cruz

From: pgsql-general-owner@postgresql.org [mailto:pgsql-general-owner@postgresql.org] On Behalf Of David G. Johnston
Sent: Wednesday, June 15, 2016 1:31 PM
To: Durgamahesh Manne <maheshpostgres9@gmail.com>
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] regarding schema only migration from sqlserver to postgres with runmtk.sh

On Wed, Jun 15, 2016 at 11:27 AM, Durgamahesh Manne <maheshpostgres9@gmail.com <mailto:maheshpostgres9@gmail.com> > wrote:

may i know recommended approach to migrate the tables from sql server to postgresql instead of using 3rd party tools

​I suppose SQL Server has some means to export in TSV/CSV or other row-oriented structured output. The \copy psql meta-command or COPY SQL ​command could load that data.

David J.

There are MANY tools for sql server, many are built in (aka free) that will generate DDL, or extract data, or both, plus you can directly query the system catalogs, just like PG. Utterly trivial stuff to use and Postgres can ingest all of it since it’s normally either flat file or ansi sql.

MikeS

sir

as per above discussion .the URL which i mentioned in toolkit properties
was 100% correct .i have checked db connectivity from another cluster with
psql .connection esatblished to below mentioned database
conn =jdbc:postgresql://archive.trustfort.com:5432/edb

thank you for the valuable information

On Thu, Jun 16, 2016 at 3:08 AM, Mike Sofen <msofen@runbox.com> wrote:

On 06/15/2016 08:50 PM, Durgamahesh Manne wrote:

sir

as per above discussion .the URL which i mentioned in toolkit properties
was 100% correct .i have checked db connectivity from another cluster
with psql .connection esatblished to below mentioned database
conn =jdbc:postgresql://archive.trustfort.com:5432
<http://archive.trustfort.com:5432&gt;/edb

thank you for the valuable information

So does this mean the migration is working now?

--
Adrian Klaver
adrian.klaver@aklaver.com

--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

sir

PostgreSQL always no1 in world
as per above discussion

migration not working from sql to postgreSQL with runmtk.sh

Connecting with source SQL Server database server...
Connected to Microsoft SQL Server, version '10.50.1600'
Connecting with target EnterpriseDB database server...
MTK-10045: The URL specified for the "target" database is invalid.
Check the connectivity credentials.
Stack Trace:
com.edb.MTKException: MTK-10045: The URL specified for the "target"
database is invalid.
Check the connectivity credentials.

same error repeated even there mentioned correct credentials as here i
checked multiple times

thank you

On Thu, Jun 16, 2016 at 10:19 AM, Durgamahesh Manne <
maheshpostgres9@gmail.com> wrote:

sir

PostgreSQL always no1 in world
as per above discussion

migration not working from sql to postgreSQL with runmtk.sh

Connecting with source SQL Server database server...
Connected to Microsoft SQL Server, version '10.50.1600'
Connecting with target EnterpriseDB database server...
MTK-10045: The URL specified for the "target" database is invalid.
Check the connectivity credentials.
Stack Trace:
com.edb.MTKException: MTK-10045: The URL specified for the "target"
database is invalid.
Check the connectivity credentials.

same error repeated even there mentioned correct credentials as here i
checked multiple times

​Maybe you should try using an IP address instead of a host name.

David J.​

On 06/16/2016 07:19 AM, Durgamahesh Manne wrote:

sir

PostgreSQL always no1 in world
as per above discussion

migration not working from sql to postgreSQL with runmtk.sh

Connecting with source SQL Server database server...
Connected to Microsoft SQL Server, version '10.50.1600'
Connecting with target EnterpriseDB database server...
MTK-10045: The URL specified for the "target" database is invalid.
Check the connectivity credentials.
Stack Trace:
com.edb.MTKException: MTK-10045: The URL specified for the "target"
database is invalid.
Check the connectivity credentials.

same error repeated even there mentioned correct credentials as here i
checked multiple times

Are you sure you are looking at the right file?

Also:

Have you looked here?:

https://www.enterprisedb.com/docs/en/9.5/migrate/Postgres_Plus_Migration_Guide.1.16.html#

In particular do you have a user and associated password set for the
Postgres database?

thank you

--
Adrian Klaver
adrian.klaver@aklaver.com

--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

hi
sir
as per above discussion same error repeated even mentioned ip address of
hostname

./runMTK.sh -sourcedbtype sqlserver -targetSchema public -schemaOnly
-allTables dbo

TARGET_DB_URL=jdbc:postgresql://192.168.168.201:5432/raghu
TARGET_DB_USER=postgres
TARGET_DB_PASSWORD=*****

Connecting with source SQL Server database server...
Connected to Microsoft SQL Server, version '10.50.1600'
Connecting with target EnterpriseDB database server...
MTK-10045: The URL specified for the "target" database is invalid.
Check the connectivity credentials.
Stack Trace:
com.edb.MTKException: MTK-10045: The URL specified for the "target"
database is invalid.
Check the connectivity credentials.

On Thu, Jun 16, 2016 at 7:55 PM, David G. Johnston <
david.g.johnston@gmail.com> wrote:

yes sir

as per above discussion..i already looked pdf postgres plus guide you
mentioned

as well as i already set password for postgres user associated with
postgres db

On Thu, Jun 16, 2016 at 8:30 PM, Durgamahesh Manne <
maheshpostgres9@gmail.com> wrote:

Please don't top-post.

On Thursday, June 16, 2016 8:30:53 PM EDT Durgamahesh Manne wrote:

hi
sir
as per above discussion same error repeated even mentioned ip address of
hostname

./runMTK.sh -sourcedbtype sqlserver -targetSchema public -schemaOnly
-allTables dbo

TARGET_DB_URL=jdbc:postgresql://192.168.168.201:5432/raghu
TARGET_DB_USER=postgres
TARGET_DB_PASSWORD=*****

Connecting with source SQL Server database server...
Connected to Microsoft SQL Server, version '10.50.1600'
Connecting with target EnterpriseDB database server...
MTK-10045: The URL specified for the "target" database is invalid.
Check the connectivity credentials.
Stack Trace:
com.edb.MTKException: MTK-10045: The URL specified for the "target"
database is invalid.
Check the connectivity credentials.

So have you tried the connectivity details? What does

$ psql --host 192.168.168.201 --user postgres -d raghu

give you?

I have a sneaking suspicion you don't have TCP/IP access to the database
configured in pg_hba.conf.

--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

On 2016-06-16 11:13 AM, Durgamahesh Manne wrote:

yes sir

as per above discussion..i already looked pdf postgres plus guide you
mentioned

as well as i already set password for postgres user associated with
postgres db

On Thu, Jun 16, 2016 at 8:30 PM, Durgamahesh Manne
<maheshpostgres9@gmail.com <mailto:maheshpostgres9@gmail.com>> wrote:

hi
sir
as per above discussion same error repeated even mentioned ip
address of hostname

./runMTK.sh -sourcedbtype sqlserver -targetSchema public -schemaOnly
-allTables dbo

TARGET_DB_URL=jdbc:postgresql://192.168.168.201:5432/raghu
<http://192.168.168.201:5432/raghu&gt;
TARGET_DB_USER=postgres
TARGET_DB_PASSWORD=*****

Connecting with source SQL Server database server...
Connected to Microsoft SQL Server, version '10.50.1600'
Connecting with target EnterpriseDB database server...
MTK-10045: The URL specified for the "target" database is invalid.
Check the connectivity credentials.
Stack Trace:
com.edb.MTKException: MTK-10045: The URL specified for the "target"
database is invalid.
Check the connectivity credentials.

On Thu, Jun 16, 2016 at 7:55 PM, David G. Johnston
<david.g.johnston@gmail.com <mailto:david.g.johnston@gmail.com>> wrote:

On Thu, Jun 16, 2016 at 10:19 AM, Durgamahesh Manne
<maheshpostgres9@gmail.com <mailto:maheshpostgres9@gmail.com>>wrote:

sir

PostgreSQL always no1 in world
as per above discussion

migration not working from sql to postgreSQL with runmtk.sh

Connecting with source SQL Server database server...
Connected to Microsoft SQL Server, version '10.50.1600'
Connecting with target EnterpriseDB database server...
MTK-10045: The URL specified for the "target" database is
invalid.
Check the connectivity credentials.
Stack Trace:
com.edb.MTKException: MTK-10045: The URL specified for the
"target" database is invalid.
Check the connectivity credentials.

same error repeated even there mentioned correct credentials
as here i checked multiple times

​Maybe you should try using an IP address instead of a host name.

David J.​

I've never used this tool so like everyone else I am guessing here but
having quickly looked at the documentation have you tried specifying the
'-targetdbtype postgres' in addition to the '-sourcedbtype sqlserver'
that you have already specified?

Neil A

--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

as per above conversation. i checked connectivity details as it is
connected to database (even hostname i mentioned connected to database)
psql --host 192.168.168.201 --user postgres -d raghu
Password for user postgres:
psql.bin (9.4.8, server 9.4.4)
Type "help" for help.

No entry for terminal type "xterm";
using dumb terminal settings.
raghu=#

On Thu, Jun 16, 2016 at 8:51 PM, Jan de Visser <jan@de-visser.net> wrote: