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

Opinions on db structure

P: n/a
DFS
I'm creating an Access 2003 field-based survey tool. The field users (50 of
them) submit survey results each week to a master db at the HQ.

Primary Key for field database is SurveyID, with a unique index on
PropertyID + SurveyDate.

When the field users submit the data, I'm going to send only the PropertyID
+ SurveyDate, and have the master db assign a new SurveyID for use within
that [Oracle] database.

So I'll end up with two SurveyIDs - one on the field user's system, and a
different one at HQ. I doubt anyone but me will ever see or use the
SurveyIDs.

Anyone think this is good or bad?

I could go with a composite PK of PropertyID + SurveyDate on both systems,
but this system will eventually have millions of records, so the single
SurveyID is more efficient.

Thanks
Nov 13 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.