DHIS 2 to support PostgreSQL only?

Hi all,

I want to bring up the idea of solely support PostgreSQL for DHIS 2 for production use to get feedback from the community.

The DHIS 2 team is seeing clear benefits of moving to PostgreSQL-only. The main ones are:

  1. Supporting and testing for more than one database platform is time-consuming. The majority of DHIS 2 implementations is using PostgreSQL already.

  2. PostgreSQL supports advanced geospatial features through PostGIS. We are already depending on these for the GIS module to work optimally (i.e. for event clustering in GIS). There are no direct equivalent in e.g. MySQL. We are also considering using PostGIS data types in main data model.

  3. PostgreSQL will provide some impressive features which will become very useful for us in version 10 and 11. E.g. native partitioning, parallel queries, logical replication, foreign tables and improved query performance will be useful and allow us to develop the next DHIS 2 analytics solution.

We are aware this will be inconvenient for users of other databases such as MySQL, but there is the option of migrating your database through the DHIS 2 metadata and data value import-export feature.

On a technical note, we will keep the Hibernate development framework and keep supporting the H2 database for unit testing purposes.

Please let us know your thoughts on this.

regards,

Lars

···

Lars Helge Øverland

Lead developer, DHIS 2

University of Oslo

Skype: larshelgeoverland

lars@dhis2.org

http://www.dhis2.org

Hi Lars,
Make a lot of sense, and would free time in your team to provide more value (seems you are not lacking ideas). I would say go for it, with maybe dedicated documentation about how to move (even if it’s basically using the import/export feature “as is”, may be worth a couple of hours to write a step by step guide).

Martin

···

On Fri, Sep 8, 2017 at 10:26 AM, Lars Helge Øverland lars@dhis2.org wrote:

Hi all,

I want to bring up the idea of solely support PostgreSQL for DHIS 2 for production use to get feedback from the community.

The DHIS 2 team is seeing clear benefits of moving to PostgreSQL-only. The main ones are:

  1. Supporting and testing for more than one database platform is time-consuming. The majority of DHIS 2 implementations is using PostgreSQL already.
  1. PostgreSQL supports advanced geospatial features through PostGIS. We are already depending on these for the GIS module to work optimally (i.e. for event clustering in GIS). There are no direct equivalent in e.g. MySQL. We are also considering using PostGIS data types in main data model.
  1. PostgreSQL will provide some impressive features which will become very useful for us in version 10 and 11. E.g. native partitioning, parallel queries, logical replication, foreign tables and improved query performance will be useful and allow us to develop the next DHIS 2 analytics solution.

We are aware this will be inconvenient for users of other databases such as MySQL, but there is the option of migrating your database through the DHIS 2 metadata and data value import-export feature.

On a technical note, we will keep the Hibernate development framework and keep supporting the H2 database for unit testing purposes.

Please let us know your thoughts on this.

regards,

Lars


Lars Helge Øverland

Lead developer, DHIS 2

University of Oslo

Skype: larshelgeoverland

lars@dhis2.org

http://www.dhis2.org


Mailing list: https://launchpad.net/~dhis2-users

Post to : dhis2-users@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-users

More help : https://help.launchpad.net/ListHelp

**Martin Van Aken - **Freelance Enthusiast Developer

Mobile : +32 486 899 652

Follow me on Twitter : @martinvanaken

Call me on Skype : vanakenm

Hang out with me : martin@joyouscoding.com

Contact me on LinkedIn : http://www.linkedin.com/in/martinvanaken

Company website : www.joyouscoding.com

Hello Lars

I hope you are well.

I fully agree with your assessment and the benefits are clear.

Best regards,

JM

···

Lars Helge Øverland

Lead developer, DHIS 2

University of Oslo

Skype: larshelgeoverland

lars@dhis2.org

http://www.dhis2.org

Hi Lars,
I think like the DHIS2 is a system that needs to be deployed on a large scale, the choice to keep postgresql is ideal. In its recent version Postgresql becomes more flexible when there is a lot of data. It becomes very close to Oracle. the possibility of using the Json and its highly developed GIS module is a major asset. I’m ok to keep Postgresql as DHIS2 DBMS.

Cheers,

···

2017-09-08 10:02 GMT+01:00 JM Alcantara jmalcantara1@gmail.com:

Hello Lars
I hope you are well.

I fully agree with your assessment and the benefits are clear.

Best regards,

JM

El 08/09/2017, a las 10:26, Lars Helge Øverland lars@dhis2.org escribió:

Hi all,

I want to bring up the idea of solely support PostgreSQL for DHIS 2 for production use to get feedback from the community.

The DHIS 2 team is seeing clear benefits of moving to PostgreSQL-only. The main ones are:

  1. Supporting and testing for more than one database platform is time-consuming. The majority of DHIS 2 implementations is using PostgreSQL already.
  1. PostgreSQL supports advanced geospatial features through PostGIS. We are already depending on these for the GIS module to work optimally (i.e. for event clustering in GIS). There are no direct equivalent in e.g. MySQL. We are also considering using PostGIS data types in main data model.
  1. PostgreSQL will provide some impressive features which will become very useful for us in version 10 and 11. E.g. native partitioning, parallel queries, logical replication, foreign tables and improved query performance will be useful and allow us to develop the next DHIS 2 analytics solution.

We are aware this will be inconvenient for users of other databases such as MySQL, but there is the option of migrating your database through the DHIS 2 metadata and data value import-export feature.

On a technical note, we will keep the Hibernate development framework and keep supporting the H2 database for unit testing purposes.

Please let us know your thoughts on this.

regards,

Lars


Lars Helge Øverland

Lead developer, DHIS 2

University of Oslo

Skype: larshelgeoverland

lars@dhis2.org

http://www.dhis2.org


Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help : https://help.launchpad.net/ListHelp


Mailing list: https://launchpad.net/~dhis2-users

Post to : dhis2-users@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-users

More help : https://help.launchpad.net/ListHelp

Riddy NDOMA

“Codeur nocturne”

Skype: riddyndoma, G+: riddyndoma, FB: riddy ndoma
Twitter: riddyndoma, LinkedIn: riddy ndoma
Blog: http://riddyndoma.blogspot.com/
Vous servir est mon désire (Serving you is my desire)

Agree. As a prelude we can put the export import through its paces. Would be great to have a volunteer mysql Guinea pig user that we could document a migration.

···

On 8 Sep 2017 9:27 am, “Lars Helge Øverland” lars@dhis2.org wrote:

Hi all,

I want to bring up the idea of solely support PostgreSQL for DHIS 2 for production use to get feedback from the community.

The DHIS 2 team is seeing clear benefits of moving to PostgreSQL-only. The main ones are:

  1. Supporting and testing for more than one database platform is time-consuming. The majority of DHIS 2 implementations is using PostgreSQL already.
  1. PostgreSQL supports advanced geospatial features through PostGIS. We are already depending on these for the GIS module to work optimally (i.e. for event clustering in GIS). There are no direct equivalent in e.g. MySQL. We are also considering using PostGIS data types in main data model.
  1. PostgreSQL will provide some impressive features which will become very useful for us in version 10 and 11. E.g. native partitioning, parallel queries, logical replication, foreign tables and improved query performance will be useful and allow us to develop the next DHIS 2 analytics solution.

We are aware this will be inconvenient for users of other databases such as MySQL, but there is the option of migrating your database through the DHIS 2 metadata and data value import-export feature.

On a technical note, we will keep the Hibernate development framework and keep supporting the H2 database for unit testing purposes.

Please let us know your thoughts on this.

regards,

Lars


Lars Helge Øverland

Lead developer, DHIS 2

University of Oslo

Skype: larshelgeoverland

lars@dhis2.org

http://www.dhis2.org


Mailing list: https://launchpad.net/~dhis2-users

Post to : dhis2-users@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-users

More help : https://help.launchpad.net/ListHelp

Hi Lars

Fully agreed. To concentrate one one DB platforms will not only saves time and effort, also being efficiency to the system and can make more use of advance functionality of the PostgreSQL & PostGIS.

You will have our full support.

Hannan

···

On Fri, Sep 8, 2017 at 2:26 PM, Lars Helge Øverland lars@dhis2.org wrote:

Hi all,

I want to bring up the idea of solely support PostgreSQL for DHIS 2 for production use to get feedback from the community.

The DHIS 2 team is seeing clear benefits of moving to PostgreSQL-only. The main ones are:

  1. Supporting and testing for more than one database platform is time-consuming. The majority of DHIS 2 implementations is using PostgreSQL already.
  1. PostgreSQL supports advanced geospatial features through PostGIS. We are already depending on these for the GIS module to work optimally (i.e. for event clustering in GIS). There are no direct equivalent in e.g. MySQL. We are also considering using PostGIS data types in main data model.
  1. PostgreSQL will provide some impressive features which will become very useful for us in version 10 and 11. E.g. native partitioning, parallel queries, logical replication, foreign tables and improved query performance will be useful and allow us to develop the next DHIS 2 analytics solution.

We are aware this will be inconvenient for users of other databases such as MySQL, but there is the option of migrating your database through the DHIS 2 metadata and data value import-export feature.

On a technical note, we will keep the Hibernate development framework and keep supporting the H2 database for unit testing purposes.

Please let us know your thoughts on this.

regards,

Lars


Lars Helge Øverland

Lead developer, DHIS 2

University of Oslo

Skype: larshelgeoverland

lars@dhis2.org

http://www.dhis2.org


Mailing list: https://launchpad.net/~dhis2-users

Post to : dhis2-users@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-users

More help : https://help.launchpad.net/ListHelp

Muhammad Abdul Hannan Khan

Team Leader

Support to the National HMIS

MIS, Director General of Health Service

Ministry of Health and Family Welfare

T +880-2- 58816459, 58816412 ext 118

F +88 02 58813 875

M+88 01819 239 241

M+88 01534 312 066

E hannank@gmail.com

S hannan.khan.dhaka

B hannan-tech.blogspot.com

L https://bd.linkedin.com/in/hannankhan

Thanks all for the feedback on this issue!

regards,

Lars

···

On Fri, Sep 8, 2017 at 1:19 PM, Hannan Khan hannank@gmail.com wrote:

Hi Lars

Fully agreed. To concentrate one one DB platforms will not only saves time and effort, also being efficiency to the system and can make more use of advance functionality of the PostgreSQL & PostGIS.

You will have our full support.

Hannan

On Fri, Sep 8, 2017 at 2:26 PM, Lars Helge Øverland lars@dhis2.org wrote:

Hi all,

I want to bring up the idea of solely support PostgreSQL for DHIS 2 for production use to get feedback from the community.

The DHIS 2 team is seeing clear benefits of moving to PostgreSQL-only. The main ones are:

  1. Supporting and testing for more than one database platform is time-consuming. The majority of DHIS 2 implementations is using PostgreSQL already.
  1. PostgreSQL supports advanced geospatial features through PostGIS. We are already depending on these for the GIS module to work optimally (i.e. for event clustering in GIS). There are no direct equivalent in e.g. MySQL. We are also considering using PostGIS data types in main data model.
  1. PostgreSQL will provide some impressive features which will become very useful for us in version 10 and 11. E.g. native partitioning, parallel queries, logical replication, foreign tables and improved query performance will be useful and allow us to develop the next DHIS 2 analytics solution.

We are aware this will be inconvenient for users of other databases such as MySQL, but there is the option of migrating your database through the DHIS 2 metadata and data value import-export feature.

On a technical note, we will keep the Hibernate development framework and keep supporting the H2 database for unit testing purposes.

Please let us know your thoughts on this.

regards,

Lars


Lars Helge Øverland

Lead developer, DHIS 2

University of Oslo

Skype: larshelgeoverland

lars@dhis2.org

http://www.dhis2.org


Mailing list: https://launchpad.net/~dhis2-users

Post to : dhis2-users@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-users

More help : https://help.launchpad.net/ListHelp


Muhammad Abdul Hannan Khan

Team Leader

Support to the National HMIS

MIS, Director General of Health Service

Ministry of Health and Family Welfare

T +880-2- 58816459, 58816412 ext 118

F +88 02 58813 875

M+88 01819 239 241

M+88 01534 312 066

E hannank@gmail.com

S hannan.khan.dhaka

B hannan-tech.blogspot.com

L https://bd.linkedin.com/in/hannankhan

Lars Helge Øverland

Lead developer, DHIS 2

University of Oslo

Skype: larshelgeoverland

lars@dhis2.org

http://www.dhis2.org

Hello @Lars

@BoHou was trying to install DHIS2 with H2 Database and asked a doubt here. because there were errors due to absence of postgis

He was following installation doc here

would like to know your advice on postgis alternative he shall try if we still support H2 based DHIS2 installation.

Hi @jthomas,

thanks for reviving this three year old thread :slight_smile: DHIS 2 now only works on PostgreSQL and H2 will not work.

The page you found is unfortunately out of date. Please refer to the official installation docs here:

best regards,

Lars

2 Likes