Thank you but once again, I'm simply trying to find a way to tell the Call Sweet to not attempt to write and/or retain as much data to the database so that it does not fill up. This in of itself should not have anything to do with Avaya or the database engine.
It is, but if I can just configure Call Sweet to not retain as much information, the MS SQL limitation would not be an issue.
If I could just tell Callsweet to retain one or two less days of data, that may solve our problem.
Hello all,
We have an Avaya phone system with Datel Call Sweet. We have had a persistent issue in which Call Sweet will simply stop tracking calls in the middle of the day. We have determined it is likely due to the 4GB limit per database on the SQL Server 2005 engine it is running on as I see...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.