AXForum  
Вернуться   AXForum > Microsoft Dynamics AX > DAX Blogs
All
Забыли пароль?
Зарегистрироваться Правила Справка Пользователи Сообщения за день Поиск Все разделы прочитаны

 
 
Опции темы Поиск в этой теме Опции просмотра
Старый 12.10.2017, 16:11   #1  
Blog bot is offline
Blog bot
Участник
 
19,717 / 666 (62) +++++++
Регистрация: 28.10.2006
dennis365foroperations: It’s back! Batch job history clean-up is available (again)
Источник: https://dennis365foroperations.blog/...ailable-again/
==============

When batch jobs execute, their execution history is stored in the batch job history. This helps in monitoring and validating proper running of (recurring) batch jobs, their execution time and possible logs. However, with a lot of recurring batch jobs, especially those with a high recurrence, will generate a lot of batch job history entries. In addition to keeping the history notes clean and relevant, this feature also provides performance enhancements by eliminating the negative performance impact of having a large volume of entries in history tables, if left unmonitored for long periods of time.

Functionality to clean up the history of batch jobs was available in Dynamics AX 2012 and has now been re-introduced in Dynamics 365 for Finance and Operations. It is available in, and from, platform update 9. Before Platform update 9, you needed to delete the history on a job-by-job basis, which required extra time to cover all the wanted jobs.




Two new forms have been added to the System Administration workspace:
  • Batch job history clean-up
  • Batch job history clean-up (custom)
Regular versus custom batch job history clean-up options

The regular version of batch job history clean-up allows you to quickly clean all history entries older than a specified timeframe (in days). Any entry that was created prior to – will be deleted from the BatchJobHistorytable, as well as from linked tables with related records (BatchHistory and BatchConstraintsHistory). This form has improved performance optimization because it doesn’t have to execute any filtering.

The custom batch job clean-up form should be used only when specific entries need to be deleted. This form allows you to clean up selected types of batch job history records, based on criteria such as status, job description, company, or user. Other criteria can be added using the Filter button.




Источник: https://dennis365foroperations.blog/...ailable-again/
__________________
Расскажите о новых и интересных блогах по Microsoft Dynamics, напишите личное сообщение администратору.
 

Похожие темы
Тема Автор Раздел Ответов Посл. сообщение
patrickmouwen: Dynamics AX Retail: how to automate processes and interfaces in a combined way Blog bot DAX Blogs 0 23.12.2015 23:11
axinthefield: Optimizing AX Batch Performance - Batch Group Configuration Blog bot DAX Blogs 0 01.04.2011 13:11
axaptapedia: Batch processing Blog bot DAX Blogs 0 29.01.2009 17:05
wiki.dynamicsbook: Changes Made in Navision Attain 3.60 Blog bot Dynamics CRM: Blogs 0 02.09.2008 13:23
NAV Sustained Engineering Team Blog: How to Set Up Job Queue in Microsoft Dynamics NAV 5.0 Blog bot Dynamics CRM: Blogs 0 19.12.2007 15:30
Опции темы Поиск в этой теме
Поиск в этой теме:

Расширенный поиск
Опции просмотра

Ваши права в разделе
Вы не можете создавать новые темы
Вы не можете отвечать в темах
Вы не можете прикреплять вложения
Вы не можете редактировать свои сообщения

BB коды Вкл.
Смайлы Вкл.
[IMG] код Вкл.
HTML код Выкл.
Быстрый переход

Рейтинг@Mail.ru
Часовой пояс GMT +3, время: 04:49.
Powered by vBulletin® v3.8.5. Перевод: zCarot
Контактная информация, Реклама.