MANAGING RENAME OF TABLES AND TABLE FIELDS

• US 20180129676A1
• Filed: 11/08/2016
• Published: 05/10/2018
• Est. Priority Date: 11/08/2016
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP SE
• Inventors: Eberlein, Peter, Driesen, Volker
• Granted Patent: US 10,496,401 B2
• Time in Patent Office: Days
• CPC Class Codes: G06F 16/213 with details for schema evolution support
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management

Abstract

According to some embodiments, a system and method are provided to automatically rename database objects. The system receives a rename file comprising (i) a plurality of database object names representing a plurality of database objects associated with an application and (ii) an identity assignment associated with one or more of the plurality of database objects. One or more of the plurality of database objects are automatically renamed based on (i) a currently installed version of the application, (ii) a version of the application associated with the rename file and (iii) the identity assignment associated with the one or more of the plurality of database objects.

Claims

1. A method of automatically renaming database objects, the method comprising:

receiving a rename file comprising (i) a plurality of database object names representing a plurality of database objects associated with an application and (ii) an identity assignment associated with one or more of the plurality of database objects; and

automatically renaming, via a processor, one or more of the plurality of database objects based on (i) a currently installed version of the application, (ii) a version of the application associated with the rename file and (iii) the identity assignment associated with the one or more of the plurality of database objects.

2. The method of claim 1, wherein in case that the version of the application associated with the rename file is a first version and the currently installed version of the application is a first version, the plurality of database object names will be saved as the plurality of database objects in the database and the plurality of database object names will be saved in a database object dictionary.

3. The method of claim 1, wherein in case that the version of the application associated with the rename file is a second version and the currently installed version of the application is a first version, automatically determine actions to rename the one or more of the plurality of database objects.

4. The method of claim 1, wherein the identity assignment assigns a global unique identifier (GUID) to one or more of the plurality of database objects.

5. The method of claim 1, wherein each database object is a database table.

6. The method of claim 1, wherein each database object is a database column.

7. The method of claim 1, wherein automatically renaming comprises reading a rename statement from a work list and determining if a target object name is already used, wherein in a case that the target object name is already used, skipping the rename statement and wherein in a case that the target object name has not been used, executing the rename statement.

8. A non-transitory computer-readable medium comprising instructions that when executed by a processor perform a method of automatically renaming database tables, the method comprising:

receiving (i) a first file comprising a plurality of database table names representing a plurality of database tables associated with an application and (ii) a second file comprising an identity assignment associated with one or more of the plurality of database tables; and

automatically renaming, via a processor, one or more of the plurality of database tables based on (i) a currently installed version of the application, (ii) a version of the application associated with the first file and the second file and (iii) the identity assignment associated with the one or more of the plurality of database objects.

9. The medium of claim 8, wherein in case that the version of the application associated with the first file and the second is a first version and the currently installed version of the application is a first version, the plurality of database object names will be saved as the plurality of database objects in the database and the plurality of database object names will be saved in a database object dictionary.

10. The medium of claim 8, wherein in case that the version of the application associated with first file and the second is a second version and the currently installed version of the application is a first version, automatically determine actions to rename the one or more of the plurality of database objects.

11. The medium of claim 8, wherein the identity assignment assigns a global unique identifier (GUID) to one or more of the plurality of database objects.

12. The medium of claim 8, wherein the rename file comprises a first file comprising the plurality of database object names and a second file comprising the identity assignment associated with the one or more of the plurality of database objects.

13. The medium of claim 8, wherein automatically renaming comprises reading a rename statement from a work list and determining if a target object name is already used, wherein in a case that the target object name is already used, skipping the rename statement and wherein in a case that the target object name has not been used, executing the rename statement.

14. A system for renaming database objects, the system comprising:

a processor; and

a non-transitory computer-readable medium comprising instructions that when executed by a processor perform a method to automatically rename database objects, the method comprising;

receiving a rename file comprising (i) a plurality of database object names representing a plurality of database objects associated with an application and (ii) an identity assignment associated with one or more of the plurality of database objects; and

automatically renaming, via a processor, one or more of the plurality of database objects based on (i) a currently installed version of the application, (ii) a version of the application associated with the rename file and (iii) the identity assignment associated with the one or more of the plurality of database objects, wherein the identity assignment assigns a global unique identifier (GUID) to one or more of the plurality of database objects.

15. The system of claim 14, wherein in case that the version of the application associated with the rename file is a first version and the currently installed version of the application is a first version, the plurality of database object names will be saved as the plurality of database objects in the database and the plurality of database object names will be saved in a database object dictionary.

16. The system of claim 14, wherein the identity assignment assigns a global unique identifier (GUID) to one or more of the plurality of database objects.

17. The system of claim 14, wherein each database object is a database table.

18. The system of claim 14, wherein each database object is a database view.

19. The system of claim 14, wherein automatically renaming comprises reading a rename statement from a work list and determining if a target object name is already used, wherein in a case that the target object name is already used, skipping the rename statement and wherein in a case that the target object name has not been used, executing the rename statement.

20. The system of claim 14, wherein in case that the version of the application associated with the rename file is a second version and the currently installed version of the application is a first version, automatically determine actions to rename the one or more of the plurality of database objects.