Managing rename of tables and table fields

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) a respective first identity assignment associated with each respective one of the plurality of database objects, each respective first identity assignment present in a currently installed version of the application;

the rename file including a respective second identity assignment associated with each respective one of the plurality of database objects, each respective second identity assignment present in a subsequent version of the application associated with the rename file;

assigning each respective first identity assignment and each respective second identity assignment to a respective same globally unique identifier for each respective one of the plurality of database objects;

automatically renaming, via a processor, one or more of the plurality of database objects based on (i) the currently installed version of the application, and (ii) the subsequent version of the application, there being one or more interim versions between the currently installed version and the subsequent version, the one or more interim versions each including respective identity assignments for each respective one of the plurality of database objects, the interim version respective identity assignments being different than the respective first identity assignment and the second identity assignment;

the automatic renaming occurring with the one or more interim versions not being installed; and

for each of the plurality of database objects being renamed, changing within the subsequent version of the application each respective second identity assignment to the respective first identity assignment assigned to the same globally unique identifier.

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 a 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 cause the processor to 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 a respective first identity assignment associated with each respective one of the plurality of database tables, each respective first identity assignment present in a currently installed version of the application;

the second file including a respective second identity assignment associated with each respective one of the plurality of database tables, each respective second identity assignment present in a subsequent version of the application associated with the second file;

assigning each respective first identity assignment and each respective second identity assignment to a respective same globally unique identifier for each respective one of the plurality of database tables;

automatically renaming, via a processor, one or more of the plurality of database tables based on (i) the currently installed version of the application, and (ii) the subsequent version of the application, there being one or more interim versions between the currently installed version and the subsequent version, the one or more interim versions each including respective identity assignments for each respective one of the plurality of database tables, the interim version respective identity assignments being different than the respective first identity assignment and the second identity assignment;

the automatic renaming occurring with the one or more interim versions not being installed; and

for each of the plurality of database tables being renamed, changing within the subsequent version of the application each respective second identity assignment to the respective first identity assignment assigned to the same globally unique identifier.

9. The medium of claim 8 , wherein in case that the version of the application associated with the first file and the second file is a first version and the currently installed version of the application is a first version, the plurality of database tables names will be saved as the plurality of database tables in a database and the plurality of database table names will be saved in a database data 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 tables.

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 tables.

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

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) a respective first identity assignment associated with each respective one of the plurality of database objects, each respective first identity assignment present in a currently installed version of the application;

the rename file including a respective second identity assignment associated with each respective one of the plurality of database objects, each respective second identity assignment present in a subsequent version of the application associated with the rename file;

assigning each respective first identity assignment and each respective second identity assignment to a respective same globally unique identifier for each respective one of the plurality of database objects;

automatically renaming, via a processor, one or more of the plurality of database objects based on (i) the currently installed version of the application, and (ii) the subsequent version of the application, there being one or more interim versions between the currently installed version and the subsequent version, the one or more interim versions each including respective identity assignments for each respective one of the plurality of database objects, the interim version respective identity assignments being different than the respective first identity assignment and the second identity assignment;

the automatic renaming occurring with the one or more interim versions not being installed; and

for each of the plurality of database objects being renamed, changing within the subsequent version of the application each respective second identity assignment to the respective first identity assignment assigned to the same globally unique identifier.

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-a 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.