>Or the ODBC-ODBC Bridge from EasySoft.
I have about three weeks experience with the ODBC-ODBC bridge, and it works
well and seemed to work pretty simply. It's what I used when converting
Rob's DB/2 driver into the new odbc driver.
If I recall correctly, that would give you the possibilities of:
Windows: AOLserver speaking ODBC to Windows ODBC Manager to SQL Server
or
Linux: AOLserver speaking ODBC to Linux: Easy Soft Bridge to Windows: SQL
Server
or even
Linux: AOLserver speaking ODBC to Windows: Easy Soft Bridge to Windows: SQL
Server
Unfortunately within an AOLserver application, your choice of db and db
driver can impact what your code looks like. The advantage of any of the
above is that you will only have to debug/experience one db driver within
AOLserver, regardless of which platform you run AOLserver on.
A client of mine found that AOLserver connecting to SQL Server didn't have
the performance they desired. And I believe that others have described
experiences where AOLserver on Windows just didn't have the punch of
AOLserver on *nix.
If Linux is a possibility in the future, you may wish to consider using it
now or benchmarking it. Also, another choice you may wish to look into now
if Linux is a future migration path is using Postgres instead of SQL
Server. Postgres runs on both Linux and Windows, and that will also give
you more options when it comes to migrating webserver or db from one
platform to another. You'll be able to do all sorts of stuff without
having to worry about changing dbs, or changing your applications. I can't
comment on which is faster for your needs: postgres or sql server.
Jerry
=====================================================
Jerry Asher [EMAIL PROTECTED]
1678 Shattuck Avenue Suite 161 Tel: (510) 549-2980
Berkeley, CA 94709 Fax: (877) 311-8688
