The online FAQ database contains hundreds of answers to frequently asked questions, articles on using our
web server applications and other related technologies, and resolutions to common problems. If you are seeing
an error message, be sure to try searching on the error message or error number that you are seeing.
|
| |
| |
| |
| |
|
How do I decide what kind of database I should use for my site? I don't know if I should use a JET database or a SQL Server database.
|
|
|
Choosing between a JET database and a SQL Server database is fairly easy, as there are a few distinct points between the two that should make the choices easy for you. But first, let us take a look at what these databases are. A JET database is a flat file database that consists of single MDB file that you upload to your site. The application can store its data within the JET MDB database file. This is the same file format used by Microsoft Access and the MDB file can be opened and read with Microsoft Access. However, you do not need to have Microsoft Access at all in order to use a JET database. All of the current versions of Windows Server have the built in ability to use JET databases. You can backup your JET database by simply making a copy of the MDB file on your site. The limitations with a JET database are that the JET database engine is not built for high concurrent usage or security or fault tolerance. We will expand on that more in a moment.
A Microsoft SQL Server database is pretty different from a flat file database like JET. First, you do not have any files or anything to upload to the SQL Server in the same manner as a JET database. A SQL Server database operates very differently from flat file databases. When your SQL Server database is created, it is an empty database and must have the database structure, or schema, created within it for the application(s) to use. Our applications include SQL Server setup scripts that build and create all of the database objects needed in your SQL Server database. SQL Server databases are built for high performance and high security.
Now in actually choosing which database to use, you can determine that pretty easily based on the anticipated size or performance needs of your site. If your site is starting off small, you have a limited budget to work within, or you have no idea of the amount of traffic that you anticipate on receiving on your site, then you should probably start with a JET database. While the exact numbers and performance varies based on server resources, JET databases can usually handle up to around 25 concurrent users on your site at once. This is not a limit on the number of users accounts that you can have on your site. You can have hundreds or thousands of accounts. The limitation of a JET database will be how many of those users can be active on your site at the same time. Once you reach the limitations of what a JET database will be able to do, your users will start seeing very slow site response times and page timeout or database error messages. This is just the nature of the way JET works up to its failure point. When a site using a JET database reaches that point, then it is time to upgrade to a SQL Server database.
If you anticipate an active site with many users, need the best performance, or need the highest reliability, then you should use a SQL Server database. Since SQL Server is built for performance and reliability, it can easily take your site up to dozens, hundreds and even thousands of concurrent users on your site. Of course, once you start having thousands of concurrent users, you will need more advanced options than most sites are using, but then at that point you will also have suitable traffic to warrant the need for it. SQL Server also allows for much more advanced features such as active backup of the database without interrupting site operation. Searches and other database operations are drastically faster using a SQL Server database and will make your site much more responsive to your end users. Most ISP's or web hosts will also provide shared SQL Server hosting for their customers. So you can have the benefits of a high performance SQL Server without any licensing costs or issues, or having to learn or hire someone to operate a SQL Server.
|
|
|
|
| |
