Speed of network database
- Thread starter miacino
- Start date
Fifty2One
Legend in my own mind
- Local time
- Today, 04:15
- Joined
- Oct 31, 2006
- Messages
- 1,412
Here is a link to blueclaw with some speed suggestions
http://www.blueclaw-db.com/access_consultant_rapid.htm
Also you can write a separate Access App for each type of user to link to a single shared Access database.
http://www.blueclaw-db.com/access_consultant_rapid.htm
Also you can write a separate Access App for each type of user to link to a single shared Access database.
- Local time
- Today, 06:15
- Joined
- Feb 28, 2001
- Messages
- 30,450
A lot of flip answers come to mind, but a hospital is serious business. I'll tone it down in this case.
My first thought is that you should consider searching this forum for the topics "Optimizing" and "Performance" - as well as "Networks" - using the forum's search function. You'll find various discussions, some of which might apply to your situation.
My second thought is that while Access is very good at what it does, network speed is not its strong point. Not to burst ANYONE's bubble here, but you must ask your bosses whether their goal is speed of service or cost. (Yeah, I know - they'll say "BOTH" - but you have to make them make a decision. That's why bosses make the big bucks.)
Where this is going is that for security (with the HIPAA act for USA hospitals) and stability, not to mention performance and minimizing exposure of records "over the wire", you MIGHT wish to consider something like a moderate server-class machine running SQL server. My thought here is that normally Access doesn't encrypt anything. Because of the way it passes data over the network, there is to my mind a significant risk of someone tapping the network and getting critical personal data. There are products that can capture whole transmission sequences. Someone with unscrupulous thoughts could grab tons of stuff off your wire and leave your lawyers gasping. Using SQL server (or a small ORACLE if you have that) as a back-end would give you improved security in that you would not transmit whole tables repeatedly over the wire. Instead, what you see would be more limited and therefore would leave the DB safer.
Not only that, but your networking gurus could set up an IPSEC session that includes data encryption over the wire, thus protecting your patients and clients even inside your own hospital. This is not without cost and only your IT shop will be able to properly evaluate that cost. But my point is that you have a special case of security when talking patient records and I don't thing out-of-the-box Access will be as safe for you as you might like. Further, I know that other products will give you better performance.
My first thought is that you should consider searching this forum for the topics "Optimizing" and "Performance" - as well as "Networks" - using the forum's search function. You'll find various discussions, some of which might apply to your situation.
My second thought is that while Access is very good at what it does, network speed is not its strong point. Not to burst ANYONE's bubble here, but you must ask your bosses whether their goal is speed of service or cost. (Yeah, I know - they'll say "BOTH" - but you have to make them make a decision. That's why bosses make the big bucks.)
Where this is going is that for security (with the HIPAA act for USA hospitals) and stability, not to mention performance and minimizing exposure of records "over the wire", you MIGHT wish to consider something like a moderate server-class machine running SQL server. My thought here is that normally Access doesn't encrypt anything. Because of the way it passes data over the network, there is to my mind a significant risk of someone tapping the network and getting critical personal data. There are products that can capture whole transmission sequences. Someone with unscrupulous thoughts could grab tons of stuff off your wire and leave your lawyers gasping. Using SQL server (or a small ORACLE if you have that) as a back-end would give you improved security in that you would not transmit whole tables repeatedly over the wire. Instead, what you see would be more limited and therefore would leave the DB safer.
Not only that, but your networking gurus could set up an IPSEC session that includes data encryption over the wire, thus protecting your patients and clients even inside your own hospital. This is not without cost and only your IT shop will be able to properly evaluate that cost. But my point is that you have a special case of security when talking patient records and I don't thing out-of-the-box Access will be as safe for you as you might like. Further, I know that other products will give you better performance.
Similar threads
