You cannot generate an alarm when a user changes configuration in the database.  Database changes do affect the running process until a download is performed, so they do not have relevance to the alarm system, nor should they.  An alarm is for operators and should only be configured if a response is expected by the operator to resolve a process condition problem.

If you want to know when changes are downloaded, I would suggest having a reporting tool that indicates when downloads are performed by looking at the event chronicle.

You can set up a process history view event file with filtering to report that information. You could also potentially use an OPC A&E client like Plant Messenger, to subscribe to download events and email/text you when an event is detected.

If you wish to control database changes, I would start with security.  Make sure only those allowed to make database changes have the priviliges to do so; that means everyone doesn't log in or know the administrator password, but uses their own dedicated account that they are responsible for. 

Next, try enabling Version Control Audit trail. It will record all changes and enforce check in and check out. You can generate a report of all changes by date to determine when someone has made a change.