Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Call sweet issues

Status
Not open for further replies.
Sep 20, 2017
3
US
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 the following errors all throughout the event viewer:

Code:
CREATE DATABASE or ALTER DATABASE failed because the resulting cumulative database size would exceed your licensed limit of 4096 MB per database.

Code:
Could not allocate space for object 'dbo.ErrorLog'.'PK_ErrorLog' in database 'SWEET_LOGGING' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.

Before you suggest that we migrate to a new SQL Server engine, I should say that we attempted to migrate to 2008R2 with a 10GB limit, but it did not appear to track any new calls so we rolled back. Also, we intend to migrate to a new phone system shortly anyway. Ideally within a few months we will not be using this system anymore.

Ideally what I need is this: some way to reduce the overall database size so that Call Sweet actually becomes usable. Is there a setting somewhere I can use to change the number of days worth of data that it retains? Thank you
 
So to make a long story short: the problem is neither the Avaya nor the Datel Call Sweet, it is a MS SQL limitation.
This limitation has always been there so the decision to go the cheap way pays off now, but you can cleanup the database with a SQL query.
I advise to go to this this forum and get your answer there from the SQL guru's.
 
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.
 
I'm with intrigrant, I read that error code on a spice site and seems to be SQL indeed.


________________________________________

Add me to LinkedIN

small-logo-sig.png

=----(((((((((()----=
Toronto, CAN
 
Freight-Brain said:
We have an Avaya phone system

which Avaya system?
saying Avaya without specifying system is like saying BMW without specifying Motorcycle, Car or Messerschmitt!


Do things on the cheap & it will cost you dear
 
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.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top