Page 1 of 1

different database (SQL Server, SQLite, PostgreSQL)

Posted: 2022-06-02 05:19
by onoehring
Hi,

has anyone used AG with a different backend database than MySQL/MariaDB? I am thinking of SQL Server, SQLite or PostgreSQL.
I know that in AG code we are supposed to be able to add certain database specific commands, but I have not done it.
Now, another project lurking around the corner this might be interesting.

If you have used another database system maybe you could elaborate what you did and how it worked, which errors you encountered while testing/in production. Didi it match the MySQL experience or are some things more problematic?

Thanks already
Olaf

Re: different database (SQL Server, SQLite, PostgreSQL)

Posted: 2022-06-02 11:51
by crnjak
in db.php you have a comment on top
/*
To implement a new db driver you should change the value of
the DATABASE cnonstant in definitions.php to the desired driver name, for example 'mssql'.
then adding cases for the that driver in each function below ...
*/
Personaly I dont try. But I have similar problem over a year ago where old base data is in MSSQL and I need to deliver on MySQL.

Re: different database (SQL Server, SQLite, PostgreSQL)

Posted: 2022-06-03 05:15
by onoehring
Hi crnjak,

thanks for point out that file/position - I did not remember that.

Did you solve your MSSSQL problem? Did you try to access via ODBC? Did it work - or how did you handle the task (and with which result?

Olaf

Re: different database (SQL Server, SQLite, PostgreSQL)

Posted: 2022-06-03 06:51
by crnjak
I try but didnt work. I think its because it have a lot of script for this database in MSSQL. For me is best solution to migrate data on MySQL and build solution from zero.