We've actually done some custom installations for larger customers to
put
the calls table into its own database, to prevent it from causing
problems
with the Emerald database. There isn't any reason why you couldn't do
that
with the calldetails as well. Just create the new database, and fully
qualify the objects. For Example, if you create a new DB called
Emerald2,
and created the CallDetails table in there, you would need to modify the
trigger to insert into Emerald2..CallDetails rather than just
CallDetails.
> I have a question on the trigger and exactly when it is used. Are the
> records inserted each time the calls arrive? Or could this be scheduled to
> run as a scheduled task nightly?
The trigger is ran at the exact moment the record is inserted (and one
for
each record inserted). It can be scheduled, but its not an exact art
and
requires additional modifications beyond just running a couple of
commands.
> Select @ast=i.AcctStatusType From inserted i IF @ast = 2 BEGIN Insert INTO
> CallDetails Select DateAdd(Second, 0-i.AcctDelayTime, i.CallDate),
Just fully qualify CallDetails here with the name format of:
Database..Table
-- Dale E. Reed Jr. (daler@iea-software.com)_________________________________________________________________ IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs Internet Solutions for Today | http://www.iea-software.com