Database administration has always been a demanding task, and even more so when recovering after a systems crash, incorrect maintenance or other events that lead to data loss. Sure, OfficeRecovery software products are here to extract what is left in the damaged database files and save the results to a number of SQL scripts. But what should one do next once the scripts with salvaged data are produced?
This is where the new feature of OfficeRecovery products comes in handy: introducing Database Creation Utility. The wizard breaks the deployment of recovered data into a few easy steps. It's not necessary anymore to study manuals with database-specific command line operators to perform a simple task of importing data. Database Creation Utility will do it in a few clicks in a neat user-friendly interface.
To give a better idea of how the wizard works, let us review a sample scenario of recovering a crashed Microsoft SQL Server database:
It's also worth noting that while Database Creation Utility simplifies routine tasks a lot, it is not the solution for each and every data recovery case and its use is optional.
Complex situations, when recovered database content may need pre-processing before deploying, may be better handled in manual mode. Such cases may involve splitting and/or filtering results of recovery, deciding whether to import deleted rows etc.
For such advanced procedures, SQL (DXL - Domino Extensible Language - in case of Recovery for Lotus Notes) scripts produced by OfficeRecovery utilities are still readily available. If, for example, there is a need of aligning the recovery process with local services for scheduled tasks – remember about the possibility of manual fine-tuning the scripts before execution.
No portion of this website may be reproduced without express written permission by OfficeRecovery
Copyright © 1998-2017 OfficeRecovery