SQL Anywhere Feedback

Author

Jasper?

Richard Biffl

2005-08-23, 7:24 am

What have you TechWave attendees learned about SQL Anywhere 10? The press
release mentioned materialized views, hot failover, and profiling tools. It
also mentioned MobiLink development tools, but I can't tell whether that's
part of SQL Anywhere 10 or a separate product.

Richard

Breck Carter [TeamSybase]

2005-08-23, 8:23 pm

All part of Jasper.

On 22 Aug 2005 23:32:10 -0700, "Richard Biffl"
< sybaseforums@removve
thiisphrraseblacklet
tersoftware.com> wrote:

>What have you TechWave attendees learned about SQL Anywhere 10? The press
>release mentioned materialized views, hot failover, and profiling tools. It
>also mentioned MobiLink development tools, but I can't tell whether that's
>part of SQL Anywhere 10 or a separate product.
>
> Richard
>
>

--
SQL Anywhere Studio 9 Developer's Guide
Buy the book: http://www.amazon.com/exec/obidos/A...7/risingroad-20
bcarter@risingroad.com
RisingRoad SQL Anywhere and MobiLink Professional Services
www.risingroad.com

Andre Schild

2005-08-24, 1:23 pm

Richard Biffl schrieb:
> What have you TechWave attendees learned about SQL Anywhere 10? The press
> release mentioned materialized views, hot failover, and profiling tools. It

Materialized views !

When will ASA 10 be available ?

We do sometimes such "materialzed" views via caching tables with all the
nasty "features" this gives....

André

Greg Fenton

2005-08-25, 3:31 am

Andre Schild wrote:
>
> When will ASA 10 be available ?
>

Last I've seen posted to the newsgroups is "H1 2006".

greg.fenton
--
Greg Fenton
Consultant, Solution Services, iAnywhere Solutions
--------
Visit the iAnywhere Solutions Developer Community
Whitepapers, TechDocs, Downloads
http://www.ianywhere.com/developer/

Andre Schild

2005-08-25, 3:31 am

Greg Fenton schrieb:
> Andre Schild wrote:
>
>
> Last I've seen posted to the newsgroups is "H1 2006".
>
> greg.fenton
THanks.

Edgard L. Riba

2005-08-25, 11:23 am

What is a "materialized view"?

Best regards,
Edgard

"Richard Biffl" < sybaseforums@removve
thiisphrraseblacklet
tersoftware.com>
escribió en el mensaje news:430ac2ea@forums
-1-dub...
> What have you TechWave attendees learned about SQL Anywhere 10? The press
> release mentioned materialized views, hot failover, and profiling tools.
> It
> also mentioned MobiLink development tools, but I can't tell whether that's
> part of SQL Anywhere 10 or a separate product.
>
> Richard
>
>
>

Richard Biffl

2005-08-25, 1:23 pm

Here's my understanding, and I'd welcome correction by those of you who know
more about this:

A view seems like a table, but it is really just a query that, when you
SELECT from it, gets processed as a subquery. If the view is complex or its
base tables are large, it may add considerable processing time to a query
that uses it.

A *materialized* view maintains an actual table with the view's data. For
example, you might create a view with employee_number, year, and
yearly_earnings, the yearly_earnings field being a SUM of gross pay grouped
by employee_number and year. By materializing the view, the yearly_earnings
field will be readily accessible when needed, without calculating it. The
more complex the aggregation, the more benefit you'll get from a
materialized view when you execute a query against it.

Materialized views can be implemented with different strategies for
refreshing the view as data changes in the base tables. In the example
above, you might only need to refresh the materialized view at the end of
the year if you'll be using it for historical data, but you'd want a more
frequent refresh, or a regular un-materialized view, for accurate totals in
the current year. It'll be interesting to see what ASA 10's implementation
looks like. I'm hoping it'll be simple and automatic, but those with more
demanding applications might want something more complex and flexible.

Richard

"Edgard L. Riba" <elriba at rimith dot com> wrote in message
news:430de479@forums
-1-dub...
> What is a "materialized view"?
>
> Best regards,
> Edgard
>
> "Richard Biffl" < sybaseforums@removve
thiisphrraseblacklet
tersoftware.com>
> escribió en el mensaje news:430ac2ea@forums
-1-dub...
press[color=darkred]

that's[color=darkred
]
>
>

Edgard L. Riba

2005-08-25, 8:23 pm

Wow!

This is an excellent feature!

Best regards,
Edgard

"Richard Biffl" < sybaseforums@removve
thiisphrraseblacklet
tersoftware.com>
escribió en el mensaje news:430e0575@forums
-2-dub...
> Here's my understanding, and I'd welcome correction by those of you who
> know
> more about this:
>
> A view seems like a table, but it is really just a query that, when you
> SELECT from it, gets processed as a subquery. If the view is complex or
> its
> base tables are large, it may add considerable processing time to a query
> that uses it.
>
> A *materialized* view maintains an actual table with the view's data. For
> example, you might create a view with employee_number, year, and
> yearly_earnings, the yearly_earnings field being a SUM of gross pay
> grouped
> by employee_number and year. By materializing the view, the
> yearly_earnings
> field will be readily accessible when needed, without calculating it. The
> more complex the aggregation, the more benefit you'll get from a
> materialized view when you execute a query against it.
>
> Materialized views can be implemented with different strategies for
> refreshing the view as data changes in the base tables. In the example
> above, you might only need to refresh the materialized view at the end of
> the year if you'll be using it for historical data, but you'd want a more
> frequent refresh, or a regular un-materialized view, for accurate totals
> in
> the current year. It'll be interesting to see what ASA 10's implementation
> looks like. I'm hoping it'll be simple and automatic, but those with more
> demanding applications might want something more complex and flexible.
>
> Richard
>
>
> "Edgard L. Riba" <elriba at rimith dot com> wrote in message
> news:430de479@forums
-1-dub...
> press
> that's
>
>

Russell Fleming

2005-08-26, 9:23 am

Oracle's "create snapshot" will allow you see the power of this right now.

"Edgard L. Riba" <elriba at rimith dot com> wrote in message
news:430e14fd@forums
-2-dub...
> Wow!
>
> This is an excellent feature!
>
> Best regards,
> Edgard
>
> "Richard Biffl" < sybaseforums@removve
thiisphrraseblacklet
tersoftware.com>
> escribió en el mensaje news:430e0575@forums
-2-dub...
query[color=darkred]

For[color=darkred]
The[color=darkred]
of[color=darkred]
more[color=darkred]
implementation[color
=darkred]
more[color=darkred]
< sybaseforums@removve
thiisphrraseblacklet
tersoftware.com>[color=darkred]
>
>

Andre Schild

2005-08-29, 3:23 am

Russell Fleming schrieb:
> Oracle's "create snapshot" will allow you see the power of this right now.

Correct.

In materialized views you have a very good read-performance, since the
view data is already present as a "real" table.

The drawbacks are the additional costs at insert/delete/update of the
original tables.

Depending on the database capabilities you have to choose between
updating the materialized view immediatly (like a trigger), but this
can be very time consuming depending the amount of rows to update.

Another way is to delay the update of the view until it's first used,
the engine then updates it on first reference.

Yet another way is to define some time (for example in the night)
when the updates are done. But in this case your materialized views
will hold old data until the night is over.

It will be realy interesting to see how updates are handled.

André

Paul Horan[TeamSybase]

2005-08-29, 9:23 am

"Russell Fleming" <russ.fleming@gmail.com> wrote in message news:430f1af3@forums
-1-dub...
> Oracle's "create snapshot" will allow you see the power of this right now.
>
>

at the expense of having to work with Oracle... No thanks. That tradeoff isn't worth it.

--
Paul Horan[TeamSybase]

Sponsored Links