Question Re: LOCAL ONLY in Technology Q&A

LOCAL ONLY

JimDiaz — Wed, 07 Aug 2024 14:36:26 GMT

When creating an existing table I add the LOCAL ONLY syntax to prevent the creation from failing if the remote server does not exist. Is there an equivalent for procedure/functions?

Thanks, Jim

Re: LOCAL ONLY

jack_schueler — Thu, 08 Aug 2024 10:57:25 GMT

What does the syntax look like for LOCAL ONLY? Can you post an example?

Re: LOCAL ONLY

JimDiaz — Thu, 08 Aug 2024 21:11:14 GMT

Sure It's the CREATE EXISTING TABLE syntax with LOCAL ONLY for example

CREATE EXISTING TABLE Owner.TableName( AttributeNameOne INTEGER NOT NULL, AttributeNameTwo CHAR(128) NOT NULL ) AT 'Server;Owner;TableName' LOCAL ONLY;

You can see this in a unload script from a database with remote servers and tables.

Re: LOCAL ONLY

JimDiaz — Mon, 12 Aug 2024 10:02:25 GMT

In doing some more testing the LOCAL ONLY after the CREATE EXISTING TABLLE syntax fails if the remote server is not defined. However it works if the remote server is defined but doesn't actually exist (no connection available).

When the remote server is defined a proxy procedure/function can also be created when no connection is available.

It's a bit confusing as to why LOCAL ONLY is required for the tables and not procedures/functions.

Jim

Re: LOCAL ONLY

VolkerBarth — Tue, 13 Aug 2024 05:00:19 GMT

In my understanding LOCAL ONLY is a "hidden clause" internally used for reload/extract scripts, just as the "GRANT CONNECT... AT <userid>" clause.

Are you dealing with a MobiLink or SQL Remote setup?

Re: LOCAL ONLY

JimDiaz — Tue, 13 Aug 2024 05:28:04 GMT

That's my understanding as well. We use SQL Remote, we've done some work with MobiLink but most our remotes are maritime vessels with low bandwidth and inconsistent connections.