|
100% Developed & Supported in the state of Washington, U.S.A. |
|
|
March 6, 2007 Volume 2, Number 7 |
|
|
In This Issue · New Feature in ELM - Control Your Cache Files · Give Reports More Time to Complete · Migrating from One Version of Microsoft SQL Server to Another Check us out! Popular TNT Links
Read more… "I don't see how anyone can run Windows machines without ELM. It's like watching TV without TIVO." See how companies worldwide are using ELM to proactively manage their environments Contact Us 2001
Main Street
Phone: 360.546.0878 Fax: 360.546.5017 Toll-Free: 877.546.0878 |
New Stuff at TNT SoftwareSee TNT Software at TechMentor, Orlando. Come to Booth 409 to see a preview of ELM 5.0 Winners of three free conference passes for TechMentor Orlando - congratulations to:
Getting ready for ELM 5.0 -
...and more! New Feature in ELM - Control Your Cache FilesELM's robust design includes a caching feature that allows the Service Agent to store data locally in the event that communication with the ELM Server is lost. In almost all cases, communication is restored quickly and the cached data is sent to the server - no problem. Every once in a while, though, the cache file grows to its maximum size before communications are restored and the Service Agent cannot store its data. TNT Software Development and Support departments have collaborated to provide a solution for that problem. Starting with ELM 4.0.243, you are able to specify the location and size of the cache file for a service agent. A dialog has been added to the ELM Service Agent wizard that allows you to specify where the file should be stored and how big it should be. The dialog is pre-populated with the normal ELM defaults. ELM 4.0.243 is available for download now at this page. For those of you who wish to modify the cache file location or size for Service Agents already installed, here is the information that must be added to the registry These registry entries must be created for each ELM Service Agent for which you wish to control cache file location and/or size. Any of the 3 entries can be used to control the desired aspect of the cache file, and should be created under the following key: Key : HKEY_LOCAL_MACHINE
\ SOFTWARE
\ TNT Software
\ ELM Manager Agent
\ 4.0
\ Setting
Name: CacheDataMaxSize
Type: DWORD
Data: [value in MB]
Description: Controls the maximum size of the TNT Agent cache file.
If absent, default is 100 MB.
TNT Agent service restart required.
Name: CachePath
Type: SZ
Data: [local drive and file path]
Description: Controls the destination of the TNT Agent cache file
on the local computer.
If absent, default is %systemroot%\TNTAgent.
TNT Agent service restart required.
Name: MinDiskFreeSpaceInMBToContinueCaching
Type: DWORD
Data: [value in MB]
Description: Controls the minimum free space in MB before a TNT
Agent will write to a cache file. If disk free space
drops below this value, then the Agent will stop saving
data to the cache file. Logical drive checked is
determined by CachePath.
If absent, default is 20 MB.
TNT Agent service restart required.
Give Reports More Time to CompleteTNT Software Support and Development departments recommend that those of you working with a very large database add the following timeout to the C:\Program Files\ELM Enterprise Manager\WebSite\web.config file: <httpRuntime executionTimeout="3000"/> This will give the ASP worker process extra time to complete its processing, helping larger reports complete properly. Migrating from One Version of Microsoft SQL Server to AnotherTNT Software does not provide any specific details regarding database migration from one version of Microsoft SQL Server to another. Microsoft’s Knowledge Base contains this article regarding upgrades, and specifically references the migration of SQL 2005 Express to SQL 2005 (full versions). There is an ELM consideration, however, when such a migration is done. When migrating from one database to another, you should ensure that the SQL Maintenance job gets installed correctly. You should run the Database Wizard in order to check the Maintenance box; or uncheck it, Finish, then re-run the Wizard to re-check the box. Performing this action will make the SQL Server recognize the Maintenance Job. Please note that the Maintenance Job requires the SQL Agent to be installed and running. NOT Strictly Business
March 6th in History
|