Abstract: The present disclosure provides an apparent resistivity-depth section generating method for short-offset electromagnetic exploration, including: determining, in field zones divided quantitatively based on the induction number, positions of a recording point for each of observation points and frequencies or a time window thereof, and taking determined positions of the recording point as the assignment point for the observation point and the frequencies or the time window thereof, where one survey line of an axial configuration generates one apparent resistivity-depth section along the survey line; and one survey line of an equatorial configuration typically generates one apparent resistivity-depth section along the survey line, and apparent resistivity-depth sections along connecting lines from the observation points to the source which are the same as observation points in the number.

Abstract: The present disclosure provides an apparent resistivity-depth section generating method for short-offset electromagnetic exploration, including: determining, in field zones divided quantitatively based on the induction number, positions of a recording point for each of observation points and frequencies or a time window thereof; and taking determined positions of the recording point as the assignment point for the observation point and the frequencies or the time window thereof, where one survey line of an axial configuration generates one apparent resistivity-depth section along the survey line; and one survey line of an equatorial configuration typically generates one apparent resistivity-depth section along the survey line, and apparent resistivity-depth sections along connecting lines from the observation points to the source which are the same as observation points in the number.

Abstract: Implementations include providing, by a computer-executed migration advisor executing within a run-time of a source database system, a query data set including queries processed by the source database system during production use of the source database system, providing, by the migration advisor, an object data set including data representative of database objects stored within a database of the source database system, generating, by the migration advisor, a list of query-level features and a list of object-level features, each feature in the list of query-level features and each feature in the list of object-level features including a feature that is deprecated in a target database system, resolving one or more issues represented by features of one or more of the list of query-level features and the list of object-level features, and executing migration of the database of the source database system to the database of the target database system.

Abstract: The present disclosure involves systems, software, and computer implemented methods for performing dynamic topology switch in a failover operation. In one example, a failover of a first node is determined. The first node includes a first data server and a first replication server. At least one user application connects to the first data server prior to the failover of the first node. In response to the determined failover, the at least one user application is connected to a second data server of a second node. The second node includes the second data server and a second replication server. Prior to the failover of the first node, a data replication topology of the second node is a remote topology. During the failover, if the first replication server on the first node is down, the data replication topology of the second node is switched from the remote topology to a local topology.

Abstract: The present disclosure involves systems, software, and computer implemented methods for performing dynamic topology switch in a failover operation. In one example, a failover of a first node is determined. The first node includes a first data server and a first replication server. At least one user application connects to the first data server prior to the failover of the first node. In response to the determined failover, the at least one user application is connected to a second data server of a second node. The second node includes the second data server and a second replication server. Prior to the failover of the first node, a data replication topology of the second node is a remote topology. During the failover, if the first replication server on the first node is down, the data replication topology of the second node is switched from the remote topology to a local topology.

Abstract: The present disclosure involves systems, software, and computer implemented methods for performing dynamic topology switch in a failover operation. In one example, a failover of a first node is determined. The first node includes a first data server and a first replication server. At least one user application connects to the first data server prior to the failover of the first node. In response to the determined failover, the at least one user application is connected to a second data server of a second node. The second node includes the second data server and a second replication server. Prior to the failover of the first node, a data replication topology of the second node is a remote topology. During the failover, if the first replication server on the first node is down, the data replication topology of the second node is switched from the remote topology to a local topology.

Abstract: The present disclosure involves systems, software, and computer implemented methods for performing dynamic topology switch in a failover operation. In one example, a failover of a first node is determined. The first node includes a first data server and a first replication server. At least one user application connects to the first data server prior to the failover of the first node. In response to the determined failover, the at least one user application is connected to a second data server of a second node. The second node includes the second data server and a second replication server. Prior to the failover of the first node, a data replication topology of the second node is a remote topology. During the failover, if the first replication server on the first node is down, the data replication topology of the second node is switched from the remote topology to a local topology.