MACRO uses two types of SQL Server database:
This contains user names, passwords, roles, permissions and a list of 'Data' databases. A Security database can also be used to store study definitions and subject data, although we recommend creating a separate Data database for this. Each MACRO installation can have only one Security database.
A Data database contains all the rest of the data used by MACRO, such as study definitions, site details, study-site associations and all collected subject data.
When you first log in to MACRO after it has been installed on a machine, a new Security database is automatically created for you.
You can store several studies and their associated subject data in a single Data database, although for large studies it may be better to create a separate Data database for each study that you create. Note that you will use a single Security database, in which you register one or more Data databases. All the user details stored in the Security database apply to all the registered Data databases.
Follow the steps below. The first two must be carried out, in order, before you can do any of the other actions. Click the links below for further information.
Warning: Databases cannot be copied. Do not attempt to copy a database from within SQL Server as invalid references are likely to be created, leading to data corruption. All new databases must be created and registered in the usual way via the System Management module.
If you need to enter data at a site that does not have a permanent internet connection, you must create a local database at the site, known as a site database. Subject data collected at this remote site will need to be transferred to the central server using the Data transfer module.
MACRO product version numbers contain four parts; Major.Minor.Build.SVN. For example, 4.3.0.2352.
MACRO databases use a similar versioning system with the SVN (Software Versioning number) replaced by a DBV (Database Version number).
When logging into a data or security database, the database version (DBV) is checked against the MACRO product version (SVN). If the two do not match, a warning will be displayed and the user may be prompted to upgrade the database.