Thread: Problem using ODBC driver from MS SQL DTS package

Problem using ODBC driver from MS SQL DTS package

From
David Stanaway
Date:
Hi there,

I am having problems using the latest version of the driver (Both the
stable and the beta version) from a DTS package on a Win2K server box
with SQL server 2000.

I am trying to pull data from a postgresql 7.2.1 database, and the
problem is that when I try an specify a transformation with the ODBC
connection being the destination, the mmc.exe program starts leaking
memory at about a MB/sec and the application gui freezes.

I am not sure if this is just a bug in the Microsoft program, or if it
is related to using the ODBC driver.

Has anyone else experienced this?


Here is the query from the MS SQL database I am trying to insert into a
postgresql database via DTS

select 'host401' as key, max([identity]) as lastidentity from alldata

and the postgresql query I am trying to pull into a MSSQL database

select * from alldata where "identity" > (select max("identity") from
replicationinfo where key='host401')

I have successfully used this from an xp system with sqlserver 2000 (But
without servicepack3), but have had no luck from a windows2000 system
with servicepack3.

Again, the leak occurs when I click on the transformation tab. So this
would be parsing the query via the ODBC driver I imagine, and trying to
get back tha names/types of the result set that the query would return.


--
David Stanaway
DialMex LLC
NOC Engineer
200 S. 10th Street Suite 1209
McAllen, TX 78501

(956) 994-0014 x111 office
(956) 239-0840 mobile
(956) 682-5821 fax
david@dialmex.net


Re: Problem using ODBC driver from MS SQL DTS package

From
"Wayne Armstrong"
Date:
** Reply to message from David Stanaway <david@dialmex.net> on 28 Apr 2003
16:41:33 -0500
Hi David,
 There seem to be some problems in the odbc driver when parsing statements.
 Depending on other odbc driver settings, if the parse fails, it can just hang
or do other interesting things (in my experience). The parser does seem to have
problems with statements of the form select * from (select * from).
 Try creating a strongly typed view for the second select from and change the
satement to the from of select whatever from viewname ?

Regards,
Wayne

> Hi there,
>
> I am having problems using the latest version of the driver (Both the
> stable and the beta version) from a DTS package on a Win2K server box
> with SQL server 2000.
>
> I am trying to pull data from a postgresql 7.2.1 database, and the
> problem is that when I try an specify a transformation with the ODBC
> connection being the destination, the mmc.exe program starts leaking
> memory at about a MB/sec and the application gui freezes.
>
> I am not sure if this is just a bug in the Microsoft program, or if it
> is related to using the ODBC driver.
>
> Has anyone else experienced this?
>
>
> Here is the query from the MS SQL database I am trying to insert into a
> postgresql database via DTS
>
> select 'host401' as key, max([identity]) as lastidentity from alldata
>
> and the postgresql query I am trying to pull into a MSSQL database
>
> select * from alldata where "identity" > (select max("identity") from
> replicationinfo where key='host401')
>
> I have successfully used this from an xp system with sqlserver 2000 (But
> without servicepack3), but have had no luck from a windows2000 system
> with servicepack3.
>
> Again, the leak occurs when I click on the transformation tab. So this
> would be parsing the query via the ODBC driver I imagine, and trying to
> get back tha names/types of the result set that the query would return.
>
>
> --
> David Stanaway
> DialMex LLC
> NOC Engineer
> 200 S. 10th Street Suite 1209
> McAllen, TX 78501
>
> (956) 994-0014 x111 office
> (956) 239-0840 mobile
> (956) 682-5821 fax
> david@dialmex.net
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly