|
I'm frequently using proxy tables for existing remote tables/views. The CREATE EXISTING TABLE syntax is very convenient for that, particularly as I don't have to specify column names and types then. However, when the remote table/view is altered lateron (say, to add a column), this change is not applied to the proxy table. Furthermore, it seems to be forbidden to use ALTER TABLE on a proxy table to add new columns "manually". As a consequence, one has to drop and recreate the proxy table (and re-assign the according permissions). Therefore, it would by handy if there was as statement like working similar to the ALTER VIEW RECOMPILE statement, i.e. it should regenerate the column definitions (and automatically drop/recreate indexes) based on the remote table. |
|
Just to complete: The answer from Karim Khamis [Sybase] in the product futures NG:
2
Well, it's been a very old request, and just today I ran over it again... ALTER TABLE would be handy for proxy tables particulary when privileges have to be rebuilt after the workaround via DROP TABLE/CREATE TABLE.
(15 Mar '21, 13:39)
Volker Barth
Replies hidden
OMG it's only been eleven years since the last time someone asked for this feature! :)
(16 Mar '21, 16:58)
Breck Carter
2
I have subscribed to this thread. Let's meet in eleven years again to check the status.
(19 Mar '21, 08:28)
Vlad
Comment Text Removed
|
It's a shame that you have to specify the table in detail at all - I believe in SQLServer you just add a reference to the database and then you can use any object you have rights to.
@Justin: AFAIK, that's only true when you relate to different databases on the same database server, and that's a consequence of the SQL Server/ASE "master database architecture". When relating to a different server (via MS linked server), it works similar to SA proxy tables, methinks.