Re: Sybase and materialized views
- From: "Kristian Damm Jensen" <kristiandamm@xxxxxxxx>
- Date: Thu, 22 Dec 2005 20:49:18 +0100
"Galen Boyer" <galen_boyer@xxxxxxxxx> wrote in message
news:u1x05q18g.fsf@xxxxxxxxxx
> On Wed, 21 Dec 2005, kristiandamm@xxxxxxxx wrote:
>>
>> If on the other hand, the view is based on a number of other tables,
>> each of may have data inserted and updated independently, I would be
>> more wary of such an undertaking. The complexity of the maintenance
>> could be great indeed, even without considering problems with
>> multithreaded updating: syncronisation, locking, etc.
>
> Multiple tables aren't an issue with Oracle for Materialized Views.
Meaning - I suppose - that Oracle has no problems materializing a view,
regardless of the complexity and number of tables in the defining select.
I know that.
I was simply presenting som considerations on how to implement something
like materailized views in Sybase ASE.
Regards,
Kristian Damm Jensen
.
- References:
- Sybase and materialized views
- From: supergel
- Re: Sybase and materialized views
- From: DA Morgan
- Re: Sybase and materialized views
- From: Carl Kayser
- Re: Sybase and materialized views
- From: Galen Boyer
- Re: Sybase and materialized views
- From: sybdba
- Re: Sybase and materialized views
- From: Galen Boyer
- Re: Sybase and materialized views
- From: Kristian Damm Jensen
- Re: Sybase and materialized views
- From: Galen Boyer
- Sybase and materialized views
- Prev by Date: Re: Capture return from sybase in shell script
- Next by Date: Re: get everything from table A that is not in table B
- Previous by thread: Re: Sybase and materialized views
- Next by thread: Re: Sybase and materialized views
- Index(es):
Relevant Pages
|