We're planning on launching a new commercial site that is driven by a small (4 tables) database. We're expecting a large number of visitors visiting the site simultaneously. When it comes to handling a lot of concurrent users I know Access isn't the best choice because for example it cannot handle more than 10 open concurrent connections. We're looking for a good, but somehow easy to learn alternative. Can somebody give a good suggestion of what to use? E.g. SQL-server? What are the cons and pro's, and how could Ultradev be of any help? I really would appreciate any help on this one!

Rein

It all depends on what server language you're using. If it's PHP then use My SQL. ASP goes with SQL Server.
In case of SQL Server (I haven't used MY SQL) it's very similar to Access. Few things are with different names (Query = View, Relationships = Diagrams...) but both are using same logic - create tables to store data, diagrams to connect different tables and views to manage those tables.
Is SQL better then Access? Yes it is. SQL is made for web applications. Access is desktop DB that can work but isn't made for net.

<BLOCKQUOTE id=quote><font size=1 face="Verdana, Arial, Helvetica" id=quote>quote:<hr height=1 noshade id=quote>
We're planning on launching a new commercial site that is driven by a small (4 tables) database. We're expecting a large number of visitors visiting the site simultaneously. When it comes to handling a lot of concurrent users I know Access isn't the best choice because for example it cannot handle more than 10 open concurrent connections. We're looking for a good, but somehow easy to learn alternative. Can somebody give a good suggestion of what to use? E.g. SQL-server? What are the cons and pro's, and how could Ultradev be of any help? I really would appreciate any help on this one!

Rein


<hr height=1 noshade id=quote></BLOCKQUOTE id=quote></font id=quote><font face="Verdana, Arial, Helvetica" size=2 id=quote>

Viktor Farcic

TalkZone Manager

isn't there an issue with recordset syntax when giong from Access to SQL server? I thought that rsMyrecordset.Fields.Item("dbField" for an Access DB, had to be re-written to drop the .Item? Is that right?

Michael Rudge

btw, the number of concurrent db connections is a server license issue, not the db. You can get a app that allows you to use Access as the interface to mySQL. Doesn't give the same amount of control but you can make tables etc..

Michael Rudge

Syntax for displaying table field is the same for whatever DB.

<BLOCKQUOTE id=quote><font size=1 face="Verdana, Arial, Helvetica" id=quote>quote:<hr height=1 noshade id=quote>
isn't there an issue with recordset syntax when giong from Access to SQL server? I thought that rsMyrecordset.Fields.Item("dbField" for an Access DB, had to be re-written to drop the .Item? Is that right?

Michael Rudge
<hr height=1 noshade id=quote></BLOCKQUOTE id=quote></font id=quote><font face="Verdana, Arial, Helvetica" size=2 id=quote>

Viktor Farcic

TalkZone Manager

MySQL is the way to go!

Pro's: It's free, cross-platform (runs on NT or Unix), can handle 3 Terabytes information per table (which I don't think you could fill in this life-time, unless you're NASA), almost unlimited concurrent connections, and queries extremely fast.

Con's: None really other than a mild learning curve if you're new to MySQL, the relational table setup is relative to Access.

Again its a matetr of preference and existing architecture etc. My personal choice is PHP MySQL - free open source, continuous development via community not just in house developers, and increasingly faster and able to handle large numbers of 'calls' - you will also find many many resources supporting this. PHP is also very easy to learn especialy if coming from an existing programing background, and with some recent extensions to Ultra Developer it should prove to be quite easy to get to grips with.

<life>Do what thou wilst shall be the whole of the law. Love is the law, love under will</life>

<BLOCKQUOTE id=quote><font size=1 face="Verdana, Arial, Helvetica" id=quote>quote:<hr height=1 noshade id=quote>
MySQL is the way to go!

Pro's: It's free, cross-platform (runs on NT or Unix), can handle 3 Terabytes information per table (which I don't think you could fill in this life-time, unless you're NASA), almost unlimited concurrent connections, and queries extremely fast.

Con's: None really other than a mild learning curve if you're new to MySQL, the relational table setup is relative to Access.


<hr height=1 noshade id=quote></BLOCKQUOTE id=quote></font id=quote><font face="Verdana, Arial, Helvetica" size=2 id=quote>

There are ups and down on the side here too.. I read some mySQL manual that came with like 700 pages or so. I have it on a remote linux server and I am used to using ORACLE and SQL Server 2000 Enterprise at work using InterDEV by MS or even UltraDEV by Macromedia to do database work.

mySQL and UltraDEV are a pain in the rear to use. I am at the poing where I got MS ACCESS to connect to mySQL, via myODBC and such. I done the code in ASP locally and not I am ready to publish. I have ChilliSoft on remote Unix Server but I have to re-do the connection string to the Database. I am stuck there for now, till I get some more input/help from others.

I couldn't get any help from google or such. They only show you how to connect to mySQL and work with it.