Archives and Message Searching Availability
Message threading and searchable archives will not be available immediately after upgrading from versions 5.0 and earlier. ListManager 7.0 and later has new methods of threading and indexing archives so they are searchable.
After upgrading, ListManager will attempt to determine whether a message is a response to a previous message in that same list or whether it is starting a new 'thread' of discussion. This threading will be shown in the ListManager web interface.
ListManager also has a new improved method for full-text archive searching. The database design has been changed to make searching faster and more efficient, while also using less disk space. Additionally, the new web interface will allow new options for message searching include 'not equal' words, i.e., exclude messages that contain a set of words.
The database will be altered during the dbupgrade process to enable these features, and then as ListManager runs, the message-threading and full-text archives will be built. This means that any searches of the full-text archive may not find any data when
ListManager is started for the first time. ListManager will be busily rebuilding the full-text archive in the background, and once it has completed it will remain up-to-date, since every message is archived when it is received.
Database Upgrades
Moving MSDE to MSSQL
As your ListManager MSDE database grows, or as you performance requirements increase, you may need to migrate the data in ListManager's MSDE database to
Microsoft SQL server. These instructions show how to do so when installing MS SQL on the same machine currently used by ListManager. If you are moving ListManager, please do so as a separate step.
NOTE: Although ListManager may use Microsoft SQL, Lyris does not support the
Microsoft SQL database itself. These instructions are provided for the convenience of those using ListManager with Microsoft SQL, and are not a substitute for Microsoft's documentation.
1. Shut down ListManager.
2. Open a command prompt.
Lyris, Inc. | 6401 Hollis Street, Suite 125 | Emeryville CA 94608 USA |
www.lyris.com
Toll free +1.800.768.2929 | International calls +1.510.844.1600å | Fax +1.510.844.1598
Page 114
3. Detach the ListManager database by entering the following at the command prompt: osql -S localhost -E sp_detach_db ListManager go
4. Use the service manager to stop MSDE.
5. Copy the following files to another location:
C:\Program Files\ListManager\lmcfg.txt
The first two files are a backup of your ListManager database. The third file (lmcfg.txt) contains information ListManager uses to connect to the database. Be sure you have
backup copies of these files in another location; if they are lost or corrupted, you will not
be able to restore your ListManager database.
C:\Program Files\Microsoft SQL Server\MSSQL\Data\ListManager_Data.MDF
C:\Program Files\Microsoft SQL Server\MSSQL\Data\ListManager_Log.LDF
6. Uninstall ListManager and MSDE (Microsoft SQL Server Desktop Engine) using the
Windows Add or Remove Programs utility (Start > Control Panel > Add or Remove
Programs).
7. Install Microsoft SQL server (or at a minimum, the Client Network Tools) on the
ListManager server.
On the SQL server, create an initial database to be used for installation. This database will be used for installation purposes only.
8. Download ListManager for MS SQL
9. When prompted by the installer to specify the type of installation, select "New
Install".
10. Proceed with the installation as prompted, specifying the database you created.
11. Shut down ListManager if you started it after the installation.
Lyris, Inc. | 6401 Hollis Street, Suite 125 | Emeryville CA 94608 USA |
www.lyris.com
Toll free +1.800.768.2929 | International calls +1.510.844.1600å | Fax +1.510.844.1598
Page 115
12. Attach the ListManager database backup files using SQL Server Enterprise
Manager:
1. Right click on Databases.
2. Click All Tasks.
3. Click Attach Database
4. Specify the path where you copied ListManager_Data.MDF (e.g., C:\Program
Files\Microsoft SQL Server\MSSQL\Data\ListManager_Data.MDF)
5. By default, the database will be attached as ListManager. Change the database name in Attach as: if desired.
6. Specify the database owner. You may need to create an owner through the
"Security" option in Enterprise Manager.
7. Click OK to attach the database.
For MSSQL 2000:
1. Right click on Databases.
2. Click All Tasks.
3. Click Attach Database
4. Specify the path where you copied ListManager_Data.MDF (e.g., C:\Program
Files\Microsoft SQL Server\MSSQL\Data\ListManager_Data.MDF)
5. By default, the database will be attached as ListManager. Change the database name in Attach as: if desired.
6. Specify the database owner. You may need to create an owner through the
"Security" option in Enterprise Manager.
7. Click OK to attach the database.
For MSSQL 2005:
1. Copy the MDF and LDF file into the MSSQL database directory.
By default-- C:\Program Files\Microsoft SQL Server\MSSQL\Data
2. Right click on databases and choose "Attach..."
3. Then click the "Add..." button and choose the MDF file of the old database.
4. Under the database details, edit the "Current File Path" by clicking the "..." button.
Lyris, Inc. | 6401 Hollis Street, Suite 125 | Emeryville CA 94608 USA |
www.lyris.com
Toll free +1.800.768.2929 | International calls +1.510.844.1600å | Fax +1.510.844.1598
Page 116
