I'm trying to get up to speed on SQL Express and came up with a potential showstopper for my project: I'm reading that MS doesn't recommend SQL Express in a production environment.
The particular concern is that the ASPNET process needs to run as an Administrator. I certainly haven't done that in my development environment and Sitefinity seems to run fine.
Anyone have any thoughts? I may just stick with MySQL as the full blown MS SQL isn't in my budget. Thankfully, this is an option in Sitefinity.
SQL Server Express Edition
When a process attaches to a SQL Server Express Edition database (.mdf file), the process must have administrative permissions. In general, this makes SQL Server Express Edition databases impractical for production Web sites because the ASP.NET process does not (and should not) run with administrative privileges. Therefore, use SQL Server Express Edition databases only under the following circumstances:
Use as a test database while developing your Web application. When you are ready to deploy your application, you can transfer the database from SQL Server Express Edition to a production instance of SQL Server.
Use if you are running a Web site that can use impersonation and you can control the privileges of the impersonated user. In practice, this strategy is practical only if the application is running on a local area network (not a public Web site).
Store the .mdf file in your site's App_Data folder, because the contents of the folder will not be returned to direct HTTP requests. You should also map the .mdf extension to ASP.NET in IIS and to the HttpForbiddenHandler handler in ASP.NET using the following element in the site's Web.config file: