Keep Xelence responsive and running with SQL Server Always On
Also listed as: SQL Server Always On (CQRS)
What is it?
Xelence will support SQL Server Always On. Everyday reading and reporting can run on a synchronized copy of the database, while updates go to the main copy. Separating reads from updates like this is known as CQRS.
Why does it matter?
When one database server handles every screen, report and batch job, heavy reporting can slow down staff, and a single server failure can take the whole solution offline.
Steadier response times at busy periods for staff and constituents, and a solution that keeps running if one database server fails.
Getting it into your solution
- Needs an upgrade to the Xelence release
- Needs implementation work
Start thinking about
- Does your database environment use, or plan to use, SQL Server Always On?
- Which reports and batch jobs put the most load on your database today?
- When would a move to Xelence 10.0 fit your release calendar?
Terms used on this card
- Batch job
- A scheduled task that processes many records at once, such as nightly payments or file imports, without anyone clicking through each one.
- CQRS
- Short for Command Query Responsibility Segregation: updates and reads are handled separately, so heavy reading and reporting don't slow down updates.
- SQL Server Always On
- A Microsoft SQL Server feature that keeps synchronized copies of a database on more than one server, so the application keeps running if one fails.