RE: RadiusNT with SQL server

Peter A. Sang ( (no email) )
Wed, 31 Dec 1997 17:56:20 +0100

Although there _are_ ways to remove some segments, I'd strongly
recommend creating a new DB with simpler segment allocation (~200MB
Emerald_log, ~ (current_size+250) MB Emerald_dat) and TRANSFER the old
db. Saves lot's of headaches, and takes 10% of the time ;)
REM: Always keep a proper documentation of a db's segment/device scheme
since you have to use *exactly* the same (or lager) allocation scheme if
you want to restore from a dumpfile.

Mit freundlichem Gruss,

Peter A. Sang
SANG Computersysteme GmbH * Kruppstr. 82-100 * 45145 Essen * Germany
T: +49-201-82020-0 * F:-40 * http://sang.net * mailto:pesa@sang.net
* Microsoft Solution Provider - Internet/Intranet Specialist *

> -----Original Message-----
> From: Dale E. Reed Jr. [SMTP:daler@iea.com]
> Sent: Wednesday, December 31, 1997 9:20 AM
> To: RadiusNT@iea-software.com
> Subject: Re: RadiusNT with SQL server
>
> Endang Rachmawati Adwiarto wrote:
> >
> > >> Thanks for a prompt reply.
> > >> I execute the command and truncate the log, it reduces the
> > >> size but it didn't totally zero in the log size.
> > >>
> > >> For your information, the log is using 3 different devices.
> > >
> > >How close to zero did it get?
> >
> > it deleted 6/8 of the Log size.
> >
> > Since I'm using multiple devices, do you know how I can release the
> device
> > which used to be used and now available by Log Table?
>
> Unfortunately, I do not.
>
> --
> Dale E. Reed Jr. (daler@iea.com)
> _________________________________________________________________
> IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs
> Internet Solutions for Today | http://www.iea-software.com
>
> ----------------------------------------------------------
> RadiusNT Mailing List lists@iea-software.com