Design Issue

[VB400]

In an effort to minimize network traffic, we're thinking of offloading some database table access to each individual desktop (this is NOT a web based app and there is no intention of making it so). This would only apply to static tables that hardly ever change such as "State", "Department", etc.

Clarification:

Rather than going across the network every time this list needs to be accessed, we're thinking of creating a local Microsoft Access database on each desktop that would house these static tables. This will definitely improve performance. As far as updating these tables in case they do change, we can have a program that will push these changes from the main backend DB to this Access MDB.

Pros and cons are welcomed.

Thanks! Tarek

 

[SemperFiDownUnda]

Con you can not do joins to these tables

ie
SELECT EA.Address1, EA.Address2,
C.CityName,
S.StateName
FROM EmployeeAddress EA
INNER JOIN City C
ON EA.FK_CityID = C.K_CityID
INNER JOIN State S
ON EA.FK_StateID = S.K_StateID

now becomes

SELECT EA.Address1, EA.Address2,
EA.FK_CityID,
EA.FK_StateID
FROM EmployeeAddress EA

then you have to look up localy for the other 2 pieces of info.

This will slow things down and may not actually save you that much bandwidth.

 

[Polu]

Hello, VB400.

Maybe running a few querys over the network an loading data into a hashmap could be useful.

Regards.

Polu.