It may be necessary to move an entire NoiseTools database to a new location. For example, if NoiseTools has been running on a local PC and there is a need to move the data to a server or if NoiseTools will be transferred to a new PC or computer.
Backup the data before moving the files
It is recommended that all files are backed up before attempting to move them to a new location.
Close NoiseTools
Before moving the data, please ensure that NoiseTools is not running on any PC that has access to the data.
If you have more than one user who can access the data, please ensure that no of them are running NoiseTools.
To move the data, follow the steps below:
1. Move the measurement data
To move the measurement data to a new location, create a new folder in the new location called NoiseTools.
It is essential that full read and write access is available to this folder for any user that wishes to access the data.
A) Locate the current database.
The NoiseTools databases use a .crtnd file extension. This is the database file that contains all of the acoustic measurement data.
By default, NoiseTools will store measurements and audio recordings in the local user’s roaming data folder which may be similar to:
C:\Users\username\AppData\Roaming\Cirrus Research\NoiseTools
where username is the name of the current user. If the database is stored in a different location, locate the folder using Windows Explorer.
B) Find the file with the extension .crntd and move this to the new location.
C) Open NoiseTools. NoiseTools will still be looking for the database in the old location and when it cannot find the file, it will create a new, empty database.
D) Click Tools, Databases and click Add Existing.
Locate the .crtnd file that was moved to the new location and click OK.
In the database list, move the database in the new location to the top of the list using the up arrow button. The empty database that was created in step C above can be removed by highlighting it and clicking the X button.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article