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).
I like this idea if for no other reason than moving my database off my Plex Server. I also have hope that the ability to have an external database server might also facilitate things like synchronizing two PMS servers with shared storage.
Well my database just passed 800GB and now plex crashes on every refresh. So i had to make a PowerShell script to restart it automatically. The DB is just to big for SQLLite. Adding option to use external alternativ database would also make it easier to get frontends like plexwatch and similar going.
Are you sure your db is 800gb larg? My whole Database folder has roughly 1gb (/$path/Library/Application Support/Plex Media Server/Plug-in Support/Databases). The thumbnails on the other hand are REALY space consuming… My library has roughly more then 3k movies and way more tv episodes. Still, the main db file itself is less than 200mb…
Though, an option to use a standalone DBMS support would be much appreciated.
Understanding that SQLLite is easy from a web installation and deployment process, another database platform, even at a mark up would be appreciated. It would open up a number of other options such as reporting and security to protect the core database activity while allowing a “PlexReporter” to have dirty-read access so it would not lock the database tables while creating reports such as a simple list of movies or music. how many copies of the same song do I have? Right now these simple questions are not easy to access. In order to make this accessible to Grandparents and the technically challenged, SQLlite is going to reach it’s end of very quickly and they will simply think the product doesn’t work. The good news MicroSoft has announced sqlserver for linux… https://www.tecmint.com/install-ms-sql-server-centos-ubuntu-linux/ , and there is Firebird, and MySQL which have easy deployment tools.
We understand this is not a simple request, but for those of us who love the product we are quickly pushing the limits and a more robust engine is becoming apparent.
There are still timeouts to the DB when tailing the log when using dedicated SSD’s. While sqlite is great for a single user on a device, it’s pure dog ■■■■for this solution. Instead you’ll hear bullshit like upgrade your hardware because it’s easier to redirect the issue than to actually correct it.
This should be done a long time ago. After so many years still sitting on sqlite with no option to connect to anything else is kinda joke. Almost every application give the possibility to connect to external database provider and it’s not so hard to implement.
I suggest making sqlite as the default provider with an advanced possibility to connect to external database
1 Like
It’s pretty sad that folks are having to migrate to NVME storage JUST so the DB won’t be the bottle neck in the system. Even tossing the DB in a RAM drive hasn’t helped and my DB is only ~700MB. This is getting absurd. Can someone from the Plex side please prioritize this as a new feature?
1 Like
My database file is over 1gb in size and even while it was not the fastest on spinning disk, still worked acceptably.
If you have problems with a ~700 meg db file on nvme or even ramdisk, then I suggest you have other problems at play.
All that said, I do support the request for being able to use an external database like mysql or whatever.
fwiw, I now have my plex (linux) install spread across multiple disks.
- installation folder and metadata on raid 10 (4 disks)
- database folder on dedicated 500 sata ssd (nothing else using that disk).
Everything works fine, I just see those warnings in the logs which really annoys me. Searches function fine, libraries load fine etc. Moved it back to my 4 disk RAID5 setup and it’s still acting the same way.
OIC.
OCD.
ok then.
1 Like
It’s a curse. Knowing something isn’t quite right makes me want to solve the problem before it becomes a major issue.
I had to reinstall my Plex server on FreeNAS because it suddenly became unavailable while I was modifying music metadata through the web interface. I tried to use the same DB but could not connect to the server. Once doing a fresh install losing all manually added metadata, Plex Media Server worked without a hitch and has been running perfectly for the better part of a month.
So my question is: could this have been due to an overload of the db, or something else? I’m working on relatively old hardware tbh, but an upgrade is probably not in the near future. I’d like to make the library look as good as possible, including artwork etc, but don’t want to run into the same issue a few days into the project.
Bump!. having alternatives or even just one alternative to SQLite needs to be a priority!
A request for the same feature exists already, and it has more votes.
Therefore this one is closed, to prevent spreading the votes across several threads, even though they vote for the same (or at least very similar thing).
Votes are given back to the users who voted on this request. Please think of re-voting in the other thread if you still want it.
Rules for the Feature Suggestions forum section:
- Please search before creating a new suggestion thread.
- Only one feature per thread.
See existing feature suggestions, sorted by most popular first
https://forums.plex.tv/c/general/feature-suggestions/l/votes
