Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You shouldn't be needing that.</p> <p>If you are concerned about differences of your views and your underlying tables, then you should schemabind your views. That way your table can't be modified in the way it clashes with view definition. In addition, you can't use <code>SELECT *</code> in a schemabound view.</p> <p>However, if you want to play with automatic view refreshing, here's the idea:</p> <pre><code>CREATE VIEW tv AS SELECT * FROM dbo.t1 UNION ALL SELECT * FROM dbo.t2 GO CREATE TRIGGER alterView ON DATABASE FOR ALTER_TABLE AS EXEC sp_refreshview 'tv' GO ALTER TABLE dbo.t1 ADD txt nvarchar(18) ALTER TABLE dbo.t2 ADD txt nvarchar(18) </code></pre> <p>However, you will notice that it's not possible to do alter in the first place, because it would break the 'equal number of expressions' rule for the view.</p> <p><em>EDIT</em></p> <p>I could have missed the point because I maybe didn't understand the question. If you want to alias, you can use <a href="http://technet.microsoft.com/en-us/library/ms177544.aspx" rel="nofollow">SYNONYMS</a>. If combined with schema, you can use them to alias a view:</p> <pre><code>CREATE SCHEMA TEST GO CREATE SYNONYM TEST.t1 FOR dbo.tv GO SELECT * FROM TEST.t1 GO </code></pre> <p>If your focus is on the syntax, you will notice that new t1 aliased view is prefixed woth the schema. However, if you wrap that with procedure, you can loose the prefix and data will be selected from your aliased view.</p> <pre><code>CREATE PROCEDURE TEST.TestProc AS SELECT * FROM t1 </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POinstead of select table?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USOzrenTkalcecKrznaric
    1. USOzrenTkalcecKrznaric
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COi don't get this, if i do `select * from t1`, i still only get records from t1, what i would want is to get the records from t1 and t2 (view tv), the schema of the tables will not change.
      singulars
      1. PO
      1. USRMiranda
    2. COi get error `There is already an object named 't1' in the database.` when i try to create the SYNONYM, i guess this cannot be done, which is acceptable has my premise is pretty dumb :P
      singulars
      1. PO
      1. USRMiranda
    3. COWell, it depends how you look at it. let's say that you have to use a large procedure for reporting, don't have time to analyze it and have to append a bunch of data to one of the tables used in query. And must not break the schema. This could be one way to do it.
      singulars
      1. PO
      1. USOzrenTkalcecKrznaric
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload