System, method and computer program product for migrating data from one database to another database
View Patent ↗A software tool that is useful when one is attempting to migrate data from one database to another database. In one aspect of the invention, the software tool reduces the complications that may arise when one attempts to migrate data from one Lightweight Directory Access Protocol (LDAP) directory to another LDAP directory, where the schemas for the two directories are not the same.
1. A method to be implemented on a general purpose computer for migrating records from a source directory having a source schema to a destination directory having a destination schema, comprising:
determining whether an object class defined in the source schema matches an object class defined in the destination schema; and
determining whether the destination schema needs to be modified in order to be compatible with the source schema if it is determined that the object class defined in the source schema matches the object class defined in the destination schema, wherein the determination is based at least in part on information concerning the object class defined in the source schema and information concerning the object class defined in the destination schema.
2. The method of claim 1 , wherein the step of determining whether the object class defined in the source schema matches the object class defined in the destination schema comprises:
creating a first list of object class records, wherein each object class record in the first list is associated with the object class defined in the source schema and includes information about the associated object class;
creating a second list of object class records, wherein each object class record in the second list is associated with the object class defined in the destination schema and includes information about the associated object class;
selecting an object class record from the first list; and
comparing the selected object class record to the object class records in the second list to find a matching or partially matching record.
3. The method of claim 2 , further comprising:
adding an object class directly or indirectly to the destination schema if the second list does not include a matching or partially matching object class record, wherein the added object class is identical to the object class associated with the object class record selected from the first list.
4. The method of claim 2 , further comprising:
adding an object class directly or indirectly to the destination schema if the second list includes a partially matching object class record, wherein the added object class is nearly identical to the object class associated with the object class record selected from the first list.
5. The method of claim 2 , wherein the determination of whether the destination schema needs to be modified in order to be compatible with the source schema is based at least in part on information included in the selected object class record and information included in the matching object class record.
6. The method of claim 3 , wherein the source directory and the destination directory are lightweight directory access protocol (LDAP) directories.
7. The method of claim 6 , wherein the step of adding the object class to the destination schema comprises adding an entry to a lightweight directory interchange format (LDIF) file.
8. The method of claim 6 , wherein the step of adding the object class to the destination schema comprises transmitting a request to an LDAP server associated with the destination directory.
9. The method of claim 1 , further comprising:
creating a first list of attribute records, wherein each attribute record in the first list is associated with an attribute defined in the source schema and includes information about the associated attribute;
creating a second list of attribute records, wherein each attribute record in the second list is associated with an attribute defined in the destination schema and includes information about the associated attribute;
selecting an attribute record from the first list;
comparing the selected attribute record to the attribute records in the second list to find a matching or partially matching attribute record;
adding an attribute to the destination schema if the second list does not include a matching or partially matching record, wherein the added attribute is identical to the attribute associated with the attribute record selected from the first list; and
comparing content from the attribute record selected from the first list to content from the matching attribute record to determine whether the destination schema needs to be modified in order to be compatible with the source schema if the second list does include a matching record.
10. The method of claim 9 , wherein the content from the selected attribute record comprises information about syntax that is associated with the attribute associated with the selected attribute record and the content from the matching attribute record comprises information about the syntax that is associated with the attribute associated with the matching attribute record.
11. The method of claim 10 , further comprising creating or selecting a filter if the syntax associated with the attribute associated with the selected attribute record is not equivalent to the syntax associated with the attribute associated with the matching attribute record.
12. The method of claim 1 , wherein the step of determining whether the destination schema needs to be modified comprises determining the object class type of the object class defined in the source schema.
13. The method of claim 12 , further comprising determining the object class type of the matching object class defined in the destination schema if the determined object class type of the object class defined in the source schema is Undefined.
14. A method to be implemented on a general purpose computer for migrating records from a source directory to a destination directory having a destination schema, comprising:
retrieving an entry from the source directory that is to be added to the destination directory;
determining whether the destination schema allows the entry to be added to the destination directory;
updating the destination schema if the schema does not allow the entry to be added to the destination directory;
adding the entry to the destination directory; and
repeating the above steps for each entry from the source directory that is to be added to the destination directory.
15. The method of claim 14 , wherein the step of determining whether the destination schema will allow the entry to the added to the destination directory comprises:
determining an object class that is associated with the entry; and
determining whether the destination schema defines an object class that matches the object class that is associated with the entry.
16. The method of claim 15 , further comprising adding an object class to the destination schema if the destination schema does not define an object class that matches the object class that is associated with the entry.
17. The method of claim 14 , wherein the step of determining whether the destination schema will allow the entry to the added to the destination directory comprises:
determining an attribute that is associated with the entry; and
determining whether the destination schema defines an attribute that matches the attribute that is associated with the entry.
18. The method of claim 17 , further comprising adding an attribute to the destination schema if the destination schema does not define an attribute that matches the attribute that is associated with the entry.
19. A computer system for migrating records from a source directory having a source schema to a destination directory having a destination schema, comprising:
first determining means for determining whether an object class defined in the source schema matches an object class defined in the destination schema; and
second determining means for determining whether the destination schema needs to be modified in order to be compatible with the source schema, wherein the determination is based at least in part on information concerning the object class defined in the source schema and information concerning the object class defined in the destination schema.
20. The system of claim 19 , wherein the first determining means comprises:
a first list of object class records, wherein each object class record in the first list is associated with an object class defined in the source schema and includes information about the associated object class;
a second list of object class records, wherein each object class record in the second list is associated with an object class defined in the destination schema and includes information about the associated object class;
object class selector means for selecting an object class record from the first list; and
object class comparator means for comparing the selected object class record to the object class records in the second list to find a matching or partially matching record.
21. The system of claim 20 , further comprising:
first schema updater means for adding an object class directly or indirectly to the destination schema if the second list does not include a matching or partially matching object class record, wherein the added object class is identical to the object class associated with the object class record selected from the first list.
22. The system of claim 21 , wherein the source directory and the destination directory are lightweight directory access protocol (LDAP) directories.
23. The system of claim 22 , wherein the first schema updater means adds the object class to the destination schema by adding an entry to a lightweight directory interchange format (LDIF) file.
24. The system of claim 22 , wherein the first schema updater means adds the object class to the destination schema by transmitting a request to an LDAP server associated with the destination directory.
25. The system of claim 20 , further comprising first schema updater means for adding an object class directly or indirectly to the destination schema if the second list includes a partially matching object class record, wherein the added object class is nearly identical to the object class associated with the object class record selected from the first list.
26. The system of claim 20 , wherein the second determining means further determines whether the destination schema needs to be modified in order to be compatible with the source schema by comparing information included in the selected object class record with information included in the matched object class record.
27. The system of claim 19 , further comprising:
a first list of attribute records, wherein each attribute record in the first list is associated with an attribute defined in the source schema and includes information about the associated attribute; and
a second list of attribute records, wherein each attribute record in the second list is associated with an attribute defined in the destination schema and includes information about the associated attribute, wherein
attribute selector means for selecting an attribute record from the first list;
attribute comparator means for comparing the selected attribute record to the attribute records in the second list to find a matching or partially matching attribute record; and
second schema updater means for adding an attribute to the destination schema if the second list does not include a matching or partially matching record, wherein the added attribute is identical to the attribute associated with the attribute record selected from the first list, wherein the attribute comparator means compares content from the attribute record selected from the first list to content from the matching attribute record to determine whether the destination schema needs to be modified in order to be compatible with the source schema if the second list includes a matching record.
28. The system of claim 27 , wherein the content from the selected attribute record comprises information about syntax that is associated with the attribute associated with the selected attribute record and the content from the matching attribute record comprises information about the syntax that is associated with the attribute associated with the matching attribute record.
29. The system of claim 28 , further comprising a filter that transforms data from the syntax associated with the attribute associated with the selected attribute record to the syntax that is associated with the attribute associated with the matching attribute record.
30. A computer program product for migrating records from a source directory having a source schema to a destination directory having a destination schema, the computer program product being embodied in a computer readable medium and comprising computer instructions for:
determining whether an object class defined in the source schema matches an object class defined in the destination schema; and
determining whether the destination schema needs to be modified in order to be compatible with the source schema if it is determined that the object class defined in the source schema matches an object class defined in the destination schema, wherein the determination is based at least in part on information concerning the object class defined in the source schema and information concerning the object class defined in the destination schema.