Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
Database Servers
DB2InformixIngresMS SQLOraclePervasive.SQLPostgreSQLProgressSybase
Desktop Databases
FileMakerFoxProMS AccessParadox
General
General DB TopicsDatabase Theory
Related Topics
Java Development.NET DevelopmentVB DevelopmentMore Topics ...

Database Forum / DB2 Topics / May 2006

Tip: Looking for answers? Try searching our database.

.NET UBB link? (file on web)

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Brian Tkatch - 11 May 2006 21:05 GMT
I'm trying to get more information on connect via .NET to UDB.

On <URL:http://www-128.ibm.com/developerworks/db2/zones/vstudio/> there
is a link "CBT: Fast path to DB2 UDB in a Visual Basic .NET
environment"
<URL:http://www.ibm.com/software/data/education/l1630.html">, yet i see
nothing there about .NET.

We have UDB 8.1.6. and would like to know if we must upgrade to 8.2 to
be able to use .NET to access the database.

B.
Artur - 11 May 2006 22:34 GMT
I think you need only to install latest Application Development Client
8.2.x to get Development Add-In and DB2 provider for .NET (which was
greatly enhanced in 8.2) -- if client in not on the same machine as DB2
server. You can install DB2 ADC directly from the latest fixpak.

If you are accessing DB2 with ODBC or OLE DB providers you don't have
to change anything (slower than DB2 .NET provider).

Personally I would be staying with higher fixpak level. It is always a
tradeoff between well known bugs and unknown bugs. But in case of any
malfunctions you probably will be guided by tech support to higher your
db2 level -- for you this means "forced migration". It easier to plan
it, but anyway going up from 8.1.6 is quite straightforward.

-- Artur Wronski
Brian Tkatch - 12 May 2006 14:04 GMT
>I think you need only to install latest Application Development Client
>8.2.x to get Development Add-In and DB2 provider for .NET (which was
>greatly enhanced in 8.2) -- if client in not on the same machine as DB2
>server.

This is our case. I'm going to try this.

>You can install DB2 ADC directly from the latest fixpak.

I am not sure of the significance of this.

>If you are accessing DB2 with ODBC or OLE DB providers you don't have
>to change anything (slower than DB2 .NET provider).

Curerently, we're using ODBC. But it's noticeably slow. The DB2 client
is much faster when showing data (and minimizing the screen to avoid
printout slowdown). So, as we are moving to .NET and rewritting a bunch
of things, we'd like to get the best solution for the DB connection as
well.

>Personally I would be staying with higher fixpak level. It is always a
>tradeoff between well known bugs and unknown bugs. But in case of any
>malfunctions you probably will be guided by tech support to higher your
>db2 level -- for you this means "forced migration". It easier to plan
>it, but anyway going up from 8.1.6 is quite straightforward.

We have a plan to upgrade soon around the time we do a server migration
which is being planned.  It is a bit more complex to get an upgrade on
the server, which requires an upgrade to the production server as well,
so we'd rather wait for the planned one. Same is true with fixpacks,
but those are obviously easier. Therefore, we're just going to upgrade
the local client for now.

Thanx for the reply. I appreciate it.

B.
Brian Tkatch - 12 May 2006 14:33 GMT
>You can install DB2 ADC directly from the latest fixpak.

Now i see.

<URL:http://www-306.ibm.com/software/data/db2/udb/support/downloadv8_windows32bit.html>
has the link to "DB2 Application Development Client " at:
<URL:ftp://ftp.software.ibm.com/ps/products/db2/fixes2/english-us/db2winIA32v8/fixpak
/FP11_WR21365/FP11_WR21365_ADCL.exe
>

Thanx.

B.
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.