|
Advice for Companies with Sweet-CAD and Sweet-Field Data
by Kelly Rothlisberger, Product Analyst/Trainer
You never know which product (Sweet-CAD or Sweet-Field Data) is going to send its call information to the Sweet-Billing program first. Sweet-Field Data calls usually come into the UPLD schedule and Sweet-CAD calls usually come into a CADUPLD or similarly named schedule. So when Sweet-Billing personnel are reviewing the call information, they should run a report or EZ Review to:
1. Check to see if the PCR is there.
a) If the PCR isn’t there, you are viewing the Sweet-CAD call and you should not bill the call until the PCR is there. If a customer determines it still needs a PCR, they should wait 24 hours and review the list again. Some customers chose to move that call into a schedule called “Need PCR” (this must also be an upload type schedule or calls won’t merge). If you moved the call to a “Need PCR” schedule, then run a report 24 hours later that filters on that schedule to determine if the call from Sweet-CAD has merged.
b) If the PCR is there, then proceed to Step 2.
2. Check history to see if the Sweet-CAD information is there also.
a) If the Sweet-CAD information is also there, then bill the call.
b) If the Sweet-CAD information is NOT there, then users usually choose to leave the call there to wait for the Sweet-CAD information and review again in 24 hours.
If a call didn’t merge the data for Sweet-CAD and Sweet-Field Data, then the Sweet-Field Data call should be the one processed because it has contains the PCR; the Sweet-CAD call should be put in a holding bin schedule, which is typically called “NOTNEEDEDCAD” or something similar. This portion of the call has become reference only and should not be billed.
Planning for a New Server and Hard Drive Considerations
by Ann Bodensteiner, Product Lead, Support Services
You will need to consider the current size of your database when planning for a new server. You can find the size of your database in the Sweet-Billing program under “help” >> “about” on the “System Info.” tab.
When you move to a new server, you will have to install SQL to maintain the database. If the server has more than one hard drive or a partitioned drive, you will have to designate which drive you want SQL to store the database and backup files. This designation is made during the installation. If you have more than one drive, the “C:” drive is typically used for the operating system and temporary system files. The “C:” drive must have a minimum of 2 GB free space to allow for updates.
By default, the Sweet-billing program creates and stores two backup files representing the most recent two days anyone logged into the program. If you have a full version of SQL you can create a database maintenance plan that will backup the database at a scheduled time. The backup files are each about the same size as the database, so you need to multiply the size of your database by how many backups you wish to keep on the server and add one more for the actual database. This represents the minimum amount of space that will be required.
Make sure you have adequate media that will accommodate external backups considering the size of your database.
When you are in the planning process, please call Ortivus Support at 563-387-9338 with any questions. We have specific instructions for the installation of SQL. We are here to guide you and can provide documentation for a smooth transition.
|
