Re: VB CGI query of MySQL... best method?

From: Me <no-address_for_spammers_at_no-address.com>
Date: Fri, 08 Apr 2005 20:10:26 -0400
Message-ID: <d376hk$6sbb$1_at_news3.infoave.net>


kevincar wrote:

> I don't think CGI is exactly the term normally used if you are
> using VB and IIS, but I don't know;

Yes, as far as I know it would be considered CGI. The CGI routines are handled by a module called "CGI4VB" written by Kevin O'Brien. I actually emailed him and thanked him for his excellent work.

> as you didn't specify what
> web server you're using and I'm a Perl/Apache guy.

It's IIS 5.

> Just curious; Do you use ASP pages? I ask because that might
> serve you better than calling a VB program to satisfy a lot of
> hits.... You also have to tell us how many hits per day you
> are anticipating... makes a BIG difference in your architecture..
> if you are winding up for a couple thousand hits per hour you
> might want to look at C# or ASP pages.

I know of a company that has a website with a very similar database. It's about the same size with many of the same products. They use ASP, I use a compiled exe CGI called in a conventional manner. Mine is *literally* ten times faster. Mine will return in less than a second what theirs routinely takes 13 seconds to return. THAT'S why I'd prefer to stick to the compiled exe CGI. I've had customers mention the notable speed difference. I just hope I don't kill the speed too much by moving the DB to another server on the LAN that the webserver is connected to. If it does I'll duplicate the DB on both servers and have the LAN server update the DB on the web server.

> I don't think you'll have any problem if you access your new
> database via a named ODBC user/system connection... depending
> upon what you ultimately end up using you can even specify
> connection pooling to speed up the startup.
>
> Why not use SQL server? You can run pretty much any kind
> of business on it and it'l make your application migration
> from Access virtually seamless.

I've been seriously considering just that. MySQL has it's advantages, but the advantages of SQL Server seem to be the better option in this case.

I really appreciate your input. :-) Received on Sat Apr 09 2005 - 02:10:26 CEST

Original text of this message