Difference between revisions of "Template:BIBID Import"
(Created page with "'''Pre-requisites''' In order to run the BIBID Import you need: *The Firebird Client Library installing on the same PC as the import will run *The server name and path of th...") |
m |
||
| Line 7: | Line 7: | ||
If you install the iBID client application on a PC that already has BIBID installed on it, then the above pre-requisites are taken care of automatically. | If you install the iBID client application on a PC that already has BIBID installed on it, then the above pre-requisites are taken care of automatically. | ||
| + | |||
| + | '''Performance Note:''' | ||
| + | |||
| + | The table holding the audit trail information has an additional index that is required for the end-user application, but that will have a slight negative effect on performance during the '''BIBID Data Transfer'''. You may drop the index before the BIBID Data Transfer and Import, and then create the index again afterwards. | ||
| + | |||
| + | The SQL command to drop the index is: | ||
| + | |||
| + | DROP INDEX ilog.idx_ilog_change_status | ||
| + | |||
| + | and the command to recreate it afterwards is: | ||
| + | |||
| + | CREATE INDEX idx_ilog_change_status ON ilog (change_status); | ||
'''Running the import''' | '''Running the import''' | ||
| − | + | To perform the BIBID Import and transfer it to the National Database: | |
##Run the Step 1 of the '''BIBID Data Transfer''' which will [[Import from BIBID v1]] (this may take several hours) | ##Run the Step 1 of the '''BIBID Data Transfer''' which will [[Import from BIBID v1]] (this may take several hours) | ||
##When the BIBID Data Transfer is fully completed, run Step 2, '''Export database...''' (this should only take a few minutes) | ##When the BIBID Data Transfer is fully completed, run Step 2, '''Export database...''' (this should only take a few minutes) | ||
Latest revision as of 14:31, 1 August 2013
Pre-requisites
In order to run the BIBID Import you need:
- The Firebird Client Library installing on the same PC as the import will run
- The server name and path of the BIBID database.
If you install the iBID client application on a PC that already has BIBID installed on it, then the above pre-requisites are taken care of automatically.
Performance Note:
The table holding the audit trail information has an additional index that is required for the end-user application, but that will have a slight negative effect on performance during the BIBID Data Transfer. You may drop the index before the BIBID Data Transfer and Import, and then create the index again afterwards.
The SQL command to drop the index is:
DROP INDEX ilog.idx_ilog_change_status
and the command to recreate it afterwards is:
CREATE INDEX idx_ilog_change_status ON ilog (change_status);
Running the import
To perform the BIBID Import and transfer it to the National Database:
- Run the Step 1 of the BIBID Data Transfer which will Import from BIBID v1 (this may take several hours)
- When the BIBID Data Transfer is fully completed, run Step 2, Export database... (this should only take a few minutes)
- Zip the exported file and upload to the National Database via the upload facility at nww.mdsas.nhs.uk/ibidupload (Maximum upload size 23Mb)
Note: the export and data transfer is a one-time requirement. All future updates will be transmitted in real-time from within the IBID client app
The BIBID Data Transfer functions on the IBID Installation and set up tab
