Advice on Database's on Websites

[JFK]

Hi all

I've been asked if I can add a database with search facilities to our company website.

The problem is i've never done anything with databases on websites can anyone recommend a good source of information as to how I would go about this.
We mainly want to search our products by 2 or 3 parameters entered by the customer and return the results if I was doing this on a Network it would be no problem but not having any experience of using it on the web. I don't really know where to start hence the question.


thanks

JFK

[aidan]

I'm working on a similar project. I'm planning to use a MySQL database which is searched with PHP. Because I'm not very familiar with either I'm practising with a JET database and ASP. When it all works then I'll port it across.

The code will consist of:
- breaking the search string into keywords
- doing a SQL query with those keywords
- building some HTML code to display ten of the results

[mgiambrone]

Hi guys,

I want to do the same thing but I don't have the resources to do my testing.

Does anyone know of any sites that offer free space for testing with ASP and MYSQL or MS Access??

[barni07]

You can get a free space in Tripod, where you can create your own MySql database, and your PHP pages. You can create your database in a really easy way, with a nice GUI, and there's no need of large sql sentences.

I just know the spanish version (http://www.tripod.lycos.es), but I guess there should be the english version too.

Greetings and good luck

[JFK]

Aidan

I think I will be restricted to using Jet as I have no experience of MySQL at all. Where are are you finding the info on how to do this?

JFK

[abhijit]

Originally posted by JFK
Aidan

I think I will be restricted to using Jet as I have no experience of MySQL at all. Where are are you finding the info on how to do this?

JFK

I do not think that a Jet Database for a website will be a feasible solution. I suggest that you go in for a database like SQL Server, but if costs are bogging you down, then go for a free database like myDB.

In this case, I guess you already have a webserver. In case of php, you can always use ADO, if your webserver is hosted on a windows server. However I suggest that JET is a NO-NO...

Cheers!
Abhijit

[JFK]

Hi abhijit

Can you explain why you think jet is a complete no no, sorry to be a complete dunce but I have to report back to my MD and I would like to have a little more than jet is complete no no. I'm quite prepared to try others if there are justifiable reasons for doing so.

thanks

JFK

PS do you have a link where I can get more info on myDB?

[abhijit]

Originally posted by JFK
Hi abhijit

Can you explain why you think jet is a complete no no, sorry to be a complete dunce but I have to report back to my MD and I would like to have a little more than jet is complete no no. I'm quite prepared to try others if there are justifiable reasons for doing so.

Hi JFK,

I have a document, which I shall mail you. Please post your email address.

Other reasons why I found access limiting is multiple users. It cannot handle faster updates / inserts from multiple clients. This is due to its architecture.



Cheers!
Abhijit

[mendhak]

Add to that the fact that after a couple thousand entries, the MDB file starts bloating up in size.

It's best that you convince your MD to shell out some more and get a decent DB like SQL Server 7/ 2k.

Or you could go the free way and get mySQL (www.mysql.org)

Both are good, better than Access at least.

[JFK]

The database will consist of 1 table only with no more than 250 records. As more get added the old ones will be removed as they will have been replaced by the new ones.

This is likely to be a one off but i'm still not sure which is the best way to go. SQL Server seem's expensive as a one off I'll have a look at the mysql solution.

The main thing with this is speed I don't want to leave the customer hanging around for the results of the search else he's likely to leave, though I expect most of you have the same problem.

[mendhak]

Originally posted by JFK
The database will consist of 1 table only with no more than 250 records. As more get added the old ones will be removed as they will have been replaced by the new ones.

This is likely to be a one off but i'm still not sure which is the best way to go. SQL Server seem's expensive as a one off I'll have a look at the mysql solution.

The main thing with this is speed I don't want to leave the customer hanging around for the results of the search else he's likely to leave, though I expect most of you have the same problem.

If the case is as you describe it, then mySQL would be the best way to go. There isn't much point in shelling out all that cash for a corporate type database, when you can have mySQL. mySQL is just as fast, and you won't be facing many problems.

For example, take a look at vbforums.com itself. It's using php and mySQL, and I'm sure you have noticed the speed.

[abhijit]

Originally posted by mendhak
For example, take a look at vbforums.com itself. It's using php and mySQL, and I'm sure you have noticed the speed.

Mendhak,
From where I sit, it appears that vbforums.com seems to be slowing down each day.

Cheers!
Abhijit

[crpietschmann]

You should choose a database based on your needs:

1. Access is a very feasable database solution. Its just not scalable enough to have more than a handfull of simultaneous users. But, if you didn't need up to the second data, you could cache the data in your web application every minute or two and then you would drastically increase the number of simultaneous users you could have.

2. mySQL is nice and free, but it wont support stored procedures until version 5.0 is released.

3. SQL Server is also very nice and costly. You can always use the MSDE (Microsoft SQL Server Desktop Engine), which is a FREE version of SQL Server. The only limitation is that it only supports a single processor.

4. Flat XML files. This is my favorite, there is no overhead of running a service like mySQL or SQL Server. The best design would be to have an XML file for each table, and to design a great DAL that allows you to SELECT/INSERT/UPDATE the data.



These are all feasable solutions. There are many people who say you should never use Access, don't listen to them. If you have a small database thats not going to have alot of simultaneous users, then use it if you want. If you need to use stored procedures, then use SQL Server or MSDE.

[Ecniv]

I'm using Access as a backend .. well multiple, but I'm not getting many hits so its prolly ok.

As to using Asp and Access is like VBA and Access (or VB and Access) with little parts removed.

If you are comfortable programming in access/vb then go with asp. If the db needs to be scaled up in the future, then mention it now so you can say you thought about it.

igger dbs and more hits go for php n mysql (both free?) but then you'd need a training session or two on setting up and using I expect - however - benefit to you will be that you would have experience of them incase you feel the urge to shift in the future

Up to you really. I'd personally go for Asp and Access as a starter. Then shift up if you need to to Sql server (rent online?? set up on the main company server??) or to php and mysql. It all depends on time, money, and your preference.


Vince

[mendhak]

Originally posted by abhijit
Mendhak,
From where I sit, it appears that vbforums.com seems to be slowing down each day.

Cheers!
Abhijit

Maybe it's your Internet connection.

[crpietschmann]

Originally posted by Ecniv
igger dbs and more hits go for php n mysql (both free?) but then you'd need a training session or two on setting up and using I expect - however - benefit to you will be that you would have experience of them incase you feel the urge to shift in the future

When I mentioned the use of MySQL in my previous post, I did not mean use PHP. I meant using MySQL with .NET. There are a couple of open source MySQL data providers built for .NET and there is one in the Mono project I believe. But, you could always use the System.Data.OleDb namespace.

.NET all the way baby!