Abstract: Systems and methods for tokenizing data in a public cloud are disclosed. According to an embodiment, a method may include: (1) receiving, at a tokenization service in a public cloud and from a client application, source data associated with one of a plurality of namespaces; (2) generating, by the tokenization service, a token for the source data according to a token format rule, wherein the token format rule specifies one or more digit in the token format that are reserved; (3) encrypting, by the tokenization service, the source data; (4) associating, by the tokenization service, the token with the encrypted source data; (5) persisting, by the tokenization service, the association between the token and the encrypted source data in a token table in the public cloud; and (6) providing, by the tokenization service, the token to the client application.

Abstract: Systems and methods for restricting access to tokenization services are disclosed. A method may include: receiving, at a computer program in a public cloud and from a client application for a client executed by an electronic device, onboarding information; setting, by the computer program, entitlements for the client application or the client to access a plurality of services in the public cloud; receiving, by the computer program, a request to access one of the plurality of services in the public cloud from the client application; determining, by the computer program, that the client application or the client is entitled to access the service to execute the request based on the entitlements for the client application or the client; and granting, by the computer program, access to the service to execute the request; wherein the service is configured to execute the request and return data to the client application.

Abstract: A relational database may be integrated into an integrated circuit design and analysis environment as the persistent data store for data associated with the design. This design data may include two or more abstractions of the design, such as layout data models and timing data models, in some embodiments. Design data may be partitioned in the database and indexed according to various attributes. The use of a relational database may facilitate cross-probing of design data corresponding to different abstractions of the design. The relational database may be queried to produce design reports and to identify design errors or weaknesses. Reports may be graphical or tabular, and may be displayed, printed, stored, or posted for viewing. Proposed modifications to a design may be investigated by modifying data in the relational database, rather than in the actual design. Design reports may be re-generated and compared with corresponding reports for the un-modified design.

Abstract: A relational database may be integrated into an integrated circuit design and analysis environment as the persistent data store for data associated with the design. This design data may include two or more abstractions of the design, such as layout data models and timing data models, in some embodiments. Design data may be partitioned in the database and indexed according to various attributes. The use of a relational database may facilitate cross-probing of design data corresponding to different abstractions of the design. The relational database may be queried to produce design reports and to identify design errors or weaknesses. Reports may be graphical or tabular, and may be displayed, printed, stored, or posted for viewing. Proposed modifications to a design may be investigated by modifying data in the relational database, rather than in the actual design. Design reports may be re-generated and compared with corresponding reports for the un-modified design.

Abstract: A mechanism is disclosed for migrating large data sets for product upgrades. In one embodiment, an identifier is received as a parameter of a first method of an API. In response to the receipt of the identifier as a parameter of the first method, a utility is invoked. The utility exports, as one or more transportable tablespaces, one or more database objects that are associated with the identifier in a database. The identifier is also received as a parameter of a second method of the same API. In response to the receipt of the identifier as a parameter of the second method of the API, a utility is also invoked. The utility imports, into the database, database objects that are contained in the one or more transportable tablespaces. The utility also associates, with the identifier, the database objects that are contained in the one or more transportable tablespaces.