System Design in Master/Slave office setup

[Firecat1970]

Hello everyone,

I have a design question to consult.

Our system will be used by 1 master office, and many regional office.
The requirement is that
1. Master office can view/change all data inputted by all offices.
2. Slave office can only view/change data they inputted.

My question is, at which point would you place the data filtering logic by region. The probable query users would place is "SHow me all Purchase Order with PO Number beginning with A1", and I want the regional filtering mechanism to work behind the scene.

Is Stored Procedure the best place to handle this?

Thank you very much.

 

[vbkris]

>>My question is, at which point would you place the data filtering logic by region. The probable query users would place is "SHow me all Purchase Order with PO Number beginning with A1", and I want the regional filtering mechanism to work behind the scene.

depends, on the face of it, i would suggest using just one table and have an extra field for containing the region id.


>>Is Stored Procedure the best place to handle this?

Yup.

and one more thing, there is a SQL Forum here. i guess you could get better opinions there...


Known is handfull, Unknown is worldfull