Follow

GiftWorks Pro-Automatic Aggregate Update

Certain areas within this article do not apply to GiftWorks Anywhere Pro. These areas will be notated.

What is the automatic aggregate update?

This is an automatic update that is scheduled to run every morning at 1:00. It updates aggregate information for each donor such as current year giving, prior year giving and more. This is one of the changes with GiftWorks Pro that allows GiftWorks to perform well with customers that have a large number of donors and donations.This information is also kept up-to-date as users work in GiftWorks during the day. The automatic job ensures the aggregate information is correct at the end of a calendar year or fiscal year.

Why is my next scheduled aggregate update in the past?

When you create your GiftWorks database, GiftWorks schedules an automatic aggregate update to run. The next run time is scheduled for the following morning at 1:00 AM local time. Each time the job runs, it re-schedules the job again for the following morning. Here are some possible scenarios why the next scheduled aggregate update is in the past: In the event that the job does not run at the scheduled time, it may not be re-scheduled and may not continue to run. In order for the job to run, your SQL server must be running at the specified time. If it is not, then the job will not run and re-schedule itself. Another scenario is if the database has been restored from a backup where the next scheduled aggregate update is in the past. The solution to update the next scheduled aggregate update is to disable/enable the aggregate update. To see the steps to disable/enable the aggregate update, see How to disable/enable/re-enable the Automatic Aggregate Update below.

Why is a service required by GiftWorks not running, and how can I fix it?

The service that is required by GiftWorks is a SQL Server service called the Service Broker. This service handles the scheduling and running of the Automatic Aggregate Update. The most common reason that the service is not running or disabled is due to a restored database. There are some technical reasons behind why Microsoft disables the service in a restored database, but it needs to be re-enabled in order to refresh the aggregate information nightly. To see the steps to re-enable the Service Broker, see How to re-enable the Service Broker below

*This does not apply to GiftWorks Anywhere Pro

What should I know about restoring a GiftWorks Pro database?

To see some additional steps when restoring a GiftWorks Pro database, see Additional steps when restoring a GiftWorks Pro database below.

*This does not apply to GiftWorks Anywhere Pro - If you need to restore a GiftWorks Anywhere Pro database, please contact Customer Care

 

Additional steps when restoring a GiftWorks Pro database

GiftWorks uses the SQL Server Service Broker to schedule a daily job that keeps donor aggregate information up-to-date. When restoring a GiftWorks Pro database, SQL Server will disable the Service Broker by design. There are some technical reasons why Microsoft does this, but in the end you will need to re-enable the Service Broker so GiftWorks can continue to run the schedule job each morning. To see the steps to re-enable the Service Broker, see How to re-enable the Service Broker below

How to re-enable the Service Broker

*This does not apply to GiftWorks Anywhere Pro If you are using GiftWorks Anywhere Pro, please scroll down to the How to disable/enable/re-enable the Automatic Aggregate Update section of this article

There are two ways to re-enable the Service Broker and for either method you will need to ensure that everyone is signed out of GiftWorks. The first method is through a query. Open a new query window and enter the following SQL statements: USE master; GO ALTER DATABASE [your-database-name] SET ENABLE_BROKER; GO This should complete quickly but if it does not and continues to run then someone (GiftWorks or another Query window) is still connected to the database. This command requires an exclusive lock on the database. To ensure an exclusive lock you can run the following commands: USE master; GO ALTER DATABASE [your-database-name] SET SINGLE_USER WITH ROLLBACK IMMEDIATE; GO ALTER DATABASE [your-database-name] SET ENABLE_BROKER; GO ALTER DATABASE [your-database-name] SET MULTI_USER; GO Please Note: This will disconnect other processes and if someone is using GiftWorks they could receive errors. The second method is by editing the properties of the database. You can right click on the database and select properties to show the available options for the database.  

Click the Options page and scroll down until you see the Service Broker option. Change the value to True and click OK. After the Service Broker is enabled you will need to sign into GiftWorks and re-enable the Automatic Aggregate Update. 

How to disable/enable/re-enable the Automatic Aggregate Update

Open and sign into GiftWorks.

Go to Settings / Tools, Updates and Integration

To disable the Automatic Aggregate Update Click the "Enable Automatic Aggregate Update" link to enable the scheduled job.

To enable the Automatic Aggregate Update Click the "Disable Automatic Aggregate Update" link to disable the scheduled job.

To re-enable the Automatic Aggregate Update Click the "Disable Automatic Aggregate Update" link to disable the scheduled job. Click the "Enable Automatic Aggregate Update" link to enable the scheduled job.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

Powered by Zendesk