As long as you hear any strange clicking sounds from your hard drive, you should be concerned about your drive data. Any improper operation can destroy the data. So this article will tell you what to do and what not to do in this case.

As we all know, once a hard drive fails, all the data stored in this drive will tend to get damaged, such as corrupt Outlook PST, etc. One of the most common signals for hard drive failure is that drive is making strange clicking sounds. Hence, when you hear such clicking sounds from your hard drive, you should watch out for your operations. Here are 8 suggested do’s and don’ts.

8 Do's and Don'ts when Hard Drive Makes Clicking Sounds


1. Analyze the Sounds

First of all, you need to analyze the sounds in that there are many different hard drive sounds and many different situations. Some sounds may be normal sounds, some are from software or drivers, and some are owing to other hardware. Thus, you should firstly figure out if the sounds which you hear are the correct clicking sounds.

2. Back Up Drive Data

In addition, so as to protect your data from further damage or loss, you are better off backing up the drive data right away. You can select to back up them to another external hard drive or the cloud as per your preference.

3. Recur to Drive Repair & Data Recovery Service

Also, if you cannot confirm what you are suffering or you can ensure that the drive clicking sound is due to a mechanical fault, you need to take recourse to an expert drive repair and data recovery service.


4. Don’t Open It on Your Own

As what mentioned above, you should recur to professionals instead of trying DIY repair or recovery by yourself. On one hand, opening drive demands a cleanroom and specialized tools. On the other hand, if you lack related knowledge, your incorrect handlings will directly make drive recovery impossible.

5. Don’t Install Software on It

Moreover, at this time, you should never use or install any recovery software on the hard drive. Although there is much such software in the market, you shouldn’t trust in any readily. Running them on the drive can overwrite the data and make recovery far more difficult.

6. Don’t Freeze It

There are a lot of incorrect ways suggested on the Internet, like putting the drive into a freezer. However, freezing is not a good idea. It can short out the electrical components of a hard drive and directly result in drive corruption. In a nutshell, to freeze a hard drive can make case worse.

7. Don’t Knock It

Many users aren’t impatient and become angry when encountering any hard drive issues like clicking sounds. Thus they may apply physical force to the drive, hoping that the sounds can stop. However, no matter how angry you are, knocking a drive is not unadvisable way.

8. Don’t Move It While Running

When the drive is still running, you should not readily move it from one location to another. Hard drive is sensitive to shocks and movements, particularly when it is still running and malfunctioning.

Author Introduction:

Shirley Zhang is a data recovery expert in DataNumen, Inc., which is the world leader in data recovery technologies, including fix SQL Server and outlook repair software products. For more information visit

Be the first to comment

If your computer often restarts randomly somehow, you can refer to this article to figure out the causes and solve the problem easily.

Computer random rebooting could cause many problems. For example, if you are sending emails in the Outlook, but the computer suddenly restarts itself, then you will probably get a damaged Outlook. Data disasters are more likely to occur during random computer rebooting. Thus you should fix this error as soon as possible. Now let’s get started.

Computer Rebooting Problem

1 Software Issues

Software issue is a common factor that can result in computer rebooting. If the program is not compatible with your computer, then the PC will become very slow or even begin to restart itself. Therefore, if your computer gets into this trouble after installing new applications, you have to check this factor immediately.

2 System problems

Although Windows system tries its best to detect if there are any problems in the computer all the time, it doesn’t mean that it can find any issues successfully. For instance, if you delete system files by mistake and without realizing, then this error will probably happen without prompting. Thus if you have cleaned up the system files before the problem, you should call in a tool to check whether your system file is corrupt or missing.

3 Storage Device Problems

Hardware issues can always lead to this error as well. If the computer fails to respond to the operation in the device, systems are prone to reboot itself automatically. Thus if you meet up with this error, you can check the connection of the device firstly. If the error exists, you can make use of an inbuilt tool called “chkdsk” to fix the hard drive issues.

4 Computer Power Issues

Power supply plays an important role in normal computer working, especially in desktops. Power issues like power failure or power surge will trigger computer random restart problem too. Therefore, you ought to check the cables and even prepare Uninterruptible Power Supply (UPS) for your computer.

5 Virus Issues

Virus can do many terrible things. And it can also modify the settings that you have set before, or running malicious programs secretly. Thus you should select a reputed anti-virus application and update it regularly to prevent virus attacking

6 Memory Issues 

Random Access Memory (RAM) is a vital part of the computer which stores temporary data for computers. If it gets corrupt, then system will get compromised and reboot itself probably. So you can take following steps to check if your RAM is normal as usual.

  • Go to “Start” menu and enter “windows memory diagnostic” in the search window.
  • Then, the program named “Windows Memory Diagnostic (WMD)” will appear, at this time, click it.
  • Next, in the new interface, you should choose the option “Restarting immediately” or “Next restart” to detect your computer memory problems.

7 Heat Problems

If your computer hard drives become overheating and then computer will be forced to stop itself randomly. Thus, if your computer is working in a high temperature environment and running many programs at the same time, then you should take computer overheating issues into account.

Author Introduction:

Allissa Shen is a data recovery expert in DataNumen, Inc., which is the world leader in data recovery technologies, including corrupt sql and word recovery software products. For more information visit


Be the first to comment

Having a check on database owners is very important. You might hit a service broker problem and then realize that the root cause was a windows login of an ex-employee and it was set as the database owner. If you proactively track database owners, you will never meet such issues in your work environment.


In this article, we are dealing with database owner and not do or db_owner. DBO is a user, it’s a database concept and db_owner is a fixed database role.

Log it

Monitor Database OwnersFrom your central server, create a new query window and run this script. It is a prerequisite that you have already created Linked Server for all SQL Servers from which we would be collecting database owner info. Through this script, we are creating a single column table to save all SQL Server names. We will create another table which would act as our log table. This table would have 3 columns. The first is the server name, second is the database name and the last column is the owner name. Using a cursor, we will be creating dynamic TSQL statements and triggering it against the linked server. The collected info is then saved into the Log table. The script mentioned in this article uses the table sys.databases to retrieve database owner information.

     cserver VARCHAR(200) 

VALUES      ('Server1') 

     cserver VARCHAR(200), 
     cdb     VARCHAR(200), 
     cowner  VARCHAR(2000) 

  FROM   @Tserver 

OPEN c1 

FETCH next FROM c1 INTO @cmd 

      DECLARE @server NVARCHAR(2000) 

      SET @server = 'insert into Tlog select ''' + @cmd 
                    + ''', name, suser_sname(owner_sid) from [' 
                    + @cmd + '].master.sys.databases' 

      PRINT @server 

      EXEC (@server) 

      FETCH next FROM c1 INTO @cmd 



FROM   tlog

Scan for non-compliance

You can now filter this table for non-compliance i.e., look for database owners who have already left the organization. Using ALTER AUTHORIZATION ON DATABASE you can update the owner information for a database. You can use SA or a domain account and set it as owner of the database. This will help us to monitor database owners.  If you have deleted the domain account that owns a database, then you are making the database as an orphaned database. Now you would not be able to view database properties using a SQL Server management Studio.

Rare requirement

Track And Monitor SQL DatabaseIt is very rare that an application would require all databases created should have a specific account as database owner. Other than such databases you are free to modify the database owner. It is not just the deleted database owner information or a null database owner property that would restrict you from viewing database properties. If you are having a corrupted MDF file on your SQL instance, it would also block you from listing database properties.

Author Introduction:

Neil Varley is a data recovery expert in DataNumen, Inc., which is the world leader in data recovery technologies, including repair Outlook and excel recovery software products. For more information visit

2 Comments so far. Join the Conversation