Many applications of SQL Anywhere involve static data sets that are then used in conjunction with the "dynamic" part of the database - examples are things like product lists and increasingly with the support of spacial data - large geographic data sets.

It would be very useful in these circumstances to be able to ship users a replacement dbspace containing the tables, indexes etc required; rather than having to truncate / load tables etc as at the moment (or use a separate remote database).

Clearly there would have to be some restrictions especially as regards referential integrity between objects in different dbspaces - but these could be fairly strict - (eg if you replace a dbspace all RI pointing to it is dropped and you have to re-create it - or you can't replace the dbspace until all RI pointing to it from outside has been dropped).

asked 08 Dec '14, 09:09

Justin%20Willey's gravatar image

Justin Willey
6.5k105135203
accept rate: 21%

2

Would that suggestion include a "BACKUP DATABASE without dbspace ..." feature?

(08 Dec '14, 09:47) Volker Barth
Be the first one to answer this question!
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:

×106
×17

question asked: 08 Dec '14, 09:09

question was seen: 979 times

last updated: 08 Dec '14, 09:47