Keeping your Data Repository in Top Health. By: Ian Proffer MUSE Session 305. About the Presenter & Acmeware. This is our 11 th year at MUSE! Acmeware’s founder led the development of the DR while working at MEDITECH We work exclusively with the MEDITECH DR
By: Ian Proffer
MUSE Session 305
Objects within the SQL Server instance
Similar look and feel to SQL Server Enterprise Manager
Transfer Logs should be regularly monitored, though most errors are also reported to the DR Module
Manage connection threads and view thread activity
Connection Threads Status
New feature: main menu selections are repeated here
The Master Background Job is the main job all DR transfers and controls the start of the file maintenance routines.
Messages here are the same as File Maintenance
The File maintenance job clears out the storage history on the size of the database and the log files.
The Status screen shows file maintenance and purge status by module.
View of the current status of the Master Background Job.
Example of a LIVE environment with several background jobs
These jobs should be monitored daily
Enter ALL to get a list of pending activity by module, or…
Lookup and specify a specific module or modules
Select one or all modules, enter date range and click on summary.
Click here to return to Summary page
Select download folder here and click OK.
Open it when you’re done.
An entire module or specific tables can have an IL performed to reload data into a table from the NPR data structure.
Why do it?
You can manually check each table too…
Some things to remember:
So what do I do with this?
How we manage error logs and submit issues to MEDITECH:
SQL Reporting Services Report – Error Status and Detail
How we leverage RowUpdateDateTime: spGetTableStatistics
Is a table receiving updates as frequently as we expect?
What about ring release updates?