Abstract: Systems, devices, and methods are provided for determining whether security assurances are satisfied by security policies that are used to control access to resources used by a mainframe application. A system may use a database to store a plurality of security policies that may comprise security polices of various resources used by mainframes, including resources managed by operating systems and database systems. A reference policy that corresponds to the security assurance being sought may be determined. The security policies may be evaluated using a satisfiability modulo theories (SMT) solver to determine whether the security policies are equally or less permissive than the reference policy.

Abstract: Systems, devices, and methods are provided for authorizing access to database management system (DBMS) resources using security policies managed by a service external to the DBMS. A DBMS may be provisioned to obtain a database request, identify one or more securable resources that from applications, determine a request context for the system call, and sends a request to an external policy management service. The policy management service may be used to perform a policy evaluation to determine whether to grant access to the securable resources. In some cases, policies are cached by the DBMS. In various examples, the DBMS and policy management service are both hosted on resources managed by a computing resource service provider on behalf of a customer to run mainframe workloads.

Abstract: Systems, devices, and methods are provided for authorizing access to database management system (DBMS) resources using security policies managed by a service external to the DBMS. A DBMS may be provisioned to obtain a database request, identify one or more securable resources that from applications, determines a request context for the system call, and sends a request to an external policy management service. The policy management service may be used to perform a policy evaluation to determine whether to grant access to the securable resources. In some cases, policies are cached by the DBMS. In various examples, the DBMS and policy management service are both hosted on resources managed by a computing resource service provider on behalf of a customer to run mainframe workloads.

Abstract: A workload of a database may be evaluated to provide a database migration recommendation. A request for a recommendation to migrate a database to a new host may be received. An evaluation of the workload of a client application of the database at a current host may be performed. The migration recommendation may be returned based on the evaluation of the workload of the client application of the database. In some embodiments, the migration recommendation may trigger an automated migration of the database to the new host.

Abstract: A system such as a service of a computing resource service provider includes executable code that, if executed by one or more processors, causes the one or more processors to identify a set of resources associated with a first database system, determine, based at least in part on the set of resources, an expected outcome of an operation of a second database system, and generate, executable code that, if executed, verifies an actual outcome of the operation of the second database system against the expected outcome. The system may be utilized as part of a database migration process where data from a first database system is transferred to a second database system.

Abstract: The reliability of an application is improved by analyzing and implementing changes to application infrastructure that is represented, in some examples, as Infrastructure as Code (“IAC”). The system performs various tests on the infrastructure to determine how the infrastructure responds to failures and whether recovery procedures and monitoring services in place are effective and functioning properly. Various examples provide a measure of infrastructure resiliency that can be used to evaluate potential changes to application infrastructure.

Abstract: Data is migrated between a source database and a target database. The source database management system (“DBMS”) remains operational during the migration. A user selects the source DBMS and target DBMS, provides connection information used to connect to the database management systems and selects a virtual machine instance to perform the migration in conjunction with a database migration service. After the setup is complete, the virtual machine instance in conjunction with the database migration service performs data type transformations, and other operations, without user intervention. The database migration service also converts, without user intervention, the source schema and code to a format compatible with the target DBMS. Any code that is not converted is marked to assist the user of the database migration service identify where manual re-coding is required. The database migration service can also provide recommendations as to a target DBMS that is a suitable target DBMS.

Abstract: Distributed extraction of data for migration may be implemented for migrating data sets from a first data store to a second data store. Assignments may be determined for different migration agents to obtain and store the data set in the second data store along with a format for storing the assigned data set portions. The migration agents may then be caused to obtain the assigned portions and store the assigned portions in the second data store according to the identified format. Further operations to request or direct the ingestion of the data set from the second data store may be performed by migration agents with respect to a third data store that performs data ingestion.

Abstract: Described herein is technology for replicating data from a source database to one or more target databases at different points in time. The system receives a request to replicate a data set stored in a source database. The system stores a copy of a first subset of the data set from the source database to a target database at a first time. The system stores a copy of a second subset of the data set from the source database to the target database at a second time.

Abstract: A method and system for validating data migrated from a source database to a target database and storing validation metrics resulting from validating the data are described. The system receives validation information to be used to validate data to be migrated from a source database to a target database. The system validates the data using the validation information and stores validation metrics resulting from validating the data.

Abstract: Data is migrated between a source database and a target database. The source database management system (“DBMS”) remains operational during the migration. A user selects the source DBMS and target DBMS, provides connection information used to connect to the database management systems and selects a virtual machine instance to perform the migration in conjunction with a database migration service. After the setup is complete, the virtual machine instance in conjunction with the database migration service performs data type transformations, and other operations, without user intervention. The database migration service also converts, without user intervention, the source schema and code to a format compatible with the target DBMS. Any code that is not converted is marked to assist the user of the database migration service identify where manual re-coding is required. The database migration service can also provide recommendations as to a target DBMS that is a suitable target DBMS.

Abstract: Validation of a migration task to migrate data from one data store to another may be performed prior to the migration of the data. Parameters associated with the migration may be evaluated according to one or more types of validations for the migration task. In some embodiments, users may specify the validations to perform for the migration task. A determination as to whether the migration task is valid may be performed for the migration task based on the parameter evaluations. A result indicating whether the migration task is valid may be provided to a user.

Abstract: Errors may be detected and mitigated during the migration of data. Migration of data from a source data store to a target data store may be monitored for errors. When an error is detected, one or more responsive actions may be identified to modify performance of the migration. In some embodiments, responsive actions may include further analyses to validate the migration. In some embodiments, the responsive actions may be corrective actions to correct the detected error. Once identified, the responsive actions may be performed to modify performance of the migration.

Abstract: Example embodiments of the present invention provide a method, a system, and a computer program product for cloud services business management. The method includes monitoring cloud services business metrics for a cloud services provider and analyzing the cloud services business metrics. Cloud services business parameters for the cloud services provider then may be acted upon according to the analyzed cloud services business metrics.

Abstract: Data is migrated between a source database and a target database. The source database management system (“DBMS”) remains operational during the migration. A user selects the source DBMS and target DBMS, provides connection information used to connect to the database management systems and selects a virtual machine instance to perform the migration in conjunction with a database migration service. After the setup is complete, the virtual machine instance in conjunction with the database migration service performs data type transformations, and other operations, without user intervention. The database migration service also converts, without user intervention, the source schema and code to a format compatible with the target DBMS. Any code that is not converted is marked to assist the user of the database migration service identify where manual re-coding is required. The database migration service can also provide recommendations as to a target DBMS that is a suitable target DBMS.

Abstract: A geographically distributed storage system for managing the distribution of data elements wherein requests for given data elements incur a geographic inertia. The geographically distributed storage system comprises geographically distributed sites, each comprises a site storage unit for locally storing a portion of a globally coherent distributed database that includes the data elements and a local access point for receiving requests relating to ones of the data elements. The and geographically distributed storage system comprises a data management module for forwarding at least one requested data element to the local access point at a first of the geographically distributed sites from which the request is received and storing the at least one requested data element at the first site, thereby to provide local accessibility to the data element for future requests from the first site while maintaining the globally coherency of the distributed database.

Abstract: A database system includes: a first database having back-end functionality for data storage and database query execution, a database front-end and an interception unit. The database front-end is configured for processing user queries directed to a back-end of a second database, and lacks the capabilities for directly accessing the first database. The interception unit is networked with the first database over a data network, and is configured for monitoring user queries under processing by the front-end to identify queries pertaining to data stored in the first database, and redirecting the identified queries to the first database for execution. Thereby the functionality of the database front-end is provided for data stored in the first database.

Abstract: A data access system decouples the data processing from the data storage to provide improved accessibility, integrity, scalability and other features. The system comprises: database units arranged in virtual partitions each independently accessible, a plurality of data processing units, and a switching network for switching the data processing units between the virtual partitions, thereby to assign data processing capacity dynamically to respective virtual partitions.

Abstract: A geographically distributed storage system for managing the distribution of data elements wherein requests for given data elements incur a geographic inertia. The geographically distributed storage system comprises geographically distributed sites, each comprises a site storage unit for locally storing a portion of a globally coherent distributed database that includes the data elements and a local access point for receiving requests relating to ones of the data elements. The and geographically distributed storage system comprises a data management module for forwarding at least one requested data element to the local access point at a first of the geographically distributed sites from which the request is received and storing the at least one requested data element at the first site, thereby to provide local accessibility to the data element for future requests from the first site while maintaining the globally coherency of the distributed database.

Abstract: According to some embodiments of the present invention there is provided a method and a system for managing data storage in a plurality of data partitions, such as replica databases. The method is based on analyzing, for each physical data partition, the received memory access queries. Each memory access query has a different result table which is based on different fields. This analysis is performed to determine the frequency of receiving each one of the memory access queries. The analysis allows, for one or more of the analyzed memory access queries, associating between at least one key of a respective result table and at least one of the physical data partitions. In such an embodiment, data elements are stored according to a match with respective said at least one key.