The forum will be down for maintenance over the weekend of August 18-20, 2017. The forum will be shut down on the evening (EDT) of Friday, August 18. Downtime is unknown but may be up to two days. The forum will be restarted as soon as maintenance is complete.

This request was made by an attendee at Anil Goel's Techwave 2010 presentation "Improving Performance with SQL Anywhere Materialized Views":

Copy nodes are read-only databases available as part of SQL Anywhere Version 12's "Read-only scale-out" feature.

These databases may be used for reporting purposes, and materialized views are often very useful for reporting. Rather than defining the materialized views on the primary database where they might never be used, it would be great to define them ONLY on the copy nodes where they would be of some use. That way, the existence of "too many, too aggressive" materialized views would not affect performance on the primary database, and may in fact be tolerated on the reporting databases.

At least two people in the audience thought this was a great idea.

asked 10 Aug '10, 15:08

Breck%20Carter's gravatar image

Breck Carter
26.5k433604876
accept rate: 21%

2

makes a load of sense. I'm wondering how one could have a generic system that allowed one to transparently off load read only queries to a read only server if it existed, but would behave OK if it didn't. Our user base varies from installs with 100s users to single user systems and ideally one wants a common approach.

(10 Aug '10, 17:32) Justin Willey 1

This is an interesting idea, and one we have thought of - not only for materialized views, but also (for example) secondary indexes - there is every possibility that the indexes required for read-only query processing on copy nodes may be different from the set of indexes required on the primary, read/write database.

We'll consider this for a future release.

permanent link

answered 11 Aug '10, 02:30

Glenn%20Paulley's gravatar image

Glenn Paulley
10.7k571104
accept rate: 43%

Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:

×107

question asked: 10 Aug '10, 15:08

question was seen: 660 times

last updated: 11 Aug '10, 02:30