Problems with Call Consolidation

Kurt Schafer ( (no email) )
Thu, 31 Jul 1997 09:06:02 -0400

OK, after some SQL maintenance work, the Consolidation routine no longer
returns an error when trying to run it from the BATCH tab. (was a problem
with the MSDB database)

Problem, when I run it it says it processed 1 calls and when I check random
SA's of accounts which I know had call activity nothing shows up under
their call history. Likewise when I hit the OK button after the '1 calls
processed' dialog box the Emerald client goes into lala land.

I'm wonderring if it's a problem that the call table is just too darn
large. Due to the problems we've had getting the Consolidation procedure
into the DB and then running it, the Calls table has been accumulating
entries for the past month. Theres probably in excess of 300000 rows in

Looking at the actual routing it looks like it's just a SELECT which I
assume returns the row data to the Emerald client (or SQL server) for
additional processing. I'm going to leave the client program run and see if
it actually manages to struggle through but if you have any suggestions in
the meantime I'm open.


- Kurt