Base de datos protegida

Lo ideal de esa arquitectura es que se instale en un único sitio y que todos los clientes accedan a la misma instalacion con un navegador.
Para llevarte una base de datos sql-server a un equipo, puedes instalar el motor Desktop Engine (MSDE) que está pensado para eso y no requiere licencia. Te pego un trozo de la ayuda que habla sobre el tema.
Un saludo
----------------------------------------------------------
Distributing SQL Server with Applications
After building and testing a Microsoft® SQL ServerT 2000 application, you must distribute it to customers. You must also be able to distribute the SQL Server components required by your application. There are two options for how you distribute SQL Server components with your application:
Distribute the SQL Server 2000 relational database engine and client components with your application.
Distribute only the SQL Server 2000 client components if your customers will already have an instance of SQL Server to which they can connect from your application.
The licensing terms controlling the redistribution of SQL Server components are defined in the file Redist.txt, which is located on your SQL Server compact disc.
Distributing the SQL Server 2000 Desktop Engine
The SQL Server 2000 Desktop Engine is a redistributable version of the relational database engine in SQL Server 2000. It allows an application that uses the SQL Server relational database engine to install the engine as a part of the application setup process. The Desktop Engine is designed so that an application can use it to store data without requiring any database administration from the end user. The Desktop Engine is designed to manage its configuration and resource usage dynamically, minimizing the requirement for administration of the engine after it has been installed. The Desktop Engine does not include SQL Server utilities or tools that have graphical user interfaces. The application setup is coded to install the engine. After the Desktop Engine has been installed, either the application setup or the application use the standard SQL Server APIs (SQL-DMO, Transact-SQL, and so on) to create and configure the database, and the application uses the SQL Server APIs to perform any needed administration.
The Desktop Engine Setup uses the Windows Installer service that ships with Microsoft Windows® 2000 and is available on Windows NT® 4.0, Windows 98, and Windows 95. For more information about Windows Installer, see the MSDN Library at Microsoft Web site.
There are several methods an application setup program can use for installing the SQL Server Desktop Engine:
For applications that use the Windows Installer technology in their setup programs, the SQL Server 2000 Desktop Engine is supplied as a set of Windows Installer merge modules. You can use these merge modules to integrate the SQL Server 2000 Desktop Engine Setup into the application's Windows Installer setup. For more information, see Merging the Desktop Engine into Windows Installer.
For applications that do not use Windows Installer-based setup programs, the SQL Server 2000 Desktop Engine provides a Setup.exe file. This Setup.exe program operates as a shell that calls Windows Installer to install the SQL Server 2000 Desktop Engine merge modules. For more information, see SQL Server 2000 Desktop Engine Setup.
Applications that do not use Windows Installer-based setup programs can also call Windows Installer directly. For more information, see Executing Windows Installer Directly.
SQL Server 2000 Desktop Engine Setup installs the SQL Server client components, so you do not have to distribute the client components separately if you install SQL Server 2000 Desktop Engine.
Before attempting to install an instance of the Desktop Engine, an application setup process should first ensure that the proposed instance name has not already been used by another instance of SQL Server, and the computer does not already have more than 16 instances (or 15 named instances) installed. SQL Server 2000 supplies two API functions to perform these checks. For more information, see Desktop Engine Installation API.
Distributing the SQL Server Client Components
If your customers already have an installed instance of SQL Server to which they can connect, your application setup only has to install the SQL Server client components. This only needs to be done if your application setup detects that client components are not installed on the client:
If your application requires only the relational database client connectivity components needed to support ADO, OLE DB, or ODBC, SQL Server 2000 supplies a SQL Server-specific Microsoft Data Access Components (MDAC) redistribution file named Sqlredis.exe. This file installs the OLE DB and ODBC core components, the Microsoft OLE DB Provider for SQL Server, the SQL Server ODBC driver, and the default SQL Server client Net-Libraries. The license terms that govern the use of the redistribution file are in the file Redist.txt on the SQL Server 2000 compact disc. For more information about running Sqlredis.exe, see sqlredis Software Distribution Executable.
If your application uses other SQL Server client components, such as PivotTable® Service or SQL-DMO, your application setup must also install the files needed by these additional components after installing the MDAC redistributable files. The list of which files must be copied over and which files must be registered are in the file Redist.txt on the SQL Server 2000 compact disc. The components covered by Redist.txt are:
Distributed Component Object Model 95 (DCOM95)
PivotTable Service
Decision Support Objects (DSO)
English Query
Replication
Data Transformation Services (DTS)
Distributed Management Objects (DMO)
SQL Namespace (SQL NS)
DB-Library