All geek questions in one place

Disadvantages of using SQL Server Compact and a dedicated SQL Server database

I am wondering what are the key differences between using a SQL Server Compact database ( .sdf ) and a full-fledged database like SQL Server Express?

Are there any serious performance issues, and if so, how big can a compact database get before you start to notice it?

When starting projects, I find using a compact database a simple, straightforward and clean solution, when do I need to convert and move to a dedicated database?

+6
source share
3 answers

Let's try:

  • maximum file size 2 GB
  • No stored procedures, triggers, etc.
  • There is no process but loaded into your AppDomain
  • As far as I know, cost optimizer or query plans for queries are not required
  • Lack of simultaneous access of several users simultaneously

The big problem here is that CE is just a file on your system, and you get access through a simple InApp call using the dll. This is enough in many scenarios. Many people will say that later you can switch to SQLS, but I don’t think so. This is a completely different world! CE is the only product in my eyes.

Remember that you need to deploy the CE-DLL when you do not publish your application!

+11
source

SQL Compact does not support stored procedures. You write your entire request directly in code. This is enough for me to choose SQL Express. We now have the LocalDB option, which simplifies deployment scenarios.

+2
source

Source: https://habr.com/ru/post/919224/

More articles:


All Articles