remote source

In making this substitution I had drawn upon the wisdom of a very remote source -the wisdom of my boyhood .

For relational sources, nickname statistics are usually automatically retrieved by lookup from the catalog of the remote source.

It allows you to investigate single remote source addresses and what alerts they generated.

Even if such queries are pushed down to the remote source, they can be very costly, especially if the remote object is large.

Our performance tests were conducted with a supported remote source.

In this example, assume that each "shipped" query requires complex, time consuming computation at the remote source.

An "o" indicates that the statistic is not easily available from the remote source.

Since only a single remote source is involved, enabling F2PC is not necessary -- there are no multi-site transactions.

The Remote Query operator submits a query to a remote source.

The DBA can enable F2PC for a particular remote source through use of the ALTER SERVER command.

You'll use it again later in this article when you get some JSON from a remote source.

Assume that there is a LINEITEM fact table on one remote source and a PART dimension table on another.

Later, you'll learn how to add more projects from local and remote source-code repositories.

F2PC to the remote source is enabled, and the federated server's logs are on a disk without write caching (green)

F2PC to the remote source is not enabled (blue)