General Enquiry RE Access-v-SQL DB

[scribbler]

Can anyone give me advice on the following..

Without going in to too much detail I will describe the scenario.

I have been learning HTML,ASP etc and developing a website in which I link to a large Access database 340mb on a server and am told I'd be better moving onto SQL database as this would be much better, faster, secure. At the moment, while the site is being developed, there are only 2-3 users at any one time viewing the data and the database performs well. but I expect soon to have at least 100+ users and by next year double that at least, possibly more. I'd like to continue with the existing database for a while as I'm spending all of my time trying to design the site & it's functionality but am worried that if I wait until next year the Access DB won't cope with the No. of users.

Any advice would be welcome.

 

[gmmastros]

Converting an app to use SQL Server instead of Access requires effort.

For the effort involved, size doesn't matter. What matters is the complexity. The more tables and queries you have, the longer the development effort.

You will have to import your Access data in to SQL Server. This usually isn't a huge effort.

For the most part, SQL Server's version of SQL (T-SQL) is similar to Access's version of SQL, but there are some differences.

In my opinion, you should convert to SQL Server as soon as possible. If your company is anything like mine, there are functionality requests all the time. Implementing functionality in Access, only to convert it to SQL Server later, seems like a wasted effort.

-George

Strong and bitter words indicate a weak cause. - Fortune cookie wisdom