Database Archives - Datarecovery.com

Microsoft SQL Server Database Recovery

Mike Katich — Fri, 20 Nov 2020 14:30:56 +0000

Our data recovery customers often ask that we target their databases, and Microsoft SQL Server databases are among the most frequently requested files. In many cases, a SQL Server database is the only important thing on a drive or server — clients don’t need anything else, and they ask our engineers to do anything and everything possible to get these critical files up and running again. As a result, we’ve developed some specialized methods for SQL Server recovery, including key software tools, and we’re always looking for ways to improve our processes.

There are a few factors to consider when planning Microsoft SQL Server data recovery. SQL Server can be very sensitive to any issues such as bad sectors, mis-aligned or stale data. The databases can include large files, which increases the risk associated with recovery — any small issue in the recovered data will affect the entire database. Even with a 100 percent clean recovery, SQL Server may have trouble interpreting the recovered data if the database wasn’t shut down correctly (this problem has subsided somewhat with new revisions in recent versions of the software).

A database that will not attach — or that reports numerous errors when accessing data — is essentially useless to our clients. Our No Data, No Charge policy covers this situation, so we take the necessary steps to provide recovered database files that our clients can reattach and use cleanly. The goal is to allow them to easily reintegrate the data into their systems. SQL Server functions with a variety of front-end applications, however, so we are not able to provide full reintegration support.

Different Configurations and Microsoft SQL Server File Formats

In our laboratory, we work with hundreds of SQL database configurations due to the enormous popularity of the software. We often find that our clients run SQL Server on RAID systems, but it is not uncommon to find the software on standard consumer computers. Common versions of SQL server treated in our laboratories include:

SQL Server 7 (1998)
SQL Server 2000
SQL Server 2005
SQL Server 2008
SQL Server 2008 R2
SQL Server 2012
SQL Server 2014 (12.0)
SQL Server 2016 (13.0)
SQL Server 2017 (14.0)
SQL Server 2019 (15.0)
All Future Versions

In the paragraphs below, I’ll go a little further in-depth into our processes for the more difficult cases, but first I’ll attempt to provide a little background info on the actual database files associated with SQL Server.

The critical file types associated with SQL Server are MDF and LDF files (and rarely NDF). Both are required for a functioning database. The MDF file is the primary database file, and the LDF is the log file. The LDF records past transactions that occurred which allows for rolling back actions or recovering from problems since last backup, and it helps to guarantee data consistency. Generally the MDF file is the larger file, but we have seen that sometimes the LDF is larger (this depends on configuration and usage). Database backup files are generally BAK extension.

In most cases, recovered SQL Server database files test perfectly fine, but if the recovery was particularly difficult or there was significant damage to work around, we’ll often see a few issues arise. These can manifest in different ways. The database might fail to attach or show errors upon querying data. In some cases, we’ll simply find bad data within the raw files, at which point we’ll need to dive a little deeper to figure out what’s going wrong.

Depending on the case, we may need to go back to our physical data recovery procedures to try to get a better clone of the original media. If the SQL server database files were located on a RAID, we’ll have to adjust the RAID recovery to get the cleanest possible extraction from all of the drive members. This is where our in-house software tools come into play, as these tools allow us to fill in gaps of data in the SQL Server MDF and LDF files with the correct data whenever it can be found elsewhere (not in the original recovered file).

In the case of a RAID, where multiple drives have failed at different points, it may allow us to use small parts of the normally undesirable “stale” drive to this purpose. In other situations, since we are often able to find different versions of similar database files among the data, we can point our automated tool to several versions and it will piece together the best possible result with the most recent data by replacing bad sectors with the missing data from another file. We will do what it takes to get the best result, and sometimes the process can take days (we cut turnaround times by any means necessary, but the quality of the data recovery is always the top priority.)

Should I Use SQL Server Database Recovery Software or Repair Utilities?

For the IT professional dealing with a damaged SQL Server database, there are plenty of commercial tools advertised as capable alternatives to a professional SQL server database recovery service. I’d recommend against these types of utilities, however, based on the issues that often occur in a fairly typical recovery. Basic software isn’t enough to get a clean recovery, and all of these tools require access to data in order to work. That’s usually a security risk.

Beyond that, these tools will rarely return a database that attaches properly and presents usable data. Stored Procedures and Views can be dumped (these are often required by software systems using the database). Table rows are often slashed in a rough fashion, as the utility does what it needs to do to create a functioning database without taking a real look at the data. There’s simply no ability for logical decision making, which will lead to usability issues.

Of course, some SQL Server database repair tools will function as a last resort, but they’re best suited for use by knowledgeable professionals. A capable data recovery service will give you better, safer, and more secure results. If you are considering data recovery service with SQL Server data, please let us answer your questions – call 800.237.4200.

The post Microsoft SQL Server Database Recovery appeared first on Datarecovery.com.

The Ashley Madison Leak: What Information Was Released?

Ben Carmitchel — Thu, 27 Aug 2015 20:05:13 +0000

The Ashley Madison data leak is unquestionably the most high-profile IT security event of the last year, and members of the website face serious repercussions. Ashley Madison advertises as “the world’s leading married dating service for discreet encounters,” but that discretion was compromised as hackers released about 30 gigabytes of user data, including email addresses, names, and even GPS coordinates (likely collected from mobile users).

The leaked information came from a MySQL database, and many of the fields are fairly self-explanatory. “eye_color,” for instance, gives the user’s eye color (as input by the user when signing up for an Ashley Madison profile). For many accounts, some fields are left blank.

Credit card information is stored in a separate area, and most hackers will not be able to definitively link usernames with payment information. Furthermore, the leak did not contain complete credit card numbers, so payment information should be safe; even so, we would advise Ashley Madison users to contact their card providers and request a re-issued credit or debit card.

The Ashley Madison database contains the following fields—

Table: aminno_member_email

Field	Description
pnum	The record’s primary key.
email	The account email address.
isvalid
html
optin	Whether or not the user opts in to the Ashley Madison newsletter.
notify_newmail
notify_newmember
notify_login
notify_offer

Table: member_details

pnum	The record’s primary key.
eye_color	User’s eye color.
hair_color	User’s hair color.
dob	User’s date of birth.
profile_caption	User-generated caption, visible on account profile.
profile_ethnicity	User’s self-identified ethnicity, expressed as a number.
profile_weight	User’s weight, visible on profile.
profile_height	User’s height, visible on profile.
profile_bodytype	User’s body type, expressed as a number.
profile_smoke	Whether or not the user smokes. Visible on profile.
profile_drink	User’s drinking status. Visible on profile.
profile_initially_seeking	Type of relationship user is initially seeking, visible on profile.

Table: member_login

pnum	The record’s primary key.
username	User’s username.
password	User’s password (these are encrypted).
loginkey	Login keys are unique to each user, authenticating the user for logout.
notify

Table: am_am_member

id	User id number.
createdon	Date and time the account was created.
createdby	User who created the account.
updatedon	Date and time (to second) the account was last updated.
updatedby	User who updated the account.
admin	Whether or not the user has administrative status in the system.
status	User’s relationship status.
account_type	Type of account.
membership_status	User’s membership status.
ad_source	Tracks site advertising.
profile_number	User’s profile number.
nickname	User’s nickname.
first_name	User’s first name
last_name	User’s last name.
street1	User’s street address.
street2	Second line of user’s street address (if applicable).
city	City listed in user’s address.
zip	Zipcode listed in user’s address.
state	State listed in user’s address.
latitude	User’s location latitude.
longitude	Longitude of user’s location.
country	User’s country of residence.
phone	User’s primary phone number.
work_phone	User’s work phone number .
mobile_phone	User’s mobile phone number.
gender	User’s gender.
dob	User’s date of birth.
profile_caption	User-generated caption, visible on account profile.
profile_ethnicity	User’s self-identified ethnicity, expressed as a number.
profile_weight	User’s weight, visible on profile.
profile_height	User’s height, visible on profile.
profile_bodytype	User’s body type, expressed as a number.
profile_smoke	Whether or not user reports smoking.
profile_drink	Whether or not user reports drinking.
profile_initially_seeking	What the user is initially seeking, expressed as a number.
profile_relationship	User’s relationship status, expressed as a number.
pref_opento	Type of experience the user says he or she is willing to try (or “open to”), listed as numbers.
pref_opento_other	What the user hopes a match will be open to
pref_opento_abstract	User-written statement of what the user is willing to participate in.
pref_turnsmeon	Items that the user says he or she is interested in. Expressed in numbers.
pref_turnsmeon_other	List of things that the user wants a match to be interested in. Expressed in numbers.
pref_turnsmeon_abstract	Written description of the user’s “turn-ons.”
pref_lookingfor	Attributes the user is looking for in a match/dating experience.
pref_lookingfor_other	List of attributes the user hopes a match is looking for.
pref_lookingfor_abstract	User’s description of a preferred match.
main_photo	User’s uploaded photo.
security_question	User’s security question.
security_answer	Answer to user’s security question.

This is a complete list of all of the fields in the MySQL portion of the database. However, several of the fields use numerical codes to indicate a selection from the user. “profile_relationship” specifies the relationship status of the user as follows:

1: “Attached Female Seeking Male”
2: “Attached Male Seeking Female”
3: “Single Male Seeking Female”
4: “Single Female Seeking Male”
5: “Male Seeking Male”
6: “Female Seeking Female”

The “pref_opento” field contains a number that correlates to one of the following:

1: “Threesome”
3: “Being Dominant/Master”
4: “Being Submissive/Slave”
6: “Bondage”
7: “Conventional Sex”
11: “Fetishes”
14: “Nothing Kinky”
15: “One-Night Stands”
17: “Role Playing”
18: “Sex Talk”
19: “Spanking”
21: “Experimenting with Tantric Sex”
22: “Transvestitism”
23: “Experimenting with Sex Toys”
23: “Exploring with Sex Toys”
26: “Aggressiveness”
27: “Blindfolding”
28: “Bubble Bath for 2”
29: “Cuddling & Hugging”
30: “Curious – Domination”
31: “Curious – Submission”
32: “Dressing Up/Lingerie”
33: “Erotic Movies”
34: “Erotic Tickling”
36: “Extended Foreplay/Teasing”
37: “Gentleness”
38: “Good With Your Hands”
39: “Kissing”
40: “Light Kinky Fun”
41: “Likes to be Watched/Exhibitionism”
42: “Likes to Give Oral Sex”
43: “Likes to Receive Oral Sex”
44: “Likes to Go Slow”
45: “Lots of Stamina”
46: “Open to Experimentation”
48: “Sensual Massage”
49: “Sharing Fantasies”
50: “Someone I Can Teach”
51: “Someone Who Can Teach Me”
52: “You Like to Cross Dress”

The “looking for” section also contains a number that correlates to the following:

1: “A Don Juan”
4: “Sense of Humor”
6: “Aggressive/Take Charge Nature”
9: “Average Sex Drive”
10: “Confidence”
11: “Discretion/Secrecy”
12: “Dislikes Routine”
14: “Good Personal Hygiene”
16: “Has a Secret Love Nest”
17: “High Sex Drive”
18: “Imagination”
19: “Likes Routine”
30: “A Professional/Well Groomed”
31: “Stylish/Classy”
32: “Casual Jeans/T-shirt Type”
33: “Tattoos”
34: “Body Piercing”
35: “BBW”
36: “Full Size Body”
37: “Muscular/Fit Body”
38: “Petite Figure”
39: “Slim to Average Body”
40: “Tall Height”
41: “Short Height”
42: “Long Hair”
43: “Short Hair”
44: “Girl Next Door”
45: “Naughty Girl”
46: “Bad Boy”
47: “Boy Next Door”
48: “Creative and Adventurous”
49: “Relaxed and Easy Going”
50: “Hopeless Romantic”
51: “A Father Figure”
52: “Not Possessive”
53: “A Good Listener”
54: “Good Communicator”
55: “Disease Free”
56: “Drug Free”
57: “Casual/Social Drinker”
58: “Seeking a Sugar Baby”
59: “Seeking a Sugar Daddy”
60: “Natural Breasts”
61: “Facial Hair”
62: “Tall, Dark and Handsome”

Datarecovery.com offers computer forensics services, which can help to verify the presence (or non-presence) of an individual’s information in the Ashley Madison leak. Given the nature of this leak, we offer this service exclusively to victims — not to spouses or other individuals. For more information, speak with a computer forensics expert by calling 1-800-237-4200.

The post The Ashley Madison Leak: What Information Was Released? appeared first on Datarecovery.com.

Datarecovery.com Offers Simple Way to Verify Ashley Madison Leaks

Mike Katich — Thu, 27 Aug 2015 17:33:56 +0000

Datarecovery.com, Inc., a world leader in computer forensics services, will provide customers with a simple way to verify whether their personally identifiable information has been made publicly accessible through high-profile security breaches, including the recent leaks from dating website Ashley Madison.

“This is one of the most significant Internet security breaches in history”

Hackers began releasing the Ashley Madison data to torrent websites and the Dark Web (hidden networks that require specialized software to access) in late July, starting with more than 10 gigabytes of stolen data. Last week, another 20 gigabytes of data was released. The files contain personal information for millions of users.

The leaks have garnered significant media attention because of the unique nature of the Ashley Madison website, which markets its services towards people in committed relationships who want to start affairs. According to multiple sources, the released information has led to divorces and other serious consequences for some users.

“It’s a major breach of privacy, and users need to know whether or not they were affected,” said Ben Carmitchel, President of Datarecovery.com. “We’re offering the first computer forensics service specifically geared towards the victims of this type of data security breach.”

The computer forensics experts at Datarecovery.com can independently verify if an individual’s information was released, and to what extent. Customers can request information by using first and last name, email address and other personally identifiable information. The service is only available to primary users of hacked websites — not their spouses or other individuals.

While several websites have been set up to search through the leaked data, Ashley Madison has quickly taken them down by issuing Digital Millennial Copyright Act (DMCA) notices. Many of the remaining sites only search through some of the leaked data, and all sites ask for users’ email addresses, opening up additional security concerns.

“This is one of the most significant Internet security breaches in history,” said Carmitchel. “Our service is intended to help the affected users protect their sensitive data and retain some degree of privacy.”

Datarecovery.com is a worldwide leader in computer forensics and data recovery services. With four locations in California, Illinois, Arizona, and Toronto, the company provides a variety of services to thousands of clients each year. Visit datarecovery.com for more information.

Contacts

Datarecovery.com, Inc.
Benjamin Carmitchel, CEO
602-635-2020
ben.carmitchel@datarecovery.com

The post Datarecovery.com Offers Simple Way to Verify Ashley Madison Leaks appeared first on Datarecovery.com.

Data/Media Conversion Technologies

Ben Carmitchel — Mon, 23 Jun 2014 10:08:15 +0000

Data conversion is the process of changing data from one format to another, or migrating data to and from various formats. Conversion is used to change data to the correct format to work with the system and software specified by the customer, or to convert data from an original application format to a more accessible form . The process of Media Conversion varies according to the situation. Different conversion methods are utilized according to cost and data accuracy.

There are various types of Media Conversion, including word processor conversion, file conversion, image conversion, data base conversion, and computer systems conversion.

Word processor conversion may be necessary when developing an application that needs to read and/or write various file formats. Word processor file formats are very complex and new formats are constantly being introduced, so the demand for conversion is high.

File conversion is just converting files to a different format. It may be necessary in order to view multiple file types without the related application. For instance, instead of having to buy ten different types of word-processing software to view ten different files, the files can be converted to fit one word processing system.

Image conversion may be used to gain access to the various image processing methods from your favorite application development environment. Some popular image formats are JPEG, Photo CD, PNG, PDF, and GIF. It may be necessary to convert an image to a different format in order to resize, sharpen, change color, or add certain special effects to meet your standards.

Data base conversion is needed to change any files saved in an out-of-date database to a more modern data base program. More modern databases are generally more convenient and dependable so the advantage of data base conversion is obvious.

Basically, there are two very general methods of conversion: data and media. In general, Media Conversion is extracting the files off of the source media, followed by backing up the files to the destination media. Two types of Media Conversion are media transfer and media migration. The reasons for media transfer may be to transfer archived data into a more convenient format or to save on cost of equipment, and media migration may be utilized for a greater storage capacity, a more reliable media type, less expensive media cost per GB or flexibility of media. However, a full Media Conversion can be much more complicated, possibly including processing the data well beyond just copying files to a different type of media.

The post Data/Media Conversion Technologies appeared first on Datarecovery.com.