Most database administrators would tell you that restoring SQL tables using standard Microsoft methods can be an expensive process. Therefore, the impact of the numerous requests from employees on an organisation can be quite great and it will become clear later on. This is because SQL table restores is a time-consuming task for the IT employees who are responsible for them.
Usually, deleted or dropped SQL tables are restored by searching an existing backup or snapshot from previous backups of the entire database, the specific table is found and retrieved and then the active database is copied. It’s quite clear from this that the size of the database is the crucial decider in allocating time to carry out this task. When dealing with particularly large SQL databases, it can take several hours to extract and copy over the database server.
Every week several requests can come from employees from different departments depending on the size of the organisation. Almost every department uses certain parts of the database. This can include the research and development, sales or finance departments. Important tables are deleted, sometimes accidentally or other times because it is assumed that they are no longer needed. It’s a particularly grim realisation when they find out that these tables entries are actually linked to other tables and therefore all the calculations no longer work. So it’s no wonder that the employee is unnerved when they have to contact the DBA with a request for immediate help.
You can now quickly and easily check the costs that arise when a SQL DBA is tasked with requests for a full recovery by inputting the request parameters into the SQL Calculator. Simply enter the average amount of recoveries incurred, hours of work required for the provision of the second server, cumulative hours for the actual recovery, employee hourly salary and the average downtime costs and you will receive the (very shocking) cost to your organisation.
For example, imagine that you are dealing with a DBA for on the average salary of £15 per hour, there are 10 tables to be restored and this requires the provision of 2 hours whereby the actual recovery time is 45 minutes and the downtime costs are £1,500 per hour. This would end up costing your organisation £1,161,187.50 per year just for these tasks. This also accounts for an average of 4 requests per month which have to be turned down because DBAs don’t have the time to fulfil them. Keeping this in mind, you can input your own values and send the detailed results to your email address. It quickly becomes clear that a specialised tool which enables you to drag and drop copied tables from a SQL backup over to an active server makes the process much easier and cost-effective. From mid-November, Ontrack PowerControls for SQL will be the first product of its kind on the market to offer this time- and cost-saving functionality.
Find out how much table restores are costing your organisation with our SQL Calculator.