Hans-Christian Andersen
hans.andersen at phulse.com
Sat Dec 29 21:21:43 CST 2012
This would be a good option for someone who wants to stay within the Microsoft sphere of technology, but you just have to be aware of the limitations of the Express version of SQL Server that does not exist on other DB platforms: ie. - 10 GB database size limit - Only uses 1 CPU - Does not allow you to use more then 1 GB of RAM etc... http://en.wikipedia.org/wiki/SQL_Server_Express#Capabilities It's possible, however, that these limitations are not an issue for Tina, since she originally thought to deploy with Access as the DB backend. But, if you are expecting these projects to be scalable in size and performance, then SQL Express is a bad option to start with (unless you are anticipating paying Microsoft lots of money for a proper SQL Server license down the line when you hit those limitations). In which case, I'd recommend Postgres as being the best all round database. MySQL's perks are in that it is the most used database out there, so it is a common skill and lots of community support and it too does not have the limitations that exist in SQL Express. - Hans On 2012-12-29, at 4:56 PM, "Susan Harkins" <ssharkins at gmail.com> wrote: > If Access is part of the equation, consider SQL Server Express. > > Susan H. > >> >> I'm in complete agreement with Stuart here. MS Access was not designed for this sort of thing. If you are going to put something on the web, you are best going with MySQL as Stuart suggested or Postgres even. Both support Windows, so that's not an issue and you can find tools that convert existing access databases to MySQL, for instance. >> >> My wonder, however, is whether these Access databases will be used online and offline? >> >> Hans >> > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com