Sometime IT specialist may encounter situation, when merging data from one installation of Medikro Spirometry Software (MSS) to another one is needed. For example: there was one workstation (MSS 4.x) used with local databases and now the user wants to merge local information to existing MSS 4.x network database (SQL Server). In this article we provide step by step find instructions for different combinations of source and target environments. Make sure to choose the right instruction, depending on the version of MSS at source and at the target location as well as format of the source and target databases. Check the table below.
Table of content
| Source MSS Version | Source database | Target MSS Version | Target database | Link to instructions |
| 3.x | local database (MS Access) | 4.x | network database (SQL Server) | Go to section 1 |
| 3.x | network databases (SQL Server) | 3.x | network database (SQL Server) | Go to section 2 |
| 3.x | local databases (MS Access) | 3.x | network database (SQL Server) | Go to section 3 |
| 4.x | local databases (Sqlite) | 4.x | network databases (SQL server) | Go to section 4 |
1. How to merge MSS 3.x local databases (MS Access) to a MSS 4.x network database (SQL Server)?
These instructions assume that there is a 3.x workstation that is using a local database (MS Access) and a 4.x workstation that is using a network database (SQL Server). MSS 3.x workstation will be updated to MSS 4.x and local databases content will be merged into the network database
1. Make backups of the local databases at C:\Medikro\Database\
2. Install the Medikro Spirometry Software 4.x by selecting the "Network Database" type. Follow the Medikro Spirometry Software Installation Guide chapter "Install Workstation with Network Database". You need to use the DBConnection.ini file during installation (which was got when creating the SQL Server databases).
3. During the installation it will ask: "This tool can transfer spirometry data from your old spirometry database to new local databases. Do you want to transfer spirometry data?" Select Yes to transfer. Depending on the amount of data, transferring can take a long time (even hours). This step converts the local MS Access database to the local SQLite database.
4. After successful installation, start the spirometry software. When started, Persons and Studies starts to synchronize data from the local databases (SQLite) to network databases (SQL Server). Depending on the amount of data, synchronizing can take a long time (even hours). Please be patient and wait until sync is finished.
5. After the successful syncing, Persons and Studies will start to use network databases.
6. Please check that your network database now contains data from the local database.
2. How to merge MSS 3.x network databases (SQL Server) to a MSS 3.x network database (SQL Server)?
Merging the MSS 3.x databases require using "MSS DB Transfer Utility" software, which can be purchased from Medikro. These instructions summarise the main steps of the process but you need to read the User's Manual first, which comes with the tool.
NOTE!
-Please make a backup of your original databases before doing any other tasks.
-You must have administration rights and general knowledge about SQL Server to create a database and to give database access rights to users.
-You must have a general understanding of how to create Windows ODBC DSNs.
-You need to install "LabVIEW Runtime Engine 2009" in order to run the database transfer tool. You can install it by running: \Runtime Engine\LV900runtime.msi.
1) Creating new SQL Server databases (if not existing)
1. Check that the database server uses "Windows authentication mode".
2. Use the SQL Server scripts to create a new database in SQL Server. Scripts are located "\MSS DB Transfer Utility Software\MS SQL Server\Create Tables Script.txt"
3. Assign Windows users or groups permissions to use the database (read, write, create tables, create columns).
2) Transferring data from MS Access databases
1. Create a 32-bit ODBC DSN with the name "MEDIKRO_SPIROMETRY_OUT" and connect it to the (existing/just created) SQL Server database. It will act as a destination for data transfer.
2. Create a 32-bit ODBC DSN with the name "MEDIKRO_SPIROMETRY_IN" and connect it to the existing SQL Server database. It will act as a source for data transfer.
3. If needed, check the transfer settings according to the tool's User Manual.
4. Start the data transfer (=database merging) by running "DB Transfer.exe"
5. If you have multiple source databases to transfer, change the MEDIKRO_SPIROMETRY_IN pointing to another source database and run the transfer again until you have merged all your databases.
3) Testing the new SQL Server database with Medikro Spirometry Software
1. In the workstation you want to test the SQL database, create a 32-bit SQL Server ODBC DSN that points to your SQL Server database. Give a name for the DSN that starts with "MEDIKRO_" (for example "MEDIKRO_SQL_DATABASE"). Use the Windows authentication method.
2. Start the Medikro Spirometry Software. Go to Device->Settings->Database. In the "Result DB (DSN)" dropdown, select the DSN that points to the SQL Server database. Click ok to close the settings. Now the spirometry software should be using the SQL Server database.
3. How to merge MSS 3.x local databases (MS Access) to a MSS 3.x network database (SQL Server)?
Merging the MSS 3.x databases require using "MSS DB Transfer Utility" software, which can be purchased from Medikro. These instructions summarise the main steps of the process but you need to read the User's Manual first, which comes with the tool.
NOTE!
-Please make a backup of your original databases before doing any other tasks.
-You must have administration rights and general knowledge about SQL Server to create a database and to give database access rights to users.
-You must have a general understanding of how to create Windows ODBC DSNs.
-You need to install "LabVIEW Runtime Engine 2009" in order to run the database transfer tool. You can install it by running: \Runtime Engine\LV900runtime.msi.
1) Creating new SQL Server databases (if not existing)
1. Check that the database server uses "Windows authentication mode".
2. Use the SQL Server scripts to create a new database in SQL Server. Scripts are located "\MSS DB Transfer Utility Software\MS SQL Server\Create Tables Script.txt"
3. Assign Windows users or groups permissions to use the database (read, write, create tables, create columns).
2) Transferring data from MS Access databases
1. Create a 32-bit ODBC DSN with the name "MEDIKRO_SPIROMETRY_OUT" and connect it to the (existing/just created) SQL Server database. It will act as a destination for data transfer.
2. Create a 32-bit ODBC DSN with the name "MEDIKRO_SPIROMETRY_IN" and connect it to the existing MS Access database. It will act as a source for data transfer.
3. If needed, check the transfer settings according to the tool's User Manual.
4. Start the data transfer (=database merging) by running "DB Transfer.exe"
5. If you have multiple source databases to transfer, change the MEDIKRO_SPIROMETRY_IN pointing to another source database and run the transfer again until you have merged all your databases.
3) Testing the new SQL Server database with Medikro Spirometry Software
1. In the workstation you want to test the SQL database, create a 32-bit SQL Server ODBC DSN that points to your SQL Server database. Give a name for the DSN that starts with "MEDIKRO_" (for example "MEDIKRO_SQL_DATABASE"). Use the Windows authentication method.
2. Start the Medikro Spirometry Software. Go to Device->Settings->Database. In the ""Result DB (DSN)"" dropdown, select the DSN that points to the SQL Server database. Click ok to close the settings. Now the spirometry software should be using the SQL Server database.
4. How to merge MSS 4.x local databases (Sqlite) to MSS 4.x network databases (SQL server)?
These instructions assume that there is a 4.x workstation that is using a local database (SQLite) and a 4.x workstation that is using a network database (SQL Server). Instructions show how to merge the content of local databases to network databases.
Merging must be performed using the syncing feature of the Medikro Persons and Studies. This can be done in a local database workstation (A) or in one of the network database workstations (B). Please select the way that suits your needs:
A) Local databases content will be merged to network database and workstation will be configured to use network databases
1. Make backups of the local databases c:\ProgramData\Medikro\Databases.
2. Uninstall Medikro Spirometry Software
3. Install the Medikro Spirometry Software by selecting "Network Database" type. Follow the Medikro Spirometry Software Installation Guide chapter "Install Workstation with Network Database". You need to use the DBConnection.ini file during installation (which was got when creating the SQL Server databases).
4. After the installation copy your back upped database files to c:\ProgramData\Medikro\Databases.
5. Start the spirometry software. When started, Persons and Studies starts to synchronize data from the local databases (SQLite) to network databases (SQL Server). Depending on amount of data, synchronizing can take a long time (even hours). Please be patient and wait until sync is finished.
6. After the successful syncing, Persons and Studies will start to use network databases.
7. Please check that you network database now contains data from the local database.
B) Local databases content will be merged to network database using workstation that is already connected to network databases
1. Select one of the workstations that is already connected to network databases. Make backups of its offline databases c:\ProgramData\Medikro\Databases.
2. Copy the local databases from another computer to c:\ProgramData\Medikro\Databases.
3. Start the spirometry software. When started, Persons and Studies starts to synchronize data from the local databases (SQLite) to network databases (SQL Server). Depending on amount of data, synchronizing can take a long time (even hours). Please be patient and wait until sync is finished.
4. After the successful syncing, you can return the original offline databases that were back upped in step 1.
5. Please check that you network database now contains data from the local database.
Comments
0 comments
Please sign in to leave a comment.