-----Original Message-----
From: Michael Whisenant <mwhisen@airnet.net>
To: emerald@iea-software.com <emerald@iea-software.com>
Date: June 16, 1998 10:09 AM
Subject: Re: Database Size.
>First and foremost you need to perform a calls consolidation, successfully.
> The other thing would be to run a checkdb on the Emerald db after deletion
>of the records in the calls consolidation process. I have over 5000MBRs
>and 30,000 calls per day and my db is less than 300MB, therefore I store
>the majority in RAM. I also delete the start records each evening for the
>previous day. This reduces the calls table size immediately in half.
>
>
>At 07:45 PM 6/14/98 -0700, you wrote:
>>We have the same problem..A HUGE DB. What command can we use to delete the
>>call information?
>>
>>-----Original Message-----
>>From: Robert Boyle <robert@garden.net>
>>To: emerald@iea-software.com <emerald@iea-software.com>
>>Date: Sunday, June 14, 1998 11:22 AM
>>Subject: Re: Database Size.
>>
>>
>>>At 08:13 AM 6/13/98 -0400, you wrote:
>>>>
>>>> We have about 350 MBRs and appoaching 200Meg in size. I have run the SQL
>>>> scripts to delete the call records with little effect. I know there is
>>>> something else that needs to be done but don't know. I figure the db
>>>should
>>>> be about 60-70 Meg in size.
>>>
>>>
>>>
>>>Those are your calls. We have about 1450 MBRs and one month of calls and
>>our
>>>database is only 29MB. Is your log file on the same device? If so, think
>>about
>>>moving it to its own device.
>>>
>>>
>>>>
>>>>
>>>> Is there any other maintenance that needs to be done. I have seperated
>>the
>>>> logs for the emerald db so I know it is not the logs.
>>>
>>>
>>>
>>>Also try a:
>>>
>>>DBCC CHECKDB(Emerald)
>>>
>>>See what errors it lists.
>>>
>>>-Robert
>>>
>>>
>>>
>>>
>>>
>>
>Michael J. Whisenant
>Vice-President, Operations
>AIRnet Internet Services, Inc.
>ph: (256) 704-4692 fax: (256) 704-2329