top of page

Let us recover your data.

If it's about getting at the data once available but now lost, the chances are we can do something about it. We've extracted an old patient information form a defunct electric medical records database server, saved customer data from corrupt e-Commerce systems, rebuilt data from unbuildable failed RAID arrays and more. We even partner with drive recovery companies to recover SQL Server data out of a dead hard drive. Give us a try and find out.

Here is what you can do now.


1. Stop.


This sounds counter-intuitive. You want to do something, and you feel like - the more tries you give, the less work the professionals will have to do so you save money. Sometimes that is true, but if you are that good - send us your resume and join the team. Vast majority of the time, the user attempting to perform data recovery without proper experience makes the matter worse. Our collective apologies if that's not what you wanted to hear, but it's the truth.


Let us give you an example - a customer experienced a data loss by unintended UPDATE. The customer found a .bak file and attempted to restore from it, overwriting the backup history in the process. If the customer didn't do that - it would have been a relatively simple job, retroactively taking tail log backup and then doing a point-of-time recovery using the STOP AT clause. We eventually got the data, but would have been easier (and cheaper) job if the customer did not attempt a restore. it is like a crime scene - you don't want to touch it.


2. Prepare a remote desktop solution for us.


One thing we are going to ask as a part of free initial consultation is to get on your system to diagnose what is going on. To take advantage of limited time available in the free session, we advise that you prepare an externally accessible desktop-sharing solution so that we can look at your database together while we are on the phone. 


3. If applicable, copy all pertinent files in an external hard drive or USB storage device for shipping.


This may or may not apply. If you have a production issue that needs resolution in minutes, not days, then naturally it won't make much sense to prepare external drives for transfer. However, if you have a non-urgent recovery project on hand - copying everything you have in an external hard drive and sending it to us would be of mutual interest, since transferring terabytes of data takes significant time, reducing your contract hours.


4. If there is a failed hard drive, isolate the failed drive and get it ready for shipping.


Needless to say, if there's a failed hard drive involved - we'd like to attempt a repair by our partners before attempting to recover database from it. Please identify failed drives and get them ready for shipping.


Ready? Call us at (844) SQL-FAST.



bottom of page