Thomas, It is more fundamental than our personal stability problems with ODBC driver. OLEDB has been the newer standard for Windows drivers for many years and SAP never bothered. Now dotNet is over 18 months shipping and still no interest in a driver.
It isn't just my personal interest, I fear that SAPDB / MaxDB seems to continue to ignore a huge target - taking on Windows Server users. SAPDB has equal kernel support for Windows and Unix platforms. SAPDB could be an ideal product for people migrating from Oracle or SQL Server but still wanting to stay on Windows Server for the OS (it is not uncommon to have a company who is willing to switch DB's but not willing to switch OS until solution proven). It is for the same reason that I am hopeful SAPDB will have a FreeBSD port. Most _clients_ are Windows... and SAPDB has done the most to neglect the drivers on that platform. dotNet is the Microsoft modern architecture (their Java clone). I came up with the $5000 figure not because we profit form SAPDB. We do not resell it. If we did, the forthcoming mySQL license changes would be more a hot issue with me. $5000 is pretty much the _lease expensive_ option for a commercial database that supports unlimited users in a web site (DB2, SQL Anywhere Studio, Microsoft SQL Server 2000, Oracle even more $). And even that, it is US$5000.00 per processor. >From my perspective, PostgreSQL is the major free competitor to SAPDB / MaxDB. Alas, they have neglected the Win32 server platform (which they are addressing a native port (not cygwin) in 7.4). SAPDB is ahead of PostgreSQL in the native win32 port. But SAPDB is behind PostgreSQL in FreeBSD/*BSD support + _way behind_ in driver support. PostgreSQL: ODBC + OleDB + dotNet drivers Firebird & Interbase: ODBC + OleDB + dotNet drivers MySQL: ODBC + OleDB + dotNet drivers (multiple choices for dotNet drivers) SAPDB: ODBC only Thomas: You acknowledged on Tue 9/24/2002 the socket problems in the SAPDB Win32 ODBC driver under high concurrency. You DID reproduce that problem. Stephen Gutknecht -----Original Message----- From: Koetter, Thomas Theodor [mailto:[EMAIL PROTECTED] Sent: Friday, August 08, 2003 1:13 AM To: 'Stephen Gutknecht (SAPDB)'; [EMAIL PROTECTED] Subject: RE: Perl fork question - SAPDB communications layer written for l onger running sessions Hi Stephen > -----Original Message----- > From: Stephen Gutknecht (SAPDB) [mailto:[EMAIL PROTECTED] > Sent: Donnerstag, 7. August 2003 22:19 > To: Dittmar, Daniel; '[EMAIL PROTECTED]'; > [EMAIL PROTECTED] > Subject: RE: Perl fork question - SAPDB communications layer > written for > l onger running sessions > Importance: High > > > I would add that our testing has shown what Daniel says to be > true. Using > Perl on Linux or using dotNet on Windows we find SAPDB to be > one of the most > unreliable and poor performing database systems :) I know that you have problems at your site with ODBC. However, the problem does not seem to be easily reproducable since you never send me some standalone code to reproduce it in my environment. All what you reported (into the list and directly to me) let me think that the reason for that is the driver. And I can assure you that I investigated a considerable amount of time to find the cause for that. Until now the problem apparently remains, what I regret. But without being able to reproduce problems, it's not so easy to find solutions. I can understand that you might be somewhat frustrated but I hope you exaggerated a little bit. > P.S. to list: Would US$5000 be enough to fund someone to > develop a native > and stable Windows dotNet driver for SAPDB in c#? There are > already ones > for MySql / Postgresql. Plus the SAPDB java driver should > prove a good > place to learn the driver-protocol from... It's good to see that some business is growing around our DB :-) Regards Thomas ---------------------------------------------- Dr. Thomas K�tter SAP DB, SAP Labs Berlin Hurry up, SAP DB is open source www.sapdb.org _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
