Re: [Emerald] Please help, Questions on Emerald & SQL....

Eric ( )
Sun, 25 Jul 1999 15:57:51 -0400

Thanks! I will give this a go and let you know if I have any problems.
I don't know if you caught my earlier post "[Emerald] SQL Transfer
question...", When we transfer the Emerald DB to a new one, the data used
is significantly lower on the new DB than the old. Any ideas on this?
Thanks again,
Eric Jensen

At 12:15 PM 7/25/99 -0700, you wrote:
>Eric wrote:
> >
> > 1) Is it possible to set the "Permanent Extension" to default to 15? I
> > checked in the "MasterAccounts" table at "OverDue" and tried to change the
> > default to 15 but it did not reflect the change in Emerald when adding new
> > users.
>In the Emerlad Admin, Client Config section, you can set the defaults
>for the Default Export, Extend, and Limit (the last two are the temp and
>perm extend).
> > 2) In Emerald Admin, we have had to set the "Default Extend" (which sets
> > the temporary extend) to 15 and the "Default Expire" to 15. We have found
> > that if these are not set this way, then when you add users, a "Pro-Rate"
> > charge is added to the account, which we do not want. The way we pro-rate
> > is based on the week of the month ($5.00 per week), and if there is a way
> > for us to change Emerald to do this, then that is great. My question here
> > is... Can anyone see a potential problem with setting these values
> > ("Default Expire" & "Default Extend") each to 15 in the Emerald Admin?
>The Default Expire sets the Expire/BilledThru to that many days after
>today. Its essentially giving them that many "free" days. To avoid
>the pro-rate, you could use anniversary billing. Emerald will not do
>the weekly pro-rate.
> > 3) In the new Emerald, the way taxes are applied is different than the
> > older versions. When we upgraded, we found that all of our business
> > accounts were not set to taxable. Does anyone have a script that checks the
> > services and then modifies the "Taxable" field under "MasterAccounts" if
> > the Services matches at taxable service in the "AccountTypes" table, or
> > something like that. This one is not a 3 alarm fire, we only have about
> > 1000+ business accounts, and to go through each one and check taxable
> > wouldn't be a big deal.
>You could use a script like this:
>Update ma
>Set Taxable = 1
> From MasterAccounts ma, SubAccounts sa, AccountTypes at1
>Where ma.CustomerID = sa.CustomerID
> and sa.AccountType = at1.AccountType
> and at1.TaxID > 0
> > 4) After running a few scripts to change the dates for "PaidThru",
> > "maExpiredDate", and "OverDue", the logs are getting full, and truncating
> > the transaction log doesn't seem to clear it out. What is the SQL script to
> > clear out the logs, and are there any dangers in doing this once in a
> while?
>You probably need to run a CheckDB and then re-calc the size of
>the DB.
>Dale E. Reed Jr. Emerald and RadiusNT
>IEA Software, Inc.
>For more information about this list (including removal) go to:

For more information about this list (including removal) go to: