RE: [PHP-DB] PHP -> MS SQL (warning, RANT)

From: Date: Fri, 14 Jul 2000 12:56:02 +0000
Subject: RE: [PHP-DB] PHP -> MS SQL (warning, RANT)
References: 1  Groups: php.db 
Request: Send a blank email to php-db+get-1147@lists.php.net to get a copy of this message
Yup, JDBC as well as ODBC driver are available. Best regards, Andrew ---------------------------------------------------- Andrew Hill Professional Services Consultant OpenLink Software http://www.openlinksw.com Universal Database Connectivity Technology Providers -----Original Message----- From: Vincent Apesa [mailto:vapesa@hotmail.com] Sent: Thursday, July 13, 2000 5:37 PM To: ahill@openlinksw.com Subject: Re: [PHP-DB] PHP -> MS SQL (warning, RANT) Andrew, Another point probably less worthy of noting... I used to work for Lockheed Martin on an R&D project. I think I spoke to you before about purchasing drivers for use with Java... I remember your name. Is this at all possible? Vince ----- Original Message ----- From: Andrew Hill <ahill@openlinksw.com> To: Vincent Apesa <vapesa@hotmail.com>; <php-db@lists.php.net> Sent: Thursday, July 13, 2000 4:54 PM Subject: RE: [PHP-DB] PHP -> MS SQL (warning, RANT) > Oh dear, if I'm not careful the nickname will stick. > > Regarding scalability, we are an exceptionally scalable, thread-safe, and > tightly coded implementation of the ODBC API spec, delivering an > architecture that bypasses the native layer and speaking directly to the > Call Level Interface (CLI) of the specific database. Our version 4.0 > drivers will take that even further, and be Multi-threaded at all levels > (Currently, 3.2 drivers are multi-threaded in the client libraries and > request broker, but require additional agent processes to be spawned, or > serialized - this usually isn't a problem unless you are running a really > low resource db server, but we're eliminating the possibility of a problem > there by delivering full multi-threading across all ODBC and JDBC > components). > > We have many (5000+) companies using our drivers in production environments > including, high volume websites, ERP, and data integration systems. > > You do not need to go down to native drivers to support things like > transactions either - we actually provide a great deal more functionality > than native drivers, as we have fully implemented the ODBC 3.5 API spec as > of version 4.0 (3.2 drivers support ODBC 3.5, but do some function mapping). > This translates to a rather odd benefit - you can actually enforce > additional functionality against your database by using our drivers. Things > like additional cursor models are one example. > > In addition, we typically outperform native drivers by a nice margin, and > absolutely smoke some. > > We are also releasing a benchmarking tool (open source) when we release our > 4.0 drivers, called GTKBench. This allows you to horserace any combination > of drivers and databases in real time, and in _your_environment_ so you can > see actual benefits instead of reading published benchmarks. You get the > ability to simulate TPC-A and TPC-C benchmarks, and the code is open (and > GPL) so you can extend it as you wish (plus you will see that it's honest > when reporting just how much faster we are =) > > In addition, you get template-based session rules, to add a highly > configurable level of security, and not rely on the app or db level to take > care of it. Not that anyone here has done it, but gotta love production > Oracle servers with scott/tiger logins. > > ODBC has many many more benefits than people often realize, since their only > experience is with db vendor built odbc drivers or Microsoft drivers. There > has been quite a bit of talk on this list about database abstraction layers > in the programmatic sense. ODBC is the natural compliment to that and may > pleasantly surprise you. > > Anyhow, there is my rant (warned you, didn't I?) I'd be happy to follow up > with anyone on or off the list. > > Best regards, > Andrew > ---------------------------------------------------- > Andrew Hill > Professional Services Consultant > OpenLink Software > http://www.openlinksw.com > Universal Database Connectivity Technology Providers > > > -----Original Message----- > From: Vincent Apesa [mailto:vapesa@hotmail.com] > Sent: Thursday, July 13, 2000 4:32 PM > To: "Andrew Hill" > Subject: Re: [PHP-DB] PHP -> MS SQL > > > Andrew (Mr Openlink), > What is the scalability of your software drivers? We would like to > deploy Linux/Apache website that will take a good amount of hits. Ideally we > would have to move to the native drivers to support things like transactions > .. correct? Your feedback would be appreciated. > > cheers, > Vince > > ----- Original Message ----- > From: "Andrew Hill" <ahill@openlinksw.com> > Newsgroups: php.db > Sent: Thursday, July 13, 2000 3:21 PM > Subject: RE: [PHP-DB] PHP -> MS SQL > > > > You can use ODBC :) ODBC is not slow if implemented properly - most > people > > only know Microsoft's implementation. > > Openlink's ODBC drivers are typically faster (sometimes MUCH faster) than > > native driver. > > You want to look at the Multi-Tier Drivers. > > > > > > More info is available at http://www.openlinksw.com > > > > Best regards, > > Andrew > > ---------------------------------------------------- > > Andrew Hill > > Professional Services Consultant > > OpenLink Software > > http://www.openlinksw.com > > Universal Database Connectivity Technology Providers > > > > -----Original Message----- > > From: Vincent Apesa [mailto:vapesa@hotm@il.com] > > Sent: Thursday, July 13, 2000 3:19 PM > > To: php-db@lists.php.net > > Subject: Re: [PHP-DB] PHP -> MS SQL > > > > > > to bad about PHP4.... > > Well, considering I'm using PHP4 are there any other solutions? > > > > thanks, > > Vince > > > > -- > > > > Bryan Mattern <bmattern@buytrek.com> wrote in message > > > > news:9E5AA668748AA6468CA9B3F4E640F29410E7D7@BT02M.buytrek.com... > > > Vince, > > > > > > Take a look at FreeTDS.org. It's *worlds* better, and is much faster > than > > > ODBC for connecting to SQL server. There are a few tricks listed in the > > > FAQ, but the install is easier than the OpenLink install as there is no > > > server side installation. I have had problems with php4, but the 3.0.12 > > > works fine for my purposes. > > > > > > If anyone knows why it's incompatible with php4, I would love to know. > > > > > > --Bryan > > > > > > ************************* > > > Bryan Mattern > > > bryan.mattern@datapace.com > > > www.datapace.com > > > > > > > > > -----Original Message----- > > > From: Vincent Apesa [mailto:vapesa@hotm@il.com] > > > Sent: Thursday, July 13, 2000 9:40 AM > > > To: php-db@lists.php.net > > > Subject: [PHP-DB] PHP -> MS SQL > > > > > > > > > Where can I find some information on how to connect a Linux web server > to > > a > > > MS SQL server? > > > > > > thanks, > > > Vince > > > > > > -- > > > > > > > > > > > > > > > -- > > > PHP Database Mailing List (http://www.php.net/) > > > To unsubscribe, e-mail: php-db-unsubscribe@lists.php.net > > > For additional commands, e-mail: php-db-help@lists.php.net > > > To contact the list administrators, e-mail: php-list-admin@lists.php.net > > > > > > -- > > > PHP Database Mailing List (http://www.php.net/) > > > To unsubscribe, e-mail: php-db-unsubscribe@lists.php.net > > > For additional commands, e-mail: php-db-help@lists.php.net > > > To contact the list administrators, e-mail: php-list-admin@lists.php.net > > > > > > > > > > > -- > > PHP Database Mailing List (http://www.php.net/) > > To unsubscribe, e-mail: php-db-unsubscribe@lists.php.net > > For additional commands, e-mail: php-db-help@lists.php.net > > To contact the list administrators, e-mail: php-list-admin@lists.php.net > > > > > > > > > > -- > > PHP Database Mailing List (http://www.php.net/) > > To unsubscribe, e-mail: php-db-unsubscribe@lists.php.net > > For additional commands, e-mail: php-db-help@lists.php.net > > To contact the list administrators, e-mail: php-list-admin@lists.php.net > > > > >

« previous php.db (#1147) next »