Technically there is no limit since they're stored in SQL these days. the last time I checked this the SA started getting kinda pokey around 70 or 80 rules in a table (i.e. it took a while to refresh and got sluggish). The call routing processing for inbound calls happens lickity-split, though, even with a bunch of rules in there.
I haven't tested this recently in a 3.1 implementation, however.
I believe we documented somewhere that we didn't reccomend more than 50 rules in a table back in 2.4.5 or thereabouts. Personally I'd question an implementation that needed that many routing rules (i.e. there's probably a better way to approach the problem). It was not designed to handle 100s of routing rules if that's what you're getting at.
Jeff Lindborg
Unity Technical Lead/Answer Monkey
Cisco Systems
lindborg@cisco.com
http://www.AnswerMonkey.net (new page for Unity support tools and scripts)
