Re: Detached datasets and DRDA compliance

> Microsoft will need to use the client CPU cycles as
> part of the database access mechanism,.  That's
about
> as non-scalable as I can imagine, and a neat way to
> lock clients into the servers.

Good observation, Joe.  Distributing database I/O to
clients is a programming trick, popularized during the
client-server heyday to improve read-only performance,
and may give an illusion of direct database
connectivity, but is not a requirement of MS SQL
Server, and has nothing to do with the fact that
Microsoft doesn't support DRDA clients like OS/400.

Market pressure led IBM to support Microsoft's ODBC
interface, and market pressure would probably be the
only thing that would lead Microsoft to reciprocate
and support IBM's DRDA interface.

At this point, I suspect that IBM would be more likely
to bend, and add a native ODBC interface so that ILE
programs could run statements like:

Select * from customer@MSSQLSVR ...

to query MS SQL Server, or any other ODBC compliant
database, and return a result set to OS/400.

Perhaps neither IBM nor Microsoft will bend on the
issue.  As pointed out in earlier discussions, Java
already supports ODBC standards, so a lot of people at
IBM might question the value adding an ILE ODBC
interface.

BTW, I appreciated your response to Trevor Perry.  It
seems that the iSeries Network has been drawn away
from its traditional moorings lately, forming
alliances with sponsors having strong ties to
Microsoft, which doesn't sit well with me either.

Nathan Andelin



                
__________________________________ 
Discover Yahoo! 
Find restaurants, movies, travel and more fun for the weekend. Check it out! 
http://discover.yahoo.com/weekend.html