Microsoft SQL and ListManager
If you have never installed Microsoft SQL Server (MSSQL) before, this section will advise you on some basic steps to take. These instructions should not take the place of a qualified network administrator or any information provided by Microsoft.
Software Requirements
Note: Windows 2003 Server Web edition is not supported, as Microsoft SQL Client Tools cannot be installed on this platform.
ListManager has had its database connectivity libraries upgraded from the obsolete db libs libraries to the current OLE-DB libraries. The OLE-DB library is natively supported by the Windows operating systems dating back to Windows 2000. For Windows 2000, it will require upgrading to MDAC (Microsoft Data Access Components) version 2.80 or better for connections to work (more recent versions of Windows should have the required MDAC version). Besides increased stability, the OLE-DB will remove restrictions imposed by the older libraries, such as restrictions on the maximum sizes of particular database data types, such as varchars.
http://www.microsoft.com/downloads/details.aspx?FamilyID=8e2dfc8d-c20e-4446-99a9-b7f0213f8bc5&displaylang=en
Checking the MDAC version
1. Go to http://support.microsoft.com/kb/301202 and download the MDAC checker . Download cc_pkg.exe
2. Extract to default location: C:\CompChecker .
3. On the Component Check, choose the default: Perform analysis of your machine and automatically determine the release version.
4. In the left hand window, you should see the MDAC version under File Details. If the MDAC version is not 2.8, you need to upgrade the MDAC (the default version for Windows Server 2000 is MDAC 2.5SP3).
Upgrading MDAC to version 2.8
1. Go to :
http://www.microsoft.com/downloads/details.aspx?FamilyID=6c050fe3-c795-4b7d-b037-185d0506396c&displaylang=en and install the MDAC 2.8
2. Download MDAC_TYP.EXE version 2.80.
Restarting the server
1. CD C:\CompChecker and run cc.exe.
2. Run the default analysis.
3. Now you should see MDAC 2.8 RTM in the File Details on the left hand window in Component Checker .
Installation Options
Whether or not you are able to use all the installation defaults depends on whether you are a Microsoft house running Domain Controllers or not.
If you mainly use Microsoft software and have Domain Controllers established, then you can just select all the defaults from the wizard provided by the SQL Server installation tool. This will set your SQL Server to listen for secure connections only. Any user IDs that you want to create must be added as Windows users and mapped to the correct group in SQL Server. Please consult your manuals or Microsoft help if you have questions of how to do this.
SQL Server Authentication
If you do not primarily use Microsoft software, and do not run Domain Controllers, then you will not be able to accept all the defaults for the SQL Server install. When you get a chance to choose “Advanced Options” select Mixed Mode authentication to allow both Windows authentication and SQL Server authentication. This is the only change you need to make. Otherwise, just accept the remaining defaults.
As the SQL database password is saved unencrypted in a file (lmcfg.txt), you may later remove the password saved in this file and then specify that the password be provided on startup by altering this file.
Note: You must have a case-insensitive sort order installed (the MSSQL default).
Once your SQL Server is installed, you will need to create a database for ListManager to use.
1. Open Enterprise Manager, a tool included with your SQL Server installation.
2. Register the SQL server you'd like to use with Enterprise Manager. If the SQL Server is on the same machine which is running Enterprise Manager, you can register the name of the server as “(local),” or just leave the entry blank. Otherwise, enter the name of the remote server.
3. Choose the entry for “Connection” that matches your configuration described above. If you mainly use Microsoft software then leave the selection on “Use Windows Authentication”. If not, choose “Use SQL Server Authentication” and supply the user name and password to connect. If you have just installed the server for the first time you can use the login “SA” with a blank password. All the other options on that dialog box can be left as defaulted.
4. Once you have defined a connection to your server, expand the tree for that selection by clicking on the "+" sign next to the server.
5. Right-click the “Databases” folder, and select the option to create a new database.
6. Give the database a name appropriate for your use. If you are uncertain, you can use the name “ListManager”. The database name cannot have spaces or hyphens. All other choices in this dialog box may be left with the default value; however, we recommend setting the database autogrow size to 1GB .
At this point you have the SQL Server installed with an empty database ready for ListManager to run with!
Note: The ListManager database should be in the default instance of your SQL server. This is only for customers who may be running multiple instances of SQL server on the same machine.
Installing the Client Tools
If you are not running MS SQL on your ListManager machine (not recommended), you need to install the MS SQL Client Tools on the machine that will be running ListManager (and any other machine you'd like to be able to connect to the SQL Server). Client Tools are auxiliary programs that are necessary to connect to and manage your MS SQL server.
These tools come in two installation forms: Connectivity Only, or Server and Client Tools. All you need is the client tools (connectivity), but if you want to install more it will also install the client tools, so either choice is fine.
If you are running MS SQL Server and ListManager on the same machine (not recommended), you may skip this step, as the required client tools have already been installed as part of the server installation.