Web Database Architecture (Pros and Cons)

[Nick S via AccessMonster.com]

I’m not a database designer, yet find myself writing the specifications for a
new database (Access now -> SQL in 2008) that will be used:

1) Internally: To manage a fairly simple business (one user, 8 to 10 tables),
and
2) Externally: To enable clients to update certain fields

Architecturally, it seems I have 2 primary options:

1) Single Web-Hosted Database.
PROS: One database to manage.
CONS: Managing a database remotely seems fraught with problems.
All management/access/applications will require web front-ends (ASP.NET, Data
Access Pages, etc.)

2) Replicated Database (One Master, One Replica) Synchronized Nightly.
This option is possible because data updates from users are not time-critical.

PROS: Can manage database locally. Only front-ends to worry about are for
external users; which are vastly simpler than internal interfaces.
CONS: Replication Management (Fear of the Unknown)

Or possibly: 3) Linked Tables Over the Web. If this is even possible, I
assume this approach would introduce significant performance and security
complications, thus I’m not seriously considering it.

Can anyone offer me advice as to which, if either, of options 1) or 2) make
more sense and why? Or is there a better option of which I’m unaware?

Thanks,

Nick

 

[Baz]

I'm not a database designer, yet find myself writing the specifications for a
new database (Access now -> SQL in 2008) that will be used:

1) Internally: To manage a fairly simple business (one user, 8 to 10 tables),
and
2) Externally: To enable clients to update certain fields

Architecturally, it seems I have 2 primary options:

1) Single Web-Hosted Database.
PROS: One database to manage.
CONS: Managing a database remotely seems fraught with problems.
All management/access/applications will require web front-ends (ASP.NET, Data
Access Pages, etc.)

2) Replicated Database (One Master, One Replica) Synchronized Nightly.
This option is possible because data updates from users are not time-critical.

PROS: Can manage database locally. Only front-ends to worry about are for
external users; which are vastly simpler than internal interfaces.
CONS: Replication Management (Fear of the Unknown)

Or possibly: 3) Linked Tables Over the Web. If this is even possible, I
assume this approach would introduce significant performance and security
complications, thus I'm not seriously considering it.

Can anyone offer me advice as to which, if either, of options 1) or 2) make
more sense and why? Or is there a better option of which I'm unaware?

Thanks,

Nick

You could use terminal services (aka "thin clients") to give your clients
remote access over the net. Or, more crudely, you could allow them remote
control of a workstation on your network using PC Anywhere or VNC. Security
can be catered for adequately by using a VPN (very easy to set up).