Re: Creating relationship between views
- From: buckleyjs@xxxxxxxxx
- Date: 4 Jan 2007 16:07:29 -0800
If this is a 3rd party database, you run the risk of schema changes
with future upgrades. Given that, you do what you want.
I think I understand what you'd like to do. You can use your views to
join tables on like items. It may speed up reporting.
Be careful doing this though. You could jeapordize your contract with
the vendor if you alter "their" database. I'd suggest creating views
within your own reporting database pointing at that source database.
3rd party applications are often written so generic that they don't
lend to good adhoc queries but lend to portability.
On Jan 3, 8:10 am, "Sue" <iyer_san...@xxxxxxxxxxx> wrote:
This is a 3rd party database which does not have any refrential
integrity built on the tables, but the application would take care of
it. I'm trying to do some adhoc reporting with it. And for that as a
general rule, we use the views and not the tables. We are trying to see
if we could create those relationships on the views we have written in
the database instead of doing so in the DataSourceViews in Adhoc.
Ed Murphy wrote:
Sue wrote:
Is there a way to create a relationship between the views in a
database.
More like a Primary - Foreign key relationship like you would do for
Tables.
Why wouldn't you just create a relationship between the tables
underlying each view?
.
- References:
- Creating relationship between views
- From: Sue
- Re: Creating relationship between views
- From: Ed Murphy
- Re: Creating relationship between views
- From: Sue
- Creating relationship between views
- Prev by Date: Re: Reports
- Next by Date: Re: WEEK of the MONTH Brain Twister...
- Previous by thread: Re: Creating relationship between views
- Next by thread: SQLServer 2000 tray icon shows password
- Index(es):
Relevant Pages
|
|
