SQL Server 2005 edition for Web applications

Question

We are developing a web application (ASP.NET) for a bank, and it uses SQL Server 2005. The bank will have to buy a license for SQL Server 2005.

The question is - which SQL Server 2005 version / license will be the least expensive for such purposes?

1) It seems that the SQL Server Express version which is totally free can do. However, it also seems that this version has limitations as to the exporting and importing of data, so this may be not the best choice.

2) There is a "client access license" (CAL) licencing model in SQL Server. In an ASP.NET application, it is possible to access data using the ASP.NET system user (although the web application may have hundreds or thousands of users). In this case, will it be enough to have an SQL Server license for just 1 user (the ASP.NET system user accessing the data)? If yes, this is probably the most cost-efficient solution.

Answer 1

1. SQL Server Express has some limitations but I don't know what you exactly mean by importing and exporting data. It does well for most small apps. I would consider the features I use in the application and the database size/CPU/memory requirement to see if SQL Server Express is applicable or not.

2. No, you can't use a single CAL for a Web application.

   For externally focused server applications. Processor licensing is a better choice for externally focused server applications, such as Internet and extranet scenarios. It is often difficult to count devices or users in these scenarios, so hardware-based pricing is more straightforward.

   ---

   Also noted here:
   Multiplexing: Use of Middleware, Transaction Servers, and Multitiered architectures Sometimes organizations develop network scenarios that use various forms of hardware and/or software that reduce the number of devices or users that directly access or use the software on a particular server, often called multiplexing or pooling hardware or software. Use of such multiplexing or pooling hardware and/or software does not reduce the number of CALs required to access or use SQL Server software. A CAL is required for each distinct device or user that is connected to the multiplexing or pooling software or hardware front end.

I suggest you consider SQL Server 2008 Web Edition