SQL Anywhere Feedback - All Databases Connected Under One Server Should...

Author

All Databases Connected Under One Server Should...

Steven J. Serenska

2005-06-02, 8:23 pm

....be able to access one another's data.

Like ASE and MS-SQL Server, if the user is connected to DB1 and DB2
within the same server, referencing the DBs' rows should be as simple as:

INSERT INTO
DB1..TableName
SELECT
*
FROM
DB2..TableName

Having to define and establish proxy tables beforehand is cumbersome.
Also, if you could make the above capability operate under the Run-time
License, my life would be complete.

Thanks for listening.

Steven J. Serenska

Breck Carter

2005-06-03, 11:23 am

I support this request.

ASA databases are marvelously portable, even across
different-endian machine architectures. If I could use START
DATABASE to enable *efficient* cross-database processing I
would be all for it.

I love proxy tables but they have two major drawbacks: (1)
the administrative overhead creating server, user and table
definitions, and (2) huge performance problems with certain
operations.

The ASE/MSS architecture and syntax are not important, per
se, IMO... whatever would enable *efficient* multi-database
SQL statements would be OK.

I would even live with proxy tables (drawback 1) if they
could be made blindingly fast when dealing with ASA
databasess running on the same server (drawback 2 solved).

Breck

> ...be able to access one another's data.
>
> Like ASE and MS-SQL Server, if the user is connected to
> DB1 and DB2 within the same server, referencing the DBs'
> rows should be as simple as:
>
> INSERT INTO
> DB1..TableName
> SELECT
> *
> FROM
> DB2..TableName
>
> Having to define and establish proxy tables beforehand is
> cumbersome. Also, if you could make the above capability
> operate under the Run-time License, my life would be
> complete.
>
> Thanks for listening.
>
> Steven J. Serenska
>

David Kerber

2005-06-03, 11:23 am

In article <42a07da1.73c3.1681692777@sybase.com>, Breck Carter says...

....

> I would even live with proxy tables (drawback 1) if they
> could be made blindingly fast when dealing with ASA
> databasess running on the same server (drawback 2 solved).

I'll second this motion! The vast majority of my proxy table operations
are between ASA databases, usually running on the same engine, and
practically always on the same physical machine.

--
Remove the ns_ from if replying by e-mail (but keep posts in the
newsgroups if possible).

Martin Baur

2005-06-03, 11:23 am

In article <42a07da1.73c3.1681692777@sybase.com>, Breck Carter says...
> ASA databases are marvelously portable, even across
> different-endian machine architectures. If I could use START
> DATABASE to enable *efficient* cross-database processing I
> would be all for it.

I also support this.

What I always was wondering: How should a company development deal with certain base data which are always needed everywhere like addresses, phone lists, product tables, and still from time to time
build some applications requiring new storage but also requiring access to that central data set. Because of some problems I faced int he early days of CREATE SERVER etc. I still do import some basic
data which - however - does not change or changes quite rarely instead of proxying them.

I strongly would like to be able to access other dbs. I however would like to extend the fully specified object path to include a database.

So

select *
from db.owner.table ...

This might fail if db is not running. START DATABASE solves this.

Martin

Sponsored Links