New answers tagged view
If you haven't already, you might want to check out the Schema Changes History report available in SQL Server Management Studio. It looks like SQL Server logs changes by default (default trace) and you should be able to view that data via this report. The only unfortunate thing is that these trace files are automatically deleted/rolled over as time goes ...
The hint of the error message is right on target: You need an unconditional ON INSERT DO INSTEAD rule with a RETURNING clause. Bold emphasis mine. Per documentation: RETURNING queries on the view will be rejected if there is no RETURNING clause in any available rule. Don't confuse this with the RETURNS clause of your function. Not the same ...
There is no table or view that is the equivalent for records. You could achieve this by generating dynamic SQL in a PL/SQL script to produce selects against each table and then run each generated SQL using 'execute immediate'. Unfortunately I don't have the time to write up a quick script at the minute as I'm still at work.
DBA_TABLES.NUM_ROWS column can be used to identify tables that are empty. But this column is updated by DBMS_STATS, so it is not 100% accurate. There is no view that contains all records.
This is a bug, though one that only arises in very specific circumstances. SQL Server uses a component called Distributed Query (DQ) to build T-SQL commands to run against the linked server. The optimizer transforms a CASE expression including a sub-select to a form that works perfectly well on local objects, but which is not translated correctly to remote ...
OBSERVATION #1 The MySQL Documentation gives you the Restrictions on Views It is not possible to create an index on a view. Indexes can be used for views processed using the merge algorithm. However, a view that is processed with the temptable algorithm is unable to take advantage of indexes on its underlying tables (although indexes can be used ...
Top 50 recent answers are included