jack

Templates are used as memory storage, like phones share templates a hold over from the early dfays when memory was $$$$$.

Template errors are an early warning of potential DB corruption. Often just cleaning up the templates is enough, although re-loads and/or ETAS involvement is possible.

It is interesting that you are seeing the majority of issues with 500 sets/tns, hmmm...

I always recommend frequent edd and audits on large scale changes, if nothing else reason for a smoke break

Since you are changing so many, I'd probably start with a 100 or and then do the edd .and audit and after your comfortable that the system is accepting the changes bump up the number of stations.

AQlso keep an eye on the audits the first pass should show duplicate and corrupt templates and the second pass should run clean. If it is not running clean on the second pass you might have bigger issues.

I usally run audits at least once per month for just day to day change activity and more often after larger changes. The systems seem to run smoother from it. I know alot of folkss that have never ran the audits, which I feel is just waiting for a problem.

One never knows what ills a particular database has suffered at the hands of either a brutual tech. or a not so sharp customer.

Let us know how this works out.

Jack

__________________
Dogs rollover Phones hunt