Database authorization management method and device, medium and product
By configuring activation files of multiple authorization types on the licensed software server, the flexibility and simplification of database authorization are achieved, the complex authorization problems in the existing technology are solved, and the user experience and system scalability are improved.
Patent Information
- Application Number
- CN202510533949.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-04-25
- Publication Date
- 2025-08-15
AI Technical Summary
The existing database authorization process is complex, has low flexibility, and has poor user experience, making it difficult to meet the diverse needs of different application scenarios.
Configure activation files of multiple authorization types on the licensed software server, receive authorization applications from the client, read application types, obtain corresponding activation files, create and send authorization files, and support multiple types of database service authorization.
It improves the flexibility of database service authorization, simplifies operational processes, meets the needs of different application scenarios, improves user experience, and saves system resources.
Smart Images

Figure CN120493274A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of database technology, and in particular to a database authorization management method, device, medium and product. Background Art
[0002] The LAC (License Access Control, LAC for short) mechanism is a database software licensing management mechanism used to ensure that only users with appropriate licenses can access and use specific database services. It is an important mechanism to protect the rights and interests of database software developers. With the continuous development of database technology, the application scenarios of databases are becoming more and more complex. The database resource requirements in different application scenarios vary greatly. Database users often need to adjust the required database authorization services based on their own costs and resource requirements. However, the current authorization process for database services is relatively complicated. Each authorization application from a database user needs to be submitted on the office platform of a specific database developer. The database developer then configures activation files for the user based on the needs of the database user. This results in low flexibility and a poor user experience. Summary of the Invention
[0003] An object of the present invention is to provide a database authorization management method, device, medium and product that can improve the flexibility of database authorization.
[0004] In particular, the present invention provides a database authorization management method, comprising:
[0005] The license software server receives an authorization application from a license software client, wherein the license software client is installed on a client device where a database is located, and the license software server is installed on a server device, and the license software server is configured with activation files of multiple authorization types;
[0006] Read the authorization type of the authorization application request;
[0007] Obtain an activation file of the authorization type that meets the authorization application request, and record it as a pending activation file;
[0008] Create an authorization file based on the pending activation file;
[0009] The authorization file is sent to the licensed software client.
[0010] Optionally, the step of obtaining an activation file of an authorization type that meets the authorization application request includes:
[0011] Check whether there is an available activation file that meets the authorization type requested by the authorization application; if so, execute the step of obtaining the activation file that meets the authorization type requested by the authorization application; if not, return a preset authorization failure message to the licensed software client.
[0012] Optionally, the activation file includes a virtual processor activation file;
[0013] If it is read that the authorization type of the authorization application request is a virtual processor authorization type, the step of checking whether there is an available activation file that meets the authorization type of the authorization application request includes:
[0014] Check whether the number of virtual processors that can be authorized by the virtual processor activation file is greater than or equal to the number of virtual processors requested by the authorization application. If so, determine that there is an available activation file that meets the authorization type requested by the authorization application.
[0015] Optionally, the activation file includes an instance activation file;
[0016] If the authorization type of the authorization application request is read as an instance authorization type, the step of checking whether there is an available activation file that meets the authorization type of the authorization application request includes:
[0017] Check whether there is an available instance activation file, and if so, determine whether there is an available activation file that meets the authorization type requested by the authorization application.
[0018] Optionally, the activation file of each authorization type configured on the licensed software server is provided with a preset unique identifier, and the step of obtaining the activation file of the authorization type that meets the authorization application request includes:
[0019] Determine the corresponding preset unique identifier according to the authorization type of the authorization application request;
[0020] The activation file is searched according to the corresponding preset unique identifier.
[0021] Optionally, the licensed software server pre-builds an activation file information table, which records a preset unique identifier of the activation file of each authorization type configured by the licensed software server and usage of the activation file of each authorization type.
[0022] Optionally, the step of creating an authorization file based on the activation file to be processed includes:
[0023] Obtaining authorization configuration from the pending activation file;
[0024] Obtaining identification information of the client device in the authorization application;
[0025] Generate the authorization file containing the authorization configuration and the identification information.
[0026] According to another aspect of the present invention, a computer device is also provided, comprising a memory, a processor, and a computer executable program stored in the memory and running on the processor, and the processor implements the database authorization management method according to any one of the above items when executing the computer executable program.
[0027] According to another aspect of the present invention, a computer-readable storage medium is provided, on which a computer-executable program is stored. When the computer-executable program is executed by a processor, the database authorization management method according to any one of the above items is implemented.
[0028] According to another aspect of the present invention, a computer program product is provided, comprising a computer executable program, wherein when the computer executable program is executed by a processor, the database authorization management method of the database system according to any one of the above items is implemented.
[0029] The database authorization management method of the present invention configures a database and a licensed software client on a client device, configures a licensed software server on a server device, and configures activation files of multiple authorization types on the licensed software server. After receiving an authorization request from the licensed software client, the licensed software server reads the authorization type requested in the authorization request, obtains an activation file that meets the authorization type requested in the authorization request, records it as a pending activation file, creates an authorization file based on the pending activation file, and sends the authorization file to the licensed software client. In other words, the licensed software server can receive different types of authorization requests, then creates corresponding authorization files based on the configured activation files of the corresponding types, and then sends the authorization files to the licensed software client, thereby enabling the database to use the corresponding database services. Therefore, the licensed software server and the licensed software client cooperate to implement multiple types of database service authorization, improve the flexibility of database service authorization, simplify the authorization operation process, facilitate database users to flexibly adjust or select appropriate database services according to actual conditions, meet the diverse needs of different application scenarios, and help improve user experience. At the same time, the management process is simplified, system resources are saved, and the scalability of the system is improved.
[0030] Based on the following detailed description of specific embodiments of the present invention in conjunction with the accompanying drawings, those skilled in the art will become more aware of the above and other objects, advantages and features of the present invention. BRIEF DESCRIPTION OF THE DRAWINGS
[0031] Hereinafter, some specific embodiments of the present invention will be described in detail in an exemplary and non-limiting manner with reference to the accompanying drawings. The same reference numerals in the accompanying drawings indicate the same or similar components or parts. It should be understood by those skilled in the art that these drawings are not necessarily drawn to scale. In the accompanying drawings:
[0032] Figure 1 is a schematic flow chart of a database authorization management method according to an embodiment of the present invention;
[0033] Figure 2 is a schematic flow chart of obtaining an activation file in a database authorization management method according to an embodiment of the present invention;
[0034] Figure 3 is a schematic flow chart of creating an authorization file in a database authorization management method according to an embodiment of the present invention;
[0035] Figure 4 is a schematic flow chart of a database authorization management method according to another embodiment of the present invention;
[0036] Figure 5 is a simplified schematic diagram of a database authorization system architecture according to one embodiment of the present invention;
[0037] Figure 6 is a schematic diagram of a computer device according to one embodiment of the present invention;
[0038] Figure 7 is a schematic diagram of a computer-readable storage medium according to one embodiment of the present invention;
[0039] Figure 8 is a schematic diagram of a computer program product according to one embodiment of the present invention. DETAILED DESCRIPTION
[0040] It should be understood by those skilled in the art that the embodiments described below are only some embodiments of the present invention, rather than all embodiments of the present invention, and that these embodiments are intended to explain the technical principles of the present invention and are not intended to limit the scope of protection of the present invention. Based on the embodiments provided by the present invention, all other embodiments obtained by those skilled in the art without creative effort should still fall within the scope of protection of the present invention.
[0041] It should be noted that the logic and / or steps represented in the flowchart or described in other ways herein, for example, can be considered as a sequenced list of executable instructions for implementing logical functions, and can be specifically implemented in any computer-readable medium for use by an instruction execution system, device or equipment (such as a computer-based system, a system including a processor or other system that can fetch instructions from an instruction execution system, device or equipment and execute instructions), or used in combination with these instruction execution systems, devices or equipment.
[0042] The flowchart provided by the present invention is not intended to indicate that the operations of the method will be performed in any particular order, or that all operations of the method are included in all every case. In addition, the method may include additional operations. Within the scope of the technical ideas provided by the present embodiment method, additional changes can be made to the above method.
[0043] Reference Figure 1 As shown, in one embodiment, the database authorization management method generally includes:
[0044] In step S101, the license software server receives an authorization application from the license software client. The license software client is installed on the client device where the database is located, and the license software server is installed on the server device. Specifically, the license software client and the database are installed on the same client device. The database may have its own license software client, that is, the database supports the license software client function, or the license software client may be installed separately on the client device where the database is located. The license software server is installed on a server device that is independent of the client device where the license software client is located. The license software client communicates with the license software server, so the license software server can receive the authorization application from the license software client, and the license software server can issue an authorization file to the license software client, so that the database can run the authorized functional service according to the authorization file.
[0045] In addition, the license software server is configured with activation files of multiple authorization types. Specifically, the activation files configured by the license software server may include virtual processor activation files and instance activation files. The virtual processor activation file is used to authorize according to the number of virtual processors (Virtual Central Processing Unit, abbreviated as VCPU), and the instance activation file is used for instance authorization.
[0046] Step S102: Read the authorization type of the authorization request. Specifically, because the license software server is configured with multiple types of activation files, the license software server can receive different types of authorization requests from the license software client. Therefore, after receiving the authorization request from the license software client, the license software server must confirm the authorization type of the authorization request.
[0047] Step S103: Obtain an activation file that matches the authorization type requested by the authorization application and record it as the pending activation file. Specifically, the corresponding activation file is searched based on the authorization type requested by the authorization application. For example, if the authorization application requests virtual processor authorization, the virtual processor activation file is searched; if the authorization application requests instance authorization, the instance activation file is searched.
[0048] Reference Figure 2 As shown, specifically, each activation file of the authorization type configured on the license software server is provided with a preset unique identifier. Specifically, each activation file of the authorization type has its own unique key value. The steps of obtaining the activation file of the authorization type that meets the authorization application request include:
[0049] Step S201: Determine the corresponding preset unique identifier based on the authorization type requested by the authorization application. Specifically, the authorization application may carry the preset unique identifier corresponding to the requested authorization type, and the licensed software server may obtain the preset unique identifier corresponding to the authorization type requested by the authorization application upon receiving the authorization application.
[0050] Step S202: Search for an activation file according to the corresponding preset unique identifier. Specifically, the activation file is searched according to the preset unique identifier, and the activation file with the preset unique identifier corresponding to the authorization type requested by the authorization application is found, that is, the required activation file.
[0051] By setting a preset unique identifier in the activation file of each authorization type, when obtaining the activation file, the corresponding preset unique identifier is determined according to the authorization type requested by the authorization application, and the activation file is searched according to the corresponding preset unique identifier, which can speed up the activation file search time.
[0052] Step S104: Create an authorization file based on the activation file to be processed.
[0053] Reference Figure 3 Specifically, this step includes:
[0054] Step S301: Obtain authorization configuration from the activation file to be processed. Specifically, the authorization configuration includes the scope of authorized services, validity period, version number, etc.
[0055] Step S302: Obtain identification information of the client device in the authorization application, such as the physical address, universal unique identifier, etc. of the client device.
[0056] Step S303: Generate an authorization file containing the authorization configuration and identification information. Specifically, by combining the authorization configuration and identification information, generate an authorization file with the authorization configuration for a specific client device. Generating an authorization file containing identification information helps prevent the authorization file from being misused.
[0057] Step S105: Send the authorization file to the license software client. After the license software server completes the creation of the authorization file, it can send the authorization file to the license software client that initiated the authorization request, so that the database of the client device can use the corresponding function.
[0058] In the solution of this embodiment, a database and a licensed software client are configured on a client device, a licensed software server is configured on a server device, and activation files of multiple authorization types are configured on the licensed software server. After receiving an authorization request from the licensed software client, the licensed software server reads the authorization type requested in the authorization request, obtains an activation file that matches the authorization type requested, records it as a pending activation file, creates an authorization file based on the pending activation file, and sends the authorization file to the licensed software client. In other words, the licensed software server can receive different types of authorization requests, then create corresponding authorization files based on the configured activation files of the corresponding types, and then sends the authorization files to the licensed software client, enabling the database to use the corresponding database services. Therefore, the cooperation between the licensed software server and the licensed software client enables multiple types of database service authorization, improves the flexibility of database service authorization, simplifies the authorization operation process, and facilitates database users to flexibly adjust or select appropriate database services based on actual conditions, meeting the diverse needs of different application scenarios, and thus improving user experience. Furthermore, this simplifies the management process, conserves system resources, and improves system scalability.
[0059] like Figure 4 As shown, in one embodiment, the database authorization management method generally includes:
[0060] Step S401: The license software server receives an authorization application from the license software client.
[0061] Step S402: Read the authorization type of the authorization application request.
[0062] Step S403 , checking whether there is an available activation file that meets the authorization type requested by the authorization application. If so, executing step S404 ; otherwise, executing step S407 .
[0063] Specifically, the license software clients of multiple client devices can send authorization requests to the license software server of the same server device, so the activation files of the license software server may be exhausted. Therefore, after receiving the authorization request, it is necessary to check whether there is an activation file available for the requested authorization type.
[0064] The step of obtaining an activation file of the authorization type that meets the authorization application request, and if not, returning a preset authorization failure message to the license software client.
[0065] Specifically, if it is read that the authorization type of the authorization application request is a virtual processor authorization type, the step of checking whether there is an available activation file that meets the authorization type of the authorization application request includes:
[0066] Check whether the number of virtual processors that can be authorized by the virtual processor activation file is greater than or equal to the number of virtual processors requested by the authorization application. If so, determine that there is an available activation file that meets the authorization type requested by the authorization application; if not, determine that there is no available activation file.
[0067] Specifically, for virtual processor authorization types, the activation file of the licensing software server can pre-configure an activation file that supports multiple licensable virtual processors, and then authorize according to the number of virtual processors requested in the authorization application. When the number of virtual processors that can be authorized by the activation file does not meet the number requested by the authorization application, there is no activation file that meets the requirements. For example, the activation file of the licensing software server pre-configures 100 licensable virtual processors, and receives an authorization application for 30 virtual processors. 100 is greater than 30, so an authorization file can be created. As the authorization is given, the activation file has 10 licensable virtual processors remaining, and receives an authorization application for 20 virtual processors. 10 is less than 20, so there is no activation file that meets the requirements.
[0068] If the authorization type read in the authorization application request is an instance authorization type, the steps to check whether there is an activation file that meets the authorization type of the authorization application request include:
[0069] Check whether there is an available instance activation file. If so, determine that there is an available activation file that meets the authorization type requested by the authorization application. If not, determine that there is no available activation file.
[0070] Specifically, for instance authorization, each activation file on the license software server corresponds to one instance authorization. The license software server can pre-configure multiple activation files to support multiple licensable instances, and then issue instance authorizations based on authorization application requests. When all instance activation files are used up, no further instance authorizations can be made. For example, if the license software server pre-configures five activation files for instance authorization, it can create five instance authorization files and issue instance authorizations to up to five license software clients. If all instance activation files are used up and an authorization application for the instance authorization type is received, no activation files that meet the requirements will be available.
[0071] Step S404: Obtain an activation file that meets the authorization type requested by the authorization application and record it as an activation file to be processed.
[0072] Step S405: Create an authorization file based on the activation file to be processed.
[0073] Step S406: Send the authorization file to the licensing software client.
[0074] Step S407: Return the preset authorization failure information to the license software client. Specifically, the preset authorization failure information may include a prompt indicating that the activation file is insufficient.
[0075] In the solution of this embodiment, before the step of obtaining the activation file that meets the authorization type requested by the authorization application, it is checked whether there is an available activation file that meets the authorization type requested by the authorization application. If so, the step of obtaining the activation file that meets the authorization type requested by the authorization application is performed. If not, a preset authorization failure message is returned to the licensed software client, so that the database user can be prompted in time when the activation file is insufficient.
[0076] In addition, in one embodiment, the license software server pre-builds an activation file information table, which records the preset unique identifier of the activation file for each authorization type configured by the license software server and the usage of the activation file for each authorization type. For example, for a row of information recording a virtual processor authorization type, the first column may be the preset unique identifier corresponding to the virtual processor authorization type, the second column may be the number of remaining licensable virtual processors, and the third column may be the number of authorized virtual processors. For a row of information recording an instance authorization type, the first column may be the preset unique identifier corresponding to the instance authorization type, the second column may be the number of remaining licensable instance activation files, and the third column may be the number of used instance activation files.
[0077] By constructing an activation file information table, you can more quickly find the usage of activation files and determine whether there are available activation files.
[0078] like Figure 5 The figure shows a simplified schematic diagram of the database authorization system architecture of this embodiment. The license software server 300 is installed on the server device 100, and the license software client 400 is installed on the client device 200. A license software server 300 can communicate with multiple license software clients 400, receive different types of authorization requests, and then create and issue corresponding authorization files based on the authorization type of the authorization request. As shown in the figure, a license software client 400 can request virtual processor authorization from the license software server 300, and the license software server 300 will send it a virtual processor authorization file. Another license software client 400 can request instance authorization from the license software server 300, and the license software server 300 will send it an instance authorization file.
[0079] The licensing software server 300 and the licensing software client 400 work together to allow a single licensing software server 300 to issue authorizations to multiple licensing software clients 400 and various types of database service authorizations. This increases the flexibility of database service authorization and simplifies the authorization process, allowing database users to flexibly adjust or select appropriate database services based on their actual needs, meeting the diverse needs of different application scenarios and improving user experience. Furthermore, this simplifies management processes, conserves system resources, and enhances system scalability.
[0080] This embodiment also provides a computer device and a computer-readable storage medium. Figure 6 is a schematic diagram of a computer device 10 according to one embodiment of the present invention. Figure 7 is a schematic diagram of a computer-readable storage medium 20 according to one embodiment of the present invention.
[0081] The computer device 10 may include a memory 110, a processor 120, and a computer executable program 11 stored in the memory 110 and running on the processor 120, and the database authorization management method of any of the above embodiments is implemented when the processor 120 executes the computer executable program 11.
[0082] The computer-readable storage medium 20 stores a computer-executable program 11 thereon. When the computer-executable program 11 is executed by a processor, the database authorization management method of any of the above embodiments can be implemented.
[0083] This embodiment also provides a computer program product. Figure 8 1 is a schematic diagram of a computer program product 30 according to an embodiment of the present invention. The computer program product 30 includes a computer executable program 11. When the computer executable program 11 is executed by the processor 120, it can implement any of the above-mentioned database authorization management methods.
[0084] Specifically, the computer executable program 11 for performing the operations of the present invention can be assembly instructions, instruction set architecture (ISA) instructions, computer instructions, computer-related instructions, microcode, firmware instructions, state setting data, or source code or object code written in any combination of one or more programming languages.
[0085] For the purposes of the description of this embodiment, the computer-readable storage medium 20 can be any device that can contain, store, communicate, propagate, or transmit a program for use with an instruction execution system, device, or apparatus, or in conjunction with such instruction execution systems, devices, or apparatuses. More specific examples (a non-exhaustive list) of computer-readable media include the following: an electrical connection having one or more wirings (electronic devices), a portable computer disk cartridge (magnetic device), a random access memory (RAM), a read-only memory (ROM), an erasable and editable read-only memory (EPROM or flash memory), a fiber optic device, and a portable compact disc read-only memory (CDROM). In addition, the computer-readable storage medium 20 can even be paper or other suitable medium on which the program can be printed, since the program can be obtained electronically, for example, by optically scanning the paper or other medium, followed by editing, deciphering, or processing in other suitable ways as necessary, and then stored in a computer memory.
[0086] It should be understood that each part of the present invention can be implemented by hardware, software, firmware or a combination thereof. In the above embodiments, multiple steps or methods can be implemented by software or firmware stored in a memory and executed by a suitable instruction execution system.
[0087] Computer device 10 may be, for example, a server, a desktop computer, a laptop computer, a tablet computer, or a smartphone. In some examples, computer device 10 may be a cloud acquisition node. Computer device 10 may be described in the general context of computer system executable instructions (such as program modules) executed by a computer system. Generally, program modules may include routines, programs, object programs, components, logic, data structures, etc. that perform specific tasks or implement specific abstract data types. Computer device 10 may be implemented in a distributed cloud acquisition environment where remote processing devices linked via a communication network perform tasks. In a distributed cloud acquisition environment, program modules may be located on local or remote acquisition system storage media, including storage devices.
[0088] The computer device 10 may include a processor 120 adapted to execute stored instructions, and a memory 110 that provides temporary storage for the instructions during operation. The processor 120 may be a single-core processor, a multi-core processor, an acquisition cluster, or any number of other configurations. The memory 110 may include random access memory (RAM), read-only memory, flash memory, or any other suitable storage system.
[0089] The processor 120 may be connected to an I / O interface (input / output interface) suitable for connecting the computer device 10 to one or more I / O devices (input / output devices) via a system interconnect (e.g., PCI, PCI-Express, etc.). The I / O devices may include, for example, a keyboard and a pointing device, wherein the pointing device may include a touchpad or a touch screen, etc. The I / O devices may be built-in components of the computer device 10, or may be devices externally connected to an acquisition device.
[0090] Processor 120 can also be linked to the display interface that is suitable for connecting computer device 10 to display device through system interconnection.Display device can comprise the display screen that is built-in component of computer device 10.Display device can also comprise the computer monitor, television or projector etc. that are externally connected to computer device 10.In addition, network interface controller (network interface controller, NIC) can be suitable for connecting computer device 10 to network through system interconnection.In certain embodiments, NIC can use any suitable interface or protocol (such as Internet Small Computer System Interface etc.) to transmit data.Network can be cellular network, radio network, wide area network (WAN)), local area network (LAN) or Internet etc.Remote device can be connected to computer device through network.
[0091] At this point, those skilled in the art will recognize that, although a number of exemplary embodiments of the present invention have been shown and described in detail herein, many other variations or modifications consistent with the principles of the present invention may be directly determined or derived from the disclosure of the present invention without departing from the spirit and scope of the present invention. Therefore, the scope of the present invention should be understood and deemed to cover all such other variations or modifications.
Claims
1. A database authorization management method, comprising: The license software server receives an authorization application from a license software client, wherein the license software client is installed on a client device where a database is located, and the license software server is installed on a server device, and the license software server is configured with activation files of multiple authorization types; Read the authorization type of the authorization application request; Obtain an activation file of the authorization type that meets the authorization application request, and record it as a pending activation file; Create an authorization file based on the pending activation file; The authorization file is sent to the licensed software client.
2. The database authorization management method according to claim 1, wherein: The step of obtaining an activation file of an authorization type that meets the authorization application request includes: Check whether there is an available activation file that meets the authorization type requested by the authorization application; if so, execute the step of obtaining the activation file that meets the authorization type requested by the authorization application; if not, return a preset authorization failure message to the licensed software client.
3. The database authorization management method according to claim 2, wherein: The activation file includes a virtual processor activation file; If it is read that the authorization type of the authorization application request is a virtual processor authorization type, the step of checking whether there is an available activation file that meets the authorization type of the authorization application request includes: Check whether the number of virtual processors that can be authorized by the virtual processor activation file is greater than or equal to the number of virtual processors requested by the authorization application. If so, determine that there is an available activation file that meets the authorization type requested by the authorization application.
4. The database authorization management method according to claim 2, wherein: The activation file includes an instance activation file; If the authorization type of the authorization application request is read as an instance authorization type, the step of checking whether there is an available activation file that meets the authorization type of the authorization application request includes: Check whether there is an available instance activation file, and if so, determine whether there is an available activation file that meets the authorization type requested by the authorization application.
5. The database authorization management method according to claim 2, wherein: The activation file of each authorization type configured on the licensed software server is provided with a preset unique identifier. The steps of obtaining the activation file of the authorization type that meets the authorization application request include: Determine the corresponding preset unique identifier according to the authorization type of the authorization application request; The activation file is searched according to the corresponding preset unique identifier.
6. The database authorization management method according to claim 5, wherein: The licensed software server pre-builds an activation file information table, which records a preset unique identifier of an activation file of each authorization type configured by the licensed software server and usage of the activation file of each authorization type.
7. The database authorization management method according to claim 1, wherein: The step of producing an authorization file according to the activation file to be processed includes: Obtaining authorization configuration from the pending activation file; Obtaining identification information of the client device in the authorization application; Generate the authorization file containing the authorization configuration and the identification information.
8. A computer device comprising a memory, a processor, and a computer executable program stored in the memory and running on the processor, wherein the processor implements the database authorization management method according to any one of claims 1 to 7 when executing the computer executable program.
9. A computer-readable storage medium having a computer-executable program stored thereon, wherein the computer-executable program, when executed by a processor, implements the database authorization management method according to any one of claims 1 to 7.
10. A computer program product, comprising a computer executable program, wherein when the computer executable program is executed by a processor, the database authorization management method according to any one of claims 1 to 7 is implemented.