Re: Postgres SQL vs SQLite vs MS SQL vs MY SQL

SQLite is very good for what it is and requires zero admin and no installation, but it cannot scale, has no replication, and cannot run on separate server.

Postgres has robust transaction DDL, which means that if you get a crash in the middle of a migration the change gets reversed. MySQL does not have this, MSSQL used not to do it very well, SQlite does not do it but Django migrations try to emulate it. See here for more on migrations; https://docs.djangoproject.com/en/1.10/topics/migrations/#backend-support

Postgres is also very flexible, feature rich, FOSS, well supported by Django (especially with contrib.postgres )  and well tested with Django. It is even available on Azure as a hosted service from at least two providers. It should be the default choice unless you have strong reasons for using something else. 

On Thursday, December 22, 2016 at 5:26:07 PM UTC+5:30, NoviceSortOf wrote:

The primary cost is licensing unless we can scale the MS-SQL db projects size and more expensive hosting cost .  

Currently we use PostGresSQL, based in part of my suspicions of the limitations of SQLite. 

Our DB requirements though are complicated by the need to work with Asian languages, Chinese, Japanese and so on as well as European languages.  This makes a relative import/export trivial between various tables and is a major bottleneck. The workstations are Windows, the appeal of Azure is also knocking at the door, being able to off set some admin hardware costs. 

On Thursday, December 22, 2016 at 12:40:17 PM UTC+1, NoviceSortOf wrote:

Curious what advantages if any people are finding working with DBs other than the default SQLLite?

We are considering migrating to MSSQL to avoid kinks/ETL involved with having various DB backends for

office and server applications, but uncertain the additional cost will be worth it or not.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/b9830773-fc78-4514-83ad-adb79dd9849e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.