By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
440,086 Members | 1,460 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 440,086 IT Pros & Developers. It's quick & easy.

No Keys on Federated tables

P: n/a
RdR
Hi,

I have a table in SQL Server with no keys, I point this as a federated table
in DB2 but in DB2 I have defined keys against this federated table in SQL.
Where will the key constraints be followed in DB2 or in SQL? How should a
select statement in DB2 for this federated table behave if there are
duplicates in SQL? The result I am getting is it is showing an actual
duplicate in DB2 for this federated table. Is there any setting in DB2 or
DB2 II to take into consideration federated key constraints?

Thanks,

JWK
Nov 12 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
RdR wrote:
Hi,

I have a table in SQL Server with no keys, I point this as a federated table
in DB2 but in DB2 I have defined keys against this federated table in SQL.
Where will the key constraints be followed in DB2 or in SQL? How should a
select statement in DB2 for this federated table behave if there are
duplicates in SQL? The result I am getting is it is showing an actual
duplicate in DB2 for this federated table. Is there any setting in DB2 or
DB2 II to take into consideration federated key constraints?

Thanks,

JWK

Constraints on nicknames are informational constraints. They are just
there to tell the optimizer that certain things are supposed to be true.
These constraints are "never" enforced by DB2. An exception may be
with a check constraint when an insert or update is attempted.

--
Rob Wilson
ro********@ameritech.net.invalid (remove .invalid)
Nov 12 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.