I am coming from MSSQL background to the Postgres which I am new to.
In MSSQL we have SSDT for VS which is a great way of publishing whole scripted DB to the server - and what more importantly is that the update scripts are created automatically for the changes (of course there are cases where they need to be altered but mostly does the work).
So the question is how would a similar flow work with postgres ?
There is one approach to use pg-migration but it requires tedious manual work of writing the bversion migration scripts which is not really the same.
So the feeling I have now is that it is like back on the beginning of 2K to write manually the update scrip for every deployment and to keep it in source control file diffs, very old school.
Any suggestion would be great from the postgres folks out there
PostgreSQL is an object-relational database, while Microsoft SQL Server is a relational database system. This means PostgreSQL offers more complex data types and allows object inheritance, though it also makes working with PostgreSQL more complex.
MySQL, MariaDB, Oracle, MongoDB, and SQLite are the most popular alternatives and competitors to PostgreSQL.
Create a New Connection Manager Follow the steps below to save PostgreSQL connection properties in a connection manager. In the Connection Manager window, right-click and then click New Connection. The Add SSIS Connection Manager dialog is displayed. In the Connection Manager type menu, select PostgreSQL.
As it seem there is a neat solution for that, I will try it hands on and respond
https://metacpan.org/pod/sqitchtutorial
It achieves exactly that - automating the deployment of db changes ( for a lot of databases not only postgres)
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With