https://sqlite.org/whentouse.html
SQLite is not directly comparable to client/server SQL database engines such as MySQL, Oracle, PostgreSQL, or SQL Server since SQLite is trying to solve a different problem. Client/server SQL database engines strive to implement a shared repository of enterprise data. They emphasis scalability, concurrency, centralization, and control. SQLite strives to provide local data storage for individual applications and devices. SQLite emphasizes economy, efficiency, reliability, independence, and simplicity. SQLite does not compete with client/server databases. SQLite competes with fopen(). --- In that regard, for web development, sqlite is not very useful because it is not made for that. On Thu, Dec 22, 2016 at 8:56 AM, NoviceSortOf <dljonsson2...@gmail.com> 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+unsubscr...@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/d8ab0337-d8b9-4c72-9f70-66624acba00f%40googlegroups.com > <https://groups.google.com/d/msgid/django-users/d8ab0337-d8b9-4c72-9f70-66624acba00f%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- 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+unsubscr...@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/CALn3ei3QaW6NQ_%3DdeqstFwxxL7o%2BVJ8dj532bLEd5it8KnruQw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
