Browse By Category
Accounts (1)
Actions (6)
Alerts (3)
Client Form (1)
ClientView (14)
Configuration (1)
Contact Form (2)
Contacts (4)
Custom (1)
Custom Database (3)
Display (1)
Document Imaging (3)
Documents (3)
Errors (3)
Infrastructure (5)
Installation (4)
Interfaces (23)
Labels / Envelopes (2)
Letters (2)
Logon (1)
MSDE (2)
Opportunities (1)
Options (1)
Outlook (26)
Performance (3)
Program Use (8)
Reports (2)
Rule Builder (1)
Spreadsheet Import (4)
SQL (7)
TAPI (1)
Tech Support Note (1)
Templates (4)
Troubleshooting (1)
Upgrade (4)
Videos (1)
Vista (2)
VPN (1)
Word (8)
Worldox OEM (1)
 
 
Audit Log – Manage your Junxure backup space
3/9/2010
1994 views
The main cause of Junxure database growth is the Audit log that you can view from Database Tools ->Data Cleanup and Correction -> View Edits. This is a log of all data that has been changed in Junxure, including where and when the changes were made and by whom.  For example: if a user changes a phone number in a contact record, the audit log will make an entry for the change, storing the old value and the new value. Over time, this can become a very large log, especially when you have used J  
Junxure is slow on actions tab with Goldmine converts
7/3/2008
1268 views
If you find that an install that the original data came from a goldmine conversion, there is a mode of operation that can fix this. Why does this happen? Sql stores large text fields in the table, unless they are over 8K each.  The sql has to store the data in a Large Object Table (LOB).  When you try to access a query, like we do for the actions grid, it has to do 3 lookups for each action record.  Because of the way that Goldmine conversion haveHUGE action fields, when you go to somewhere in the program that returns actions, performance is very very slow. How can I  
Junxure Performance Monitor
6/23/2009
1235 views
The checks the status of your SQL Server by tracking 4 SQL performance counters: Total Server Memory  This indicates how much memory SQL Server is currently using.  This counter should never exceed the Target Server Memory. Target Server Memory Indicates how much memory SQL Server would like to have in order to operate efficiently.