Abstract: Various example embodiments are directed to systems and methods for migrating a database from a source database having a source schema to a target database having a target schema. For example the migrating may comprise a pre-migration phase and a migration phase. The pre-migration phase may comprise either executing a pre-migration command to modify at least a portion of the source database or generating a pre-migration object at the source database. The migration phase may comprise selecting at least one column from the source database that was modified during the pre-migration phase and writing the at least one column to the target database.

Abstract: A provisioning system to automatically determine the appropriate components to install or make available for installation on a target computer system. An example system may comprise: receiving data indicative of a bit-size and a virtual machine extension support of a processing device of the client device; determining that the processing device supports a plurality of bit-size versions of a software component; querying the client device to select a preferred version of the software component associated with the virtual machine extension support; determining that the version of a software component associated with the first bit-size is unavailable; provisioning the version of the software component associated with the virtual machine extension support and the second bit-size to the client device in view of the determination; and notifying the client device when the version of the software component associated with the first bit-size and the virtual machine extension support is available for installation.

Abstract: A provisioning system to automatically determine the appropriate components to install or make available for installation on a target computer system. An example system may comprise: receiving data indicative of a bit-size and a virtual machine extension support of a processing device of the client device; determining that the processing device supports a plurality of bit-size versions of a software component; querying the client device to select a preferred version of the software component associated with the virtual machine extension support; determining that the version of a software component associated with the first bit-size is unavailable; provisioning the version of the software component associated with the virtual machine extension support and the second bit-size to the client device in view of the determination; and notifying the client device when the version of the software component associated with the first bit-size and the virtual machine extension support is available for installation.

Abstract: A provisioning system to automatically determine the appropriate components to install or make available for installation on a target computer system. The provisioning system ensures the provisioning of software components that are appropriate to each target computer system without requiring user input. The provisioning system can identify support for 64-bit software components. The provisioning system checks a field in the processor to determine longword, that is 64-bit support, or checks an entry in a file maintained by an operating system to determine 64 bit support. If 64-bit support is not detected then a 32-bit component is installed to ensure that the target computer system is capable of executing the software component.

Abstract: Various example embodiments are directed to systems and methods for migrating a database from a source database having a source schema to a target database having a target schema. For example the migrating may comprise a pre-migration phase and a migration phase. The pre-migration phase may comprise either executing a pre-migration command to modify at least a portion of the source database or generating a pre-migration object at the source database. The migration phase may comprise selecting at least one column from the source database that was modified during the pre-migration phase and writing the at least one column to the target database.

Abstract: Various example embodiments are directed to systems and methods for migrating a database from a source database having a source schema to a target database having a target schema. For example, a computing device may identify a first source schema table associated with a first migration instruction. The first migration instruction may comprise a plurality of migration instruction sets. Each of the plurality of migration instruction sets may correspond to a version of the first source schema table. The computing device may determine that there is a match between the first source schema table and a first migration instruction set and may execute the first migration instruction set. Executing the first migration instruction set may comprise selecting at least one column of the first source schema table and writing the at least one column of the first source schema table to a first target schema table.

Abstract: A registration process for computers as part of a provisioning system that automatically determines the appropriate components to install in each computer system. The registration process ensures that the configuration information necessary for provisioning of software components that are appropriate to each system are collected. The registration process can identify support for 64-bit components. The registration process checks a field in the processor to determine longword, that is 64-bit support, or checks an entry in a file maintained by an operating system to determine 64-bit support.

Abstract: The present invention provides methods and systems for dynamically generating configuration files used in installing software distributions and software installation testing. In particular, the present invention employs a framework comprising an API to discover and monitor an inventory of distributions, a set of templates for the configuration files, and plugins that may be selectively invoked to customize the configuration files. When performing installation testing, a server will access the distribution inventory and select appropriate templates that are to be part of the test. The server will then automatically generate the installation configuration files from the templates. The server may also execute one or more plugins that customize the configuration files as desired. Small client applications run on the target machines of the installation tests and are used to download the configuration files and the distributions.

Abstract: The present invention provides methods and systems for dynamically generating configuration files used in installing software distributions and software installation testing. In particular, the present invention employs a framework comprising an API to discover and monitor an inventory of distributions, a set of templates for the configuration files, and plugins that may be selectively invoked to customize the configuration files. When performing installation testing, a server will access the distribution inventory and select appropriate templates that are to be part of the test. The server will then automatically generate the installation configuration files from the templates. The server may also execute one or more plugins that customize the configuration files as desired. Small client applications run on the target machines of the installation tests and are used to download the configuration files and the distributions.

Abstract: An upgrade controller that compares the contents of a reference database with an upgraded database is described. In one embodiment, the upgrade controller connects to the reference and upgraded database and retrieves the list of tables. For each of the tables, the upgrade controller compares the content of the reference and the upgraded table. The upgrade controller compares the table contents by comparing the contents on a record-by-record basis. In addition, the upgrade controller can use a whitelist of tables and columns to reduce the number of false positive(s) that could be generated during the comparison.

Abstract: An upgrade controller that compares the contents of a reference database with an upgraded database is described. In one embodiment, the upgrade controller connects to the reference and upgraded database and retrieves the list of tables. For each of the tables, the upgrade controller compares the content of the reference and the upgraded table. The upgrade controller compares the table contents by comparing the contents on a record-by-record basis. In addition, the upgrade controller can use a whitelist of tables and columns to reduce the number of false positive(s) that could be generated during the comparison.

Abstract: Some embodiments of a system and a method to validate database schema upgrade using denormalization have been presented. For instance, a database deployment engine may upgrade a database from a first version to a second version. The database upgraded stores a set of entities. By applying denormalization to both the upgraded database and a reference database (which contains a newly installed second version of the database), a database validation engine may reduce false positives during validation of the database schema upgrade scripts usable by customers to upgrade their database schema to the latest version.

Abstract: A registration process for computers as part of a provisioning system that automatically determines the appropriate components to install in each computer system. The registration process ensures that the configuration information necessary for provisioning of software components that are appropriate to each system are collected. The registration process can identify support for 64-bit components. The registration process checks a field in the processor to determine longword, that is 64-bit support, or checks an entry in a file maintained by an operating system to determine 64-bit support.

Abstract: A provisioning system to automatically determine the appropriate components to install or make available for installation on a target computer system. The provisioning system ensures the provisioning of software components that are appropriate to each target computer system without requiring user input. The provisioning system can identify support for 64-bit software components. The provisioning system checks a field in the processor to determine longword, that is 64-bit support, or checks an entry in a file maintained by an operating system to determine 64 bit support. If 64-bit support is not detected then a 32-bit component is installed to ensure that the target computer system is capable of executing the software component.

Abstract: The present invention provides methods and systems for dynamically generating configuration files used in installing software distributions and software installation testing. In particular, the present invention employs a framework comprising an API to discover and monitor an inventory of distributions, a set of templates for the configuration files, and plugins that may be selectively invoked to customize the configuration files. When performing installation testing, a server will access the distribution inventory and select appropriate templates that are to be part of the test. The server will then automatically generate the installation configuration files from the templates. The server may also execute one or more plugins that customize the configuration files as desired. Small client applications run on the target machines of the installation tests and are used to download the configuration files and the distributions.

Abstract: The present invention provides methods and systems for dynamically generating configuration files used in installing software distributions and software installation testing. In particular, the present invention employs a framework comprising an API to discover and monitor an inventory of distributions, a set of templates for the configuration files, and plugins that may be selectively invoked to customize the configuration files. When performing installation testing, a server will access the distribution inventory and select appropriate templates that are to be part of the test. The server will then automatically generate the installation configuration files from the templates. The server may also execute one or more plugins that customize the configuration files as desired. Small client applications run on the target machines of the installation tests and are used to download the configuration files and the distributions.