By using this web site, you agree to all terms and conditions for acceptable use.

ServiceLedger KnowledgeBase Knowledgebase Home Page > ServiceLedger > Technical | Contact Us

Search the Knowledge Base Browse by Category

ServiceLedger provides this content as-is for self help support purposes. ServiceLedger assumes no liability for any steps you take based on the directions in our knowledge base, and assumes that you have the knowledge to determine whether a given step is appropriate for your situation. Certain solutions can affect third-party software that ServiceLedger relies on or integrates with; it is your responsibility to consult with the documentation or publishers of such third-party software to understand whether any changes suggested here will have negative effects on other applications.

(T0012) How can I improve performance to address time outs and deadlocks?

Would you like to...

Print this page
Email this to a friend

Outlines steps necessary to truncate your database, and disable indexing service on your computer.  Back up your database before performing these steps:

  1. If you are using ServiceLedger 2008, ServiceLedger 2009, ServiceLedger 2009 R2, or ServiceLedger 2010, you should run history maintenance updates on at least a yearly basis, (monthly is recommended for companies with high volume.) These updates keep transaction history intact, but trim the audit trail and other internal history tables. To run a history maintenance update, run one of the following as a temporary update / one-time update.
    • history_maintenance - Keeps 6 months of change history
    • history_maintenance_90 - Keeps 90 days of change history
    • history_maintenance_60 - Keeps 60 days of change history
    • history_maintenance_30 - Keeps 30 days of change history
  2. Use the updater to run the temporary code of truncatekeepapp
  3. It is sometimes helpful to STOP your SQL Server and run the disk defragmenter on your system. It is crucial that you stop your SQL Server before defragmenting, as the database files will appear to be system files that cannot be moved if the SQL Server is still running.
  4. In recent versions of ServiceLedger, it can also be helpful to reindex the database tables. This can be performed under the Administration window, but may not work in all setups.
  5. If using Windows 2000, XP, or higher, consider disabling the indexing service on your computer.
    1. Start->Run
    2. Type in: services.msc /s
    3. Locate Indexing Service
    4. Right click, and select properties
    5. Change startup type to Manual
    6. Click Stop
    7. Click OK
    8. Close Services Window

From time to time we have seen corrupt performance counters cause issues. You can use the command below from Start->Run to restore them. Please do not run this without ensuring you have backed up your computer fully!

lodctr /r:perfstringbackup.ini

With the rise of brute-force attacks on MS SQL Server, ServiceLedger highly advises using a firewall at your internet gateway.  If you would like to see if such an attack may be incurring at the time of slow performance (the attacks can really slow your system down), please run the following from the command line:

netstat -an

If you observe many, many connections to or from port 1433 with an IP address that isn't in your network, you may wish to check that your firewall is operational.

Finally, you should verify that have at least as much physical RAM as is being used by your server, using the property sheet on My Computer to determine physical memory and the Task Manager to determine memory usage. If you are using more memory than your server physically has, ServiceLedger recommends that you either install additional RAM, reduce the load on your server machine, or install ServiceLedger's database on a different machine entirely.

Related Questions:


No attachments were found.

ServiceLedger KnowledgeBase Copyright © 2020
Powered by AcitveKB Knowledgebase Software