Use SQL Management Studio to browse the SIMS database. Under each SIMS database, you'll find an SQL branch called Views.
As an example, there's a view called
sims.rpt.vix_report_student. If you right click this view, then select Top 1000 rows, you can see how this view neatly joins the disparate tables and presents a nice coherent view of pupil records.
If you right-click a view and choose Design, you can see how the views are built from the underlying tables.
But for goodness sake, don't modify a view or you'll do a lot of damage. Only use a SELECT with views; an UPDATE can change the underlying tables directly - not good.
The good thing about views is that even if the underlying table structures change (and they often do), the names of the views remain static and any queries you write are likely to still work after upgrades.
You can use a view as part of a query, of course.
If you wanted to see the pupil details for a particular UPN, for instance, you could use this query:
Code:
select * from sims.rpt_vix_report_student sr
where sr.upn = '12345454'
With this one simple query, we can get a whole heap of data about a pupil. The view draws in fields from multiple tables. Try it to see what you get.
We can effectively treat a view as a table in its own right.