0

I'm using Orchard CMS, and on initial setup, the default setting is to use SQL Server Compact. I'm not too knowledgeable about different database types and performance.

So, will SQL Server Compact be able to handle a website getting 1,000+ hits? Assuming all else with the hosting provider is exceptional (bandwidth, up-time, etc).

2
  • Could you describe what makes SQL Server Express unusable in your scenario please? Commented Dec 9, 2014 at 16:28
  • @ThomasKejser - I did not say it was unusable. It does work perfectly fine for the site's I build so far with the Orchard CMS. However, I just wanted to know if there were considerable drawbacks to higher traffic sites. So according to the answers so far, it looks like it should still deliver, but may have reliability/security issues.
    – EdwardM
    Commented Dec 10, 2014 at 17:21

3 Answers 3

2

I have not used SQL Server Compact, but because of its design, there are warnings in the SQL Server 2012 documentation about concurrency issues.

See: http://technet.microsoft.com/en-us/library/ms171845(v=sql.110).aspx for warnings on:

  • Lost updates.

  • Inconsistent analysis (nonrepeatable reads).

  • Phantom reads.

If you need a free and much more functional version of SQL Server, consider using SQL Server Express. Its limits are considerable above the Compact edition. You can lookup its limitations.

2

SQL Server Compact is mostly used for building standalone and occasionally connected applications for mobile devices, desktops, and Web clients.

There are lots of features not supported in SQL Server Compact check differences and with lack of these features hosting provider with exceptional bandwidth, up-time, etc will not help in terms of performance and requirement too.

For website getting 1000+ hits, you can use SQL Server Express Edition, for which data limit is up to 10GB and free to use.

You can consider other edition if you are looking for database of size more than 10GB.

1

I am a SQL Server DBA - I am biased towards SQL Server. However if the budget is limited, I would suggest trying a mature open source database, perhaps MySQL, PostGreSQL or MariaDB.

Performance isn't your real issue here. The security of your data and the safety of strong ACID transactions are what you should really prioritise. How are you going to backup your data with SQL Server Compact? Do you intend to replicate your data to a reporting database? What if your instance of SQL Server Compact goes down, can you provide high availability?

The other enormous advantage of PostgreSQL and MySQL is the huge community of people using these and willing to share their knowledge / experience. We have this in SQL Server as well, but not with SQL Server Compact :(

Not the answer you're looking for? Browse other questions tagged or ask your own question.