By ITIL® from Experience ©
A large amount of data imported in an application is usually done by an administrator or a developer. It is seldom done by a user since it often requires elevated access permissions. These elevated permissions are there to reduce the possibility of inadvertently “messing” things up when using the application. A bulk data upload can be very risky for some applications. Loading bad data in applications that are driven by configuration data can result in making it inoperable.
One way application management specialists mitigates risks is by planning the change and using good release management practices. For example they:
- Backup the test environment
- Load data in the test environment to confirm that the result is as expected
- Schedule the load when the application is not in use by the business (in case the result is not as expected so that it can be restored from backup)
- Backup the application’s production data or database
- Upload the data
- Validate that the result is as expected –or- restore from backup
Given that every change has an element of risk, change management mitigates them by using standardized methods and procedures thus, a bulk data load is a change and requires a Request For Change (RFC). It also meets all aspects of the ITIL definition of a change.1
Nonetheless bulk data loads must be logged as changes if for no other reason than to help identify the source of application incidents caused by a new data import.
A bulk data load can be something that is performed on a regular basis and most often does not require coordination between multiple IT groups. It is therefore a great candidate for a standard change and steps similar to the ones above are a great foundation for a standard change.
- What is a change
- Is a reboot a change
- What is the content of a standard change
- Who should log the RFC
- Which CIs to load first in the CMDB
- Do we need an RFC to resolve a break-fix incident
Copyright 2012-2020 - ITIL® from Experience - Denis Matte