). It's a complete package, built with cf and Access, and everything's ready to go. I used it on a site about a year ago and I haven't had any problems. It's extremely easy to customize, too.
Can somoeone please comment on how well Access can handle a large site? Let's say we get 10000 sessions a month and 500 orders per month. Can Access handle that? Or should we use SQL Server?
I would say access could handle that, others would say no. But being able to handle it, and doing it well are very different if you get that much traffic, I would go with a database server (mssql, mysql, etc..), not access.
I think it's easy to change the structure from Access to SQL server, but how easy is it to import the data itself. That is, if I later decide I want to upgrade from Access to SQL server.
Importing is really not a problem. There are tools built into both Access and SQL Server for upgrading an Access database to SQL Server. The problem will be in your cfqueries. For example, Access handles dates differently than SQL Server, so you may have to modify your queries to cope with this.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.