This is
new feature given in LCS which is self-service action that can be used as
part of Data Application Lifecycle Management. No more depending on MS or
raising support ticket.
Below are
the ways you can do this
- Refresh database : https://docs.microsoft.com/en-us/dynamics365/unified-operations/dev-itpro/database/database-refresh
Data elements that aren't copied during refresh
When refreshing a production
environment to a sandbox environment, or a sandbox
environment to another sandbox environment,
there are certain elements of the database
that are not copied over to the target environment. These
elements include:
·
Email
addresses in the LogisticsElectronicAddress table.
·
Batch job
history in the BatchJobHistory, BatchHistory, and BatchConstraintHistory
tables.
·
SMTP
password in the SysEmailSMTPPassword table.
·
SMTP
Relay server in the SysEmailParameters table.
·
Print
Management settings in the PrintMgmtSettings and PrintMgmtDocInstance tables.
·
Environment-specific
records in the SysServerConfig, SysServerSessions, SysCorpNetPrinters,
SysClientSessions, BatchServerConfig, and BatchServerGroup tables.
·
Document
attachments in the DocuValue table.
·
All users
except the admin will be set to Disabled status.
·
All batch
jobs are set to Withhold status.
- Export a database : https://docs.microsoft.com/en-us/dynamics365/unified-operations/dev-itpro/database/export-database
Data elements that aren't exported
When you export a database backup from an
environment, some elements of the database aren't exported in the backup file.
Here are some examples:
·
Email
addresses in the LogisticsElectronicAddress table
·
Batch job
history in the BatchJobHistory, BatchHistory, and BatchConstraintHistory tables
·
SMTP
password in the SysEmailSMTPPassword table
·
SMTP
Relay server in the SysEmailParameters table
·
Print
Management settings in the PrintMgmtSettings and PrintMgmtDocInstance tables
·
Environment-specific
records in the SysServerConfig, SysServerSessions, SysCorpNetPrinters,
SysClientSessions, BatchServerConfig, and BatchServerGroup tables
·
Document
attachments in the DocuValue table
- Import a database : https://docs.microsoft.com/en-us/dynamics365/unified-operations/dev-itpro/database/import-database
Data elements that require attention after import
Specific activities must be completed when you
import a database backup into a sandbox UAT environment. Here are some
examples:
·
Make sure
that email capabilities are correctly reconfigured or turned off, according to
your requirements.
·
Make sure
that integration settings are turned on or off, according to your requirements.
·
Make sure
that Application Object Server (AOS) servers are added back to required batch
groups.
·
Make sure
that system Help and task guides are reconnected.
·
Make sure
that batch jobs are set to a status of Waiting.
·
Make sure
that users are re-enabled.
- Database point-in-time
restore (PITR) : https://docs.microsoft.com/en-us/dynamics365/unified-operations/dev-itpro/database/database-point-in-time-restore
Above is
helpful...
