Devart Forums

Is there a plan to support schema compare for postgres?
How come this feature is available in non-sql dbforge products but not in dbForge?

We are planning to release the first version next month. It will work with Redshift for now. However, we will keep actively working on it.

Can you give a date range for the release ?

It should be released this month.

Amazon Redshift problem with IDENTITY
This is output from Aginity Workbench for Redshift -> DDL
CREATE TABLE xxx.yyy
(
rct_sk INTEGER IDENTITY(-1, 1) NOT NULL ENCODE az64,
rct_id INTEGER NOT NULL ENCODE az64,
pch_ord_sk INTEGER ENCODE az64,
pch_ord_id INTEGER ENCODE az64,
unt_of_mea_sk_rcv INTEGER ENCODE az64,
unt_of_msmt_sk_ord INTEGER ENCODE az64,
rct_nm VARCHAR(256) ENCODE lzo,
dscr VARCHAR(1000) ENCODE zstd,

This is output from dbForge Schema Compare for PostgreSQL synchronization:
CREATE TABLE xxx.yyy(
rct_sk integer NOT NULL IDENTITY("identity"(1784630, 0, '-1,1'::text)),
rct_id integer NOT NULL,
pch_ord_sk integer,
pch_ord_id integer,
unt_of_mea_sk_rcv integer,
unt_of_msmt_sk_ord integer,
rct_nm character varying(256),
dscr character varying(1000) ENCODE zstd,

Note - IDENTITY is wrong, ENCODE only for one column.

Second issue - ALTER TABLE xxx.yyy
ADD FOREIGN KEY (apv_rcv_dt)
REFERENCES dcas_crm.dim_date(dt_sk) INITIALLY IMMEDIATE;

There no INITIALLY IMMEDIATE in Redshift.

I wanted to use this tool to compare the schema between two Azure databases for PostgreSQL, but when using the tool the following notice was shown: "Support for this server is restricted and allowed only for compatibility with Amazon Redshift."

So ... Is the Schema Compare tool for PostgreSQL? Or isn't it?
And if it isn't meant for Azure DB's, is there another option I can/should use?

We support Amazon Redshift for now.
Azure PostgreSQL is PostgreSQL Server, while support is limited.