e-nspectDB.exe is used to install Microsoft's SQL 2000 Desktop Engine (MSDE). This is a freely distributable desktop version of their SQL 2000 Server.
The e-nspectDB.exe setup is a "wrapper" installation for the windows installer. You will be able to select a destination folder for the installation. As the MSDE has a 2GB database limit it would seem wise to install onto a file system that has at least 2GB of free space.
Also, the e-nspectDB.exe setup program will configure the SQL installation with the following user credentials:
username = "sa" (no quotes)
password = "" (no quotes.. yes.. blank!)
You can of course change these after installation.
e-nspect2k.exe is used to install three components. You can select which to install at run time, because you may not want to install all 3 on the same machine. The three components are:
Used to configure the Exchange Server Components and to view reports.
These can be installed on their own (no other components selected) onto a machine used purely for configuration and report viewing (for example, a management workstation).
Exchange Server Components
Used to collect and process data. This component is required to be installed on the Exchange server computer and nowhere else.
Used to store the processed data. This component should be selected for installation only if you want to create the e_nspect database at installation time. If you select this component you have to have a database server already running. This could be the host where you previously ran the e-nspectDB setup program or another SQL server. In either case you need to know the SQL server host name, and the username and password of an account which can create databases. The e-nspectDB setup program initialises with the username "sa" (no quotes) and a blank password.
It is not necessary to create the database during the installation process as it can be created later using the Client tools.
Please refer to the architecture section for details on these components.
For low usage production scenarios the above architecture can also be used. However, the use of the SQL Desktop Engine and Exchange Server on the same machine could cause performance issues if your sites usage characteristics increase.
It would be better to separate the Exchange and SQL servers onto different machines.
The SQL2000 Desktop Engine has some limitations: