Installation Issues

The complete list of files required to install SQL DMO and SQL Namespace listed in Appendix A were taken from the Redist.txt file distributed with SQL Server. Pay special attention to the following instructions about the placement and registration of some of the key library files:

Installation Notes for Distributed Management Objects (DMO)

The sqldmo.dll file must be registered using the regsvr32.exe utility. Example: regsvr32 \mssql7\binn\sqldmo.dll)

The sqlwoa.dll file should reside in the system folder (i.e., \winnt\system32 or \windows\system).

Installation Notes for SQL Namespace (SQLNS) Files

The following files must be registered using the regsvr32.exe utility:


	Example:  regsvr32 \mssql7\binn\sqlns.dll

It has been my experience that these instructions need to be followed exactly. Placing even a single file in the wrong directory or forgetting to register any of the above mentioned files will cause a failure when trying to instantiate a SQL Namespace object. It seems that SQL DMO is more forgiving, but I still suggest that you distribute these components exactly as suggested by Microsoft.

In Summary

The Microsoft Data Engine (MSDE) provides a robust alternative for desktop applications currently using the JET database, file-server option. By designing applications for MSDE you pave the way for a more painless, hassle free upsize to SQL Server when that time comes. Thanks to the SQL DMO and SQL Namespace COM libraries, developers now have the ability to include all the administrative utilities necessary for your client to manage the database without requiring years of training or hours of coding.

In a future article, I will discuss what is required to perform a remote, unattended install of the MSDE database engine on a client machine.

See All Articles by Columnist Danny Lesandrini