dbTalk Databases Forums  

Solaris to D3 using ODBC

comp.databases.pick comp.databases.pick


Discuss Solaris to D3 using ODBC in the comp.databases.pick forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
rixx2112@yahoo.com
 
Posts: n/a

Default Solaris to D3 using ODBC - 03-19-2007 , 09:34 AM






Has anyone used a Solaris machine (as a SQL Client) to talk a D3
database using ODBC, and how well does it run?

I have run some continuity tests using a Windows PC as a Client with
success, but really need to know how it runs using Solaris as the
Client end.

Thanks in Advance,
Richard M.


Reply With Quote
  #2  
Old   
Tony Gravagno
 
Posts: n/a

Default Re: Solaris to D3 using ODBC - 03-19-2007 , 12:27 PM






You can't do direct ODBC from a *nix client to D3 because Raining Data
does not provide a *nix-based driver. You will need either a bridge
(ODBC or JDBC/ODBC) or you may want to check with FusionWare to see if
they can help:
http://fusionware.net/products/etools/index.html
(Tell um Tony sent ya!)

I don't know what tools you're using but you could also use
Mono/ADO.NET on Solaris and interface with mv.NET in a middle-tier
Windows box so that you can get data without flattening your schemas
for ODBC. I can help with that one. Along the same lines, you could
make any sort of query of a middle-tier box which returns delimited or
XML data, and then parse it on the Solaris side - this is completely
language and protocol independent.

If you already have FlashCONNECT you can make an HTTP query and return
XML data. FC has a Java API too, if you prefer.

If you really must generate an SQL query, consider wrapping the query
as a text message, then pass it to a Windows middle-tier which makes
the request of D3 and returns a dataset. Now forward this dataset
back to your Solaris client code in some acceptable format (that could
be a trick depending on needs). All of this might be done with a Web
Service (making this a completely client-independent solution). No
for-fee third-party components would be required here.

Please let us know what you do here. There are many possibilities for
indirect solutions. It would be nice to know what actually works, and
works the best.

Good luck. Assistance offered on request.
TG@ removethisNebula-RnD.com

Richard wrote:
Quote:
Has anyone used a Solaris machine (as a SQL Client) to talk a D3
database using ODBC, and how well does it run?

I have run some continuity tests using a Windows PC as a Client with
success, but really need to know how it runs using Solaris as the
Client end.

Thanks in Advance,
Richard M.


Reply With Quote
  #3  
Old   
Symeon
 
Posts: n/a

Default Re: Solaris to D3 using ODBC - 03-19-2007 , 02:04 PM



On Mar 19, 6:27 pm, Tony Gravagno
<address.is.in.po... (AT) removethis (DOT) com.invalid> wrote:
Quote:
You can't do direct ODBC from a *nix client to D3 because Raining Data
does not provide a *nix-based driver. You will need either a bridge
(ODBC or JDBC/ODBC) or you may want to check with FusionWare to see if
they can help:http://fusionware.net/products/etools/index.html
I have used an ODBC bridge before for a U2 odbc connection and it
worked well - i used http://www.easysoft.com/products/dat...dge/index.html




Reply With Quote
  #4  
Old   
rixx2112@yahoo.com
 
Posts: n/a

Default Re: Solaris to D3 using ODBC - 03-20-2007 , 07:56 AM



On Mar 19, 11:27 am, Tony Gravagno
<address.is.in.po... (AT) removethis (DOT) com.invalid> wrote:
Quote:
You can't do direct ODBC from a *nix client to D3 because Raining Data
does not provide a *nix-based driver. You will need either a bridge
(ODBC or JDBC/ODBC) or you may want to check with FusionWare to see if
they can help:http://fusionware.net/products/etools/index.html
(Tell um Tony sent ya!)

I don't know what tools you're using but you could also use
Mono/ADO.NET on Solaris and interface with mv.NET in a middle-tier
Windows box so that you can get data without flattening your schemas
for ODBC. I can help with that one. Along the same lines, you could
make any sort of query of a middle-tier box which returns delimited or
XML data, and then parse it on the Solaris side - this is completely
language and protocol independent.

If you already have FlashCONNECT you can make an HTTP query and return
XML data. FC has a Java API too, if you prefer.

If you really must generate an SQL query, consider wrapping the query
as a text message, then pass it to a Windows middle-tier which makes
the request of D3 and returns a dataset. Now forward this dataset
back to your Solaris client code in some acceptable format (that could
be a trick depending on needs). All of this might be done with a Web
Service (making this a completely client-independent solution). No
for-fee third-party components would be required here.

Please let us know what you do here. There are many possibilities for
indirect solutions. It would be nice to know what actually works, and
works the best.

Good luck. Assistance offered on request.
TG@ removethisNebula-RnD.com


Ideally we'd have preferred a direct connection, but since there's no
ODBC driver available for Solaris that's out
of the question - of course that would also have been way too easy.

Regarding the setup we're aiming for, we'd be making SQL requests from
the Solaris box to the Pick machine to retrieve single records
on demand.
It sounds like we have some options available which is good to know.



Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.