PostgreSQL Linked Server on SQL Server 2005 64-bit

PostgreSQL Linked Server on SQL Server 2005 64-bit

am 26.04.2008 03:02:19 von Paragon Corporation

Sorry for the cross-post here. I think the issue of being able to connect
to PostgreSQL from a 64-bit Windows system and in particular 64-bit SQL
Server 2005 has come up a couple of times on both PostGIS and PostgreSQL
ODBC groups. Jeff Crumbley kindly notified us that Microsoft released this
month a 64-bit OLEDB for ODBC driver which now makes connecting from a 64-it
SQL Server install via a Linked Server configuration possible. We thank him
greatly for that and have our linked servers working now.

We have posted the steps we took to achieve this on an Intel 64-bit SQL
Server 2005 install. So far seems to work well for us. We hope this
information is valuable to others.

http://www.postgresonline.com/journal/index.php?/archives/46 -Setting-up-Post
greSQL-as-a-Linked-Server-in-Microsoft-SQL-Server-64-bit.htm l

Thanks,
Leo and Regina

Re: PostgreSQL Linked Server on SQL Server 2005 64-bit

am 26.04.2008 07:00:16 von Konstantin Izmailov

--===============1467735819==
Content-Type: multipart/alternative;
boundary="----=_Part_201_4078512.1209186016112"

------=_Part_201_4078512.1209186016112
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

I have doubt about performance and scalability of this approach. Correct me
if I'm wrong but native PostgreSQL OLE DB Provider would have done work more
efficiently (see http://www.postgresql.org/about/news.895 - version 1.2.8
supports Linked Servers).

On Fri, Apr 25, 2008 at 6:02 PM, Paragon Corporation <
lr@paragoncorporation.com> wrote:

>
> Sorry for the cross-post here. I think the issue of being able to connect
> to PostgreSQL from a 64-bit Windows system and in particular 64-bit SQL
> Server 2005 has come up a couple of times on both PostGIS and PostgreSQL
> ODBC groups. Jeff Crumbley kindly notified us that Microsoft released
> this
> month a 64-bit OLEDB for ODBC driver which now makes connecting from a
> 64-it
> SQL Server install via a Linked Server configuration possible. We thank
> him
> greatly for that and have our linked servers working now.
>
> We have posted the steps we took to achieve this on an Intel 64-bit SQL
> Server 2005 install. So far seems to work well for us. We hope this
> information is valuable to others.
>
>
> http://www.postgresonline.com/journal/index.php?/archives/46 -Setting-up-Post
> greSQL-as-a-Linked-Server-in-Microsoft-SQL-Server-64-bit.htm l
>
> Thanks,
> Leo and Regina
>
>
> _______________________________________________
> postgis-users mailing list
> postgis-users@postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-user s
>

------=_Part_201_4078512.1209186016112
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

I have doubt about performance and scalability of this approach. Correct me if I'm wrong but native PostgreSQL OLE DB Provider would have done work more efficiently (see  - version 1.2.8 supports Linked Servers).



On Fri, Apr 25, 2008 at 6:02 PM, Paragon Corporation <> wrote:


Sorry for the cross-post here.  I think the issue of being able to connect
to PostgreSQL from a 64-bit Windows system and in particular 64-bit SQL

Server 2005 has come up a couple of times on both PostGIS and PostgreSQL
ODBC groups.  Jeff Crumbley kindly notified us that Microsoft released this
month a 64-bit OLEDB for ODBC driver which now makes connecting from a 64-it

SQL Server install via a Linked Server configuration possible.  We thank him
greatly for that and have our linked servers working now.

We have posted the steps we took to achieve this on an Intel 64-bit SQL
Server 2005 install.  So far seems to work well for us.  We hope this

information is valuable to others.

http://www.postgresonline.com/journal/index.php?/archives/46 -Setting-up-Post

greSQL-as-a-Linked-Server-in-Microsoft-SQL-Server-64-bit.htm l


Thanks,
Leo and Regina


_______________________________________________
postgis-users mailing list






------=_Part_201_4078512.1209186016112--

--===============1467735819==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
postgis-users mailing list
postgis-users@postgis.refractions.net
http://postgis.refractions.net/mailman/listinfo/postgis-user s

--===============1467735819==--

RE: PostgreSQL Linked Server on SQL Server 2005 64-bit

am 26.04.2008 10:30:42 von Paragon Corporation

This is a multi-part message in MIME format.

--===============1271532918==
Content-Type: multipart/alternative;
boundary="----=_NextPart_000_000B_01C8A756.4A0B74F0"

This is a multi-part message in MIME format.

------=_NextPart_000_000B_01C8A756.4A0B74F0
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit

Konstantin,

We'll have to take a look at that. I always thought that the PostgreSQL OLE
DB provider was less tested and robust than the ODBC one, but I have to
admit its been a while since we have looked at it. Last I tried it which
was awhile ago, I couldn't get it to go in a linked server configuration or
for SSIS processing. Things have probably changed as you mention.

I'll have to revisit this.

Thanks for the suggestion.

Regina

_____

From: postgis-users-bounces@postgis.refractions.net
[mailto:postgis-users-bounces@postgis.refractions.net] On Behalf Of
Konstantin Izmailov
Sent: Saturday, April 26, 2008 1:00 AM
To: PostGIS Users Discussion
Cc: pgsql-odbc@postgresql.org
Subject: Re: [postgis-users] PostgreSQL Linked Server on SQL Server 2005
64-bit


I have doubt about performance and scalability of this approach. Correct me
if I'm wrong but native PostgreSQL OLE DB Provider would have done work more
efficiently (see http://www.postgresql.org/about/news.895 - version 1.2.8
supports Linked Servers).


On Fri, Apr 25, 2008 at 6:02 PM, Paragon Corporation
wrote:



Sorry for the cross-post here. I think the issue of being able to connect
to PostgreSQL from a 64-bit Windows system and in particular 64-bit SQL
Server 2005 has come up a couple of times on both PostGIS and PostgreSQL
ODBC groups. Jeff Crumbley kindly notified us that Microsoft released this
month a 64-bit OLEDB for ODBC driver which now makes connecting from a 64-it
SQL Server install via a Linked Server configuration possible. We thank him
greatly for that and have our linked servers working now.

We have posted the steps we took to achieve this on an Intel 64-bit SQL
Server 2005 install. So far seems to work well for us. We hope this
information is valuable to others.

http://www.postgresonline.com/journal/index.php?/archives/46 -Setting-up-Post
tgreSQL-as-a-Linked-Server-in-Microsoft-SQL-Server-64-bit.ht ml>
greSQL-as-a-Linked-Server-in-Microsoft-SQL-Server-64-bit.htm l

Thanks,
Leo and Regina


_______________________________________________
postgis-users mailing list
postgis-users@postgis.refractions.net
http://postgis.refractions.net/mailman/listinfo/postgis-user s




------=_NextPart_000_000B_01C8A756.4A0B74F0
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable



charset=3Dus-ascii">


face=3DArial=20
color=3D#0000ff size=3D2>Konstantin,

face=3DArial=20
color=3D#0000ff size=3D2>
 

face=3DArial=20
color=3D#0000ff size=3D2>We'll have to take a look at that.  I =
always thought=20
that the PostgreSQL OLE DB provider was less tested and robust than the =
ODBC=20
one, but I have to admit its been a while since we have looked at=20
it.   Last I tried it which was awhile ago, I couldn't =
get it to=20
go in a linked server configuration or for SSIS processing.   =
Things=20
have probably changed as you mention.

face=3DArial=20
color=3D#0000ff size=3D2>
 

face=3DArial=20
color=3D#0000ff size=3D2>I'll have to revisit this.

face=3DArial=20
color=3D#0000ff size=3D2>
 

face=3DArial=20
color=3D#0000ff size=3D2>Thanks for the suggestion.

face=3DArial=20
color=3D#0000ff size=3D2>
 

face=3DArial=20
color=3D#0000ff size=3D2>Regina





From:=20
postgis-users-bounces@postgis.refractions.net=20
[mailto:postgis-users-bounces@postgis.refractions.net] On Behalf Of=20
Konstantin Izmailov
Sent: Saturday, April 26, 2008 1:00=20
AM
To: PostGIS Users Discussion
Cc:=20
pgsql-odbc@postgresql.org
Subject: Re: [postgis-users] =
PostgreSQL=20
Linked Server on SQL Server 2005 64-bit


I have doubt about performance and scalability of this =
approach.=20
Correct me if I'm wrong but native PostgreSQL OLE DB Provider would have =
done=20
work more efficiently (see href=3D"http://www.postgresql.org/about/news.895">http://www .postgresql.o=
rg/about/news.895 -=20
version 1.2.8 supports Linked Servers).


On Fri, Apr 25, 2008 at 6:02 PM, Paragon =
Corporation=20
< href=3D"mailto:lr@paragoncorporation.com">lr@paragoncorporat ion.com&g=
t;=20
wrote:

style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc =
1px solid">
Sorry=20
for the cross-post here.  I think the issue of being able to=20
connect
to PostgreSQL from a 64-bit Windows system and in =
particular 64-bit=20
SQL
Server 2005 has come up a couple of times on both PostGIS and=20
PostgreSQL
ODBC groups.  Jeff Crumbley kindly notified us that =

Microsoft released this
month a 64-bit OLEDB for ODBC driver which =
now=20
makes connecting from a 64-it
SQL Server install via a Linked =
Server=20
configuration possible.  We thank him
greatly for that and =
have our=20
linked servers working now.

We have posted the steps we took to =
achieve=20
this on an Intel 64-bit SQL
Server 2005 install.  So far seems =
to work=20
well for us.  We hope this
information is valuable to=20
others.

=
href=3D"http://www.postgresonline.com/journal/index.php?/arc hives/46-Sett=
ing-up-PostgreSQL-as-a-Linked-Server-in-Microsoft-SQL-Server -64-bit.html"=
=20
=
target=3D_blank>http://www.postgresonline.com/journal/index. php?/archives=
/46-Setting-up-Post
greSQL-as-a-Linked-Server-in-Microsoft-SQL-Server-=
64-bit.html

Thanks,
Leo=20
and=20
=
Regina


_______________________________________________
post=
gis-users=20
mailing list
=
href=3D"mailto:postgis-users@postgis.refractions.net">postgi s-users@postg=
is.refractions.net
href=3D"http://postgis.refractions.net/mailman/listinfo/post gis-users" =

=
target=3D_blank>http://postgis.refractions.net/mailman/listi nfo/postgis-u=
sers



------=_NextPart_000_000B_01C8A756.4A0B74F0--



--===============1271532918==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
postgis-users mailing list
postgis-users@postgis.refractions.net
http://postgis.refractions.net/mailman/listinfo/postgis-user s

--===============1271532918==--

RE: PostgreSQL Linked Server on SQL Server 2005 64-bit

am 26.04.2008 10:39:45 von Paragon Corporation

This is a multi-part message in MIME format.

--===============0983257531==
Content-Type: multipart/alternative;
boundary="----=_NextPart_000_001C_01C8A757.8DB2AE70"

This is a multi-part message in MIME format.

------=_NextPart_000_001C_01C8A757.8DB2AE70
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit

On further inspection I see the one you are pointing at is a commercial
implementation of the PostgreSQL OLE DB Provider and not the one packaged
with PostgreSQL source and binaries. We haven't tried that one at all so
can't vouch for its strength compared to using ODBC over the OLEDB Provider
for ODBC.

A really robust solution I would suspect would be a Native SQL Server .NET
provider for PostgreSQL, but I haven't figured out how all that works to see
if the NpgSQL.NET driver can be fashioned as such. I think native SQL
Server for Oracle and DB2 providers exist.

Thanks,
Regina


_____

From: postgis-users-bounces@postgis.refractions.net
[mailto:postgis-users-bounces@postgis.refractions.net] On Behalf Of
Konstantin Izmailov
Sent: Saturday, April 26, 2008 1:00 AM
To: PostGIS Users Discussion
Cc: pgsql-odbc@postgresql.org
Subject: Re: [postgis-users] PostgreSQL Linked Server on SQL Server 2005
64-bit


I have doubt about performance and scalability of this approach. Correct me
if I'm wrong but native PostgreSQL OLE DB Provider would have done work more
efficiently (see http://www.postgresql.org/about/news.895 - version 1.2.8
supports Linked Servers).


On Fri, Apr 25, 2008 at 6:02 PM, Paragon Corporation
wrote:



Sorry for the cross-post here. I think the issue of being able to connect
to PostgreSQL from a 64-bit Windows system and in particular 64-bit SQL
Server 2005 has come up a couple of times on both PostGIS and PostgreSQL
ODBC groups. Jeff Crumbley kindly notified us that Microsoft released this
month a 64-bit OLEDB for ODBC driver which now makes connecting from a 64-it
SQL Server install via a Linked Server configuration possible. We thank him
greatly for that and have our linked servers working now.

We have posted the steps we took to achieve this on an Intel 64-bit SQL
Server 2005 install. So far seems to work well for us. We hope this
information is valuable to others.

http://www.postgresonline.com/journal/index.php?/archives/46 -Setting-up-Post
tgreSQL-as-a-Linked-Server-in-Microsoft-SQL-Server-64-bit.ht ml>
greSQL-as-a-Linked-Server-in-Microsoft-SQL-Server-64-bit.htm l

Thanks,
Leo and Regina


_______________________________________________
postgis-users mailing list
postgis-users@postgis.refractions.net
http://postgis.refractions.net/mailman/listinfo/postgis-user s




------=_NextPart_000_001C_01C8A757.8DB2AE70
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable



charset=3Dus-ascii">


size=3D2> class=3D416103208-26042008>On further inspection I see the one you are =
pointing at=20
is a commercial implementation of the PostgreSQL OLE DB Provider =
and  not=20
the one packaged with PostgreSQL source and binaries.  We haven't =
tried=20
that one at all so can't vouch for its strength compared to using ODBC =
over the=20
OLEDB Provider for ODBC.

size=3D2> 

face=3DArial=20
color=3D#0000ff size=3D2>A really robust solution I would suspect would =
be a Native=20
SQL Server .NET provider for PostgreSQL, but I haven't figured out how =
all that=20
works to see if the NpgSQL.NET driver can be fashioned as such.  I=20
think native SQL Server  for Oracle and DB2 providers=20
exist.
color=3D#0000ff size=3D2>

face=3DArial=20
color=3D#0000ff size=3D2>
 

face=3DArial=20
color=3D#0000ff size=3D2>Thanks,

face=3DArial=20
color=3D#0000ff size=3D2>Regina

size=3D2> class=3D416103208-26042008> 





From:=20
postgis-users-bounces@postgis.refractions.net=20
[mailto:postgis-users-bounces@postgis.refractions.net] On Behalf Of=20
Konstantin Izmailov
Sent: Saturday, April 26, 2008 1:00=20
AM
To: PostGIS Users Discussion
Cc:=20
pgsql-odbc@postgresql.org
Subject: Re: [postgis-users] =
PostgreSQL=20
Linked Server on SQL Server 2005 64-bit


I have doubt about performance and scalability of this =
approach.=20
Correct me if I'm wrong but native PostgreSQL OLE DB Provider would have =
done=20
work more efficiently (see href=3D"http://www.postgresql.org/about/news.895">http://www .postgresql.o=
rg/about/news.895 -=20
version 1.2.8 supports Linked Servers).


On Fri, Apr 25, 2008 at 6:02 PM, Paragon =
Corporation=20
< href=3D"mailto:lr@paragoncorporation.com">lr@paragoncorporat ion.com&g=
t;=20
wrote:

style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc =
1px solid">
Sorry=20
for the cross-post here.  I think the issue of being able to=20
connect
to PostgreSQL from a 64-bit Windows system and in =
particular 64-bit=20
SQL
Server 2005 has come up a couple of times on both PostGIS and=20
PostgreSQL
ODBC groups.  Jeff Crumbley kindly notified us that =

Microsoft released this
month a 64-bit OLEDB for ODBC driver which =
now=20
makes connecting from a 64-it
SQL Server install via a Linked =
Server=20
configuration possible.  We thank him
greatly for that and =
have our=20
linked servers working now.

We have posted the steps we took to =
achieve=20
this on an Intel 64-bit SQL
Server 2005 install.  So far seems =
to work=20
well for us.  We hope this
information is valuable to=20
others.

=
href=3D"http://www.postgresonline.com/journal/index.php?/arc hives/46-Sett=
ing-up-PostgreSQL-as-a-Linked-Server-in-Microsoft-SQL-Server -64-bit.html"=
=20
=
target=3D_blank>http://www.postgresonline.com/journal/index. php?/archives=
/46-Setting-up-Post
greSQL-as-a-Linked-Server-in-Microsoft-SQL-Server-=
64-bit.html

Thanks,
Leo=20
and=20
=
Regina


_______________________________________________
post=
gis-users=20
mailing list
=
href=3D"mailto:postgis-users@postgis.refractions.net">postgi s-users@postg=
is.refractions.net
href=3D"http://postgis.refractions.net/mailman/listinfo/post gis-users" =

=
target=3D_blank>http://postgis.refractions.net/mailman/listi nfo/postgis-u=
sers



------=_NextPart_000_001C_01C8A757.8DB2AE70--



--===============0983257531==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
postgis-users mailing list
postgis-users@postgis.refractions.net
http://postgis.refractions.net/mailman/listinfo/postgis-user s

--===============0983257531==--