Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>I've long since completed the project which prompted this question, but recently I've had another project come along with very minor data requirements, so I spent some more time experimenting with this.</p> <p>I had assumed that Sql Server Express required licensing fees to deploy, but this is not in fact the case. According to Microsoft's website, you are free to use it with certain restrictions:</p> <ul> <li>Maximum database size: 4 GB</li> <li>Maximum memory used: 1 GB</li> <li>Maximum CPUs used: 1 (complete procs, not cores)</li> </ul> <p>Sql Server Compact is a bad idea for web applications because it requires a hack to make it work, and it isn't built for the concurrent access you'd need for the web. But if your application can fit within the modest limitations of Sql Server Express, it works pretty well. And since it speaks regular T-SQL like its larger siblings, you can use Linq to SQL with it.</p> <p>I hear that <a href="http://twitter.com/migueldeicaza/status/2368465000" rel="nofollow noreferrer">Linq to Sql support is now in the Mono trunk</a> for the 2.6 release, so L2S' tight-coupling to Sql Server will likely be a moot point in the near future. I will either end up porting my code to use Mono's superior Linq to Sql implementation on the db of my choice, or go <a href="http://subsonicproject.com/" rel="nofollow noreferrer">another route entirely</a> (SubSonic has improved by leaps and bounds since I last tried it). But for the time being, Sql Server Express is a valid choice for very small database-driven apps.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload