03-11-2009 02:03 AM
Our SQL keeps peaking sometimes to 100% on all processors, the memory is about 1.5Gb(Which is no problem with 8Gb memory). And then everybody complaints that ACT is slow. We configured the SQL that it may just use 2 processors instead of all 4, but its keeps using all the processors. What can we do to limited the amount of processors to use?
We updated to SQL SP03 but that doesn’t give the expected improvement. A few months ago the server worked fine and we didn’t change anything (except the windows updates). But one day we noticed the problem. We have a HP DL580 (4 x 1,9Mhz Xeon processors, 8 GB memory and SCSI 10000rpm disk). This system should be fine to use act with 25 people, I think. A lookup works fine, but when we attach a file into ACT (as link) it takes up to 15sec before it is done. So we lose a lot of time when we attach files. In the folder attachments are about 280.000 files and has the size of 15Gb. Is there a limit about the amount of files and the size of this folder? The Dbase is around 1Gb. We scheduled a maintenance of our dbase every night. Can we install the SQL monitoring and configuration tools from the complete SQL. The SQL which comes with ACT has almost no tools to change or monitoring. Can we find the password what ACT uses to connect to the SQL?
Is there also a tool to change the locations of the linked files? We upgraded from ACT6 to ACT9 (2 years ago) and then all our linked files are copied to the attachments map. These files are still on the network and we would like a link back to the network files and remove these files in the attachments folder. So we can reduce the size of this map.
03-18-2009 08:43 AM
Restart SQL Server (ACT7) service. If that improves the performance, you can create a Windows task to restart the service nightly or weekly.
ACT! SA Password Utility
The ACT! SA Password Utility provides organizations with direct, local access to the ACT! SQL instance by exposing the SA password. This utility is designed for those organizations that need third-party advanced back-up support, which requires an SA password. Customers may also find the SA password useful for querying database tables for custom reporting and data extraction using third-party tools such as Crystal Reports.
For more information, call 866-903-0006
03-19-2009 12:44 AM
We shut down the SQl every night, take our backup and restart the SQL. This drops the use of memory (which is no problem). But everyday the SQL keeps peaking to the max of all processors. I've put in a printscreen of the peaks. And at that moment everbody has to wait. When we browse true records there is a delay of 5 to 10 seconds. Is there somebody who has the same problem? I hit the "solution" button by accident, but this is not solved.