Hi Guys,

Little bit busy with relocation, some time back I came across the interesting issue on ASE Server.

Suppose in our prod env, we have cross database referential integrity constraints, these referential integrity constraints stores in
sysreferences table by relating the dbids of the two dbs(primary dband referenced db).

When we perform the refresh from one server to another (Suppose PROD– > UAT).These constraints come as it is in refreshed database.
In refreshed dataserver, all dbs may not be created in same order assource dataserver, which results in dbid mismatch from source server.
Still our constraints are same as source db with source dbids.

When we run the dbcc checks on refreshed db, it starts flaging for the wrong dbid in sysreferences table.
Interesting ! Isn’t it?

In sybase manual and sybooks, I didn’t get any article related to db id mismatch, for cross db integrity constraints.
...