This chapter describes the details of Microsoft SQL Server configuration.
Secure Office .NET have a flexible mechanism to configure the
connection to MS SQL Server. You can easily configure Secure Office .NET to work
with the existing MS SQL Server 2000/2005 or to use a free Microsoft SQL Express
2005. Secure Office .NET comes with an sc_sql_ini.exe program, which
configures the SQL Server connection. You can run this program anytime after
setup - when you will need to change the connection settings.
SQLExpress 2005 (typical
Using Microsoft SQL Express 2005 is the simplest solution.
Download and install a free SQLExpress 2005 database server
software from Microsoft.com website.
Install all modules of the program into the same computer. Select Windows Authentication
SQL Server 2000/2005
If you use MS SQL Server 2000/2005, the SQL Server settings depend on the
domain's settings. The domain's Administrator must define the necessary security
policies. You can use Windows Authentication or SQL Server Authentication.
The installation creates Sc_office_v1 database with pk_log table.
You have to enable a security permission for Windows user to read the
database. The name of the user is ASPNET for Windows 2000 and NT
AUTHORITY\NETWORK SERVICE for Windows Server 2003. If you will use
Windows Server 2003, make sure that the site "WebSetup Secure Office.NET" is
running inside the Application pool with NETWORK SERVICE rights (that is
a default behavior). The
system service "Secure Office .NET" is running with a rights of "Local System" and
has an access to MS SQL Server. To use the remote MS SQL Server, you
need to consult with
your network administrator for details regarding the database access.
Consult with your SQL Server administrator to make sure, that your MS SQL Server 2000/2005 supports this
authentication type. The "Web access" module of Secure Office .NET creates a new
restricted user of SQL Server to review
the logs and statistics. For security reasons, don't use the same user for
"Web access module" and "Secure Office .NET administration module". "Secure
Office .NET administration module" must always use Windows Authentication.
- SQL Server Authentication