Befuddled
osTicket in its current state (what we call "Legacy") only supports MySQL and MariaDB. With that being said, with v2.0 we will be able to support a few more databases. With v2.0 we are completely rewriting the codebase using the Laravel framework for the backend (and ReactJS for the frontend). Laravel 10.x (latest) currently supports 5 different databases. Here is their full list of supported databases:
Unfortunately, they don’t have MSSQL support at this time but as the framework progresses over time they should (hopefully) add support for more and more databases. The problem with supporting different databases is that the structure, storage engines, etc. are completely different for each one. You’d need an extremely robust and agnostic ORM that can handle all the different types; which is very hard to do properly and efficiently. So I commend them for their efforts so far.
On the note of v2.0 (cause I know you’re going to ask lol):
v2.0 does not have a set release date. We hope to release an RC (Release Candidate) by the end of the year for people to play with and at least see the new UI/UX, etc. v2.0 development has been going very well and we are very pleased with what we’ve accomplished so far. As you can imagine rewriting such a monolithic software like osTicket with so many intricate moving parts is a massive undertaking that needs to be handled with utmost care, attention, and just plain hard work. I know some community members think I sound like a broken record at this point but, we are so excited to share what we've been working on to the community so please stay tuned! 🙂
Cheers.
