Plex Database sqlite file has more than doubled in 10 days

[pshanew]

@danielg1976

I don’t want to hijack this thread with a debate on using sqlite, but if you want to point me to another discussion on this I am curious why you’d say this.

There are a few feature requests where folks go in to more detail as to why they’d like to see alternative database options for Plex:

[REQUEST] Move from SQLite to MySQL or Postgres

I would like to request that the metadata database com.plexapp.plugins.library.db move from SQLite to MySQL or Postgres ( Or any real external db for that matter).  I feel that this would bring additional stability and repair functionality for large collections.  Additional if this database was available as an external shared resource it would allow for additional clustering and high availability functionality.  

Switch from SQLite to PostgreSQL

So many issues with SQLite and high volumes of data. It crashes so many times. We need PostgreSQL. Please.

Alternative database options

My Plex DB is currently 489 GB in size, and SQLLite is surely having issues at times with this large database. Is there any chance we can get options to connect to mysql, mariadb or MSSQL Express sometime? This would make it so much easier to handle the large volume i am having, as well as doing preventive backups. It would also increase the ability to have several Plex servers using the same DB (as long as they have the same path to the content).

Some of it is interesting reading. Some folks desire it for a perceived deficiency in SQLite3’s performance. Others want it because they’d like to be able to share a single database among multiple servers. Yet others just don’t consider SQLite3 to be a “proper” database.

I’m of the opinion that SQLite is perfectly suited to the task of being Plex’s database engine.