Go to Top

Dropped SQL table? A better solution has arrived!

The last few months, I’ve been writing about a common problem that exists in the DBA world: the request to restore a SQL table from a backup or storage-tier snapshots. Whether it is tackled by a SQL DBA, Developer, Consultant or “Jack of All Trades,” who supports SQL in addition to many other IT roles, these requests take time. Why? Because the native restore process, which is the most common way this issue is addressed, requires the entire database to be restored and the SQL Server to be present during the restore.

Hours of time are not the only thing at stake for the DBA. Because SQL is the foundation for many enterprise applications, we are usually talking about critical revenue application downtime, which can cost a company hundreds of thousands of dollars. Let’s look at what one small internal application restore request can cost an organization. Here are the factors:

  • 1 restore per week
  • 1 hour spent finding the available storage and SQL server resources to set up the restore
  • 1 hour to perform the full database restore
  • $45 an hour as the average labor rate for a DBA in your organization
  • $1,000 per hour cost of application downtime
    Total: $105,687

Have no fear. I’m thrilled to announce that a better, faster option is near! With an amazing group of Kroll Ontrack developers and input and testing from nearly 100 DBAs internationally (thank you Alphas, PASS MN and PASS worldwide!), we have developed a new granular search and restoration tool for Microsoft SQL – Ontrack® PowerControls™ for SQL. DBAs can now restore SQL tables without having to restore the entire database or use SQL to read the backups. This literally cuts the time spent restoring tables from hours to minutes.

Using Ontrack PowerControls for SQL, DBAs will no longer have to restore a database to get back one table. With simple drag and drop functionality, single tables can be restored from native SQL backups or storage tier/SAN snapshots to the desired environment. The SQL table content can also be previewed to verify the correct table is being restored prior to actually doing the work.

Ontrack PowerControls for SQL is a win-win for DBAs and the businesses they work for. A DBA can now say “yes” to restore and table copy requests they previously had to turn away, and they can do them in a fraction of the time, giving them the ability to get back to their planned activities. The business can reduce application downtime, do more thorough testing and development, and spend more quality time on strategic projects.

Pre-register for the free trial and get it the minute it becomes available

2 Responses to "Dropped SQL table? A better solution has arrived!"

  • Larry Chesnut
    12th March 2015 - 11:27 am Reply

    I am curious about your product and have some questions.

    1. How does your tool handle object level (table, or rows of a table) restore process avoids violating foreign key dependencies?

    2. Does your tool support filestream and\or filetable?

    3. With regards to only some rows being inadvertently deleted (not the table being dropped) could you provide some insight into how your tool can help?

    • Ben Blomberg
      27th March 2015 - 4:41 pm Reply

      Thank you for the questions.

      We do not create indexes or foreign key constraints on the tables we create during the copy operation. We identify foreign key relationships in tables prior to the copy and notify the user if foreign key relationships exist between the table being copied and any other tables in the database.

      Ontrack PowerControls does not currently support filestream/ filetable, but that is something that our development teams are reviewing for a future release.

      In regards to your question about only some rows being deleted. The current use case around this would be to copy the table to a new table name or database and performing TSQL queries between the restored table and the live table. The tool is able to find and restore a single table much faster than you can restore an entire database, so that part of the restore process becomes much faster.

Leave a Reply

Your email address will not be published. Required fields are marked *