 | This is not a Wikipedia article: This is a workpage, a collection of material and work in progress that may or may not be incorporated into Very large database. It should not necessarily be considered factual or authoritative. |
Potentially usable references
- May 2008 Computer weekly about largest databases at the time 06:36, 4 October 2018 (UTC)
- AIOUG-SJH: Oracle ACE - ppt - may be useful in certain ways. Identifies 7 VLDB Challaenges on Slide 11 but doesn't elaborate Djm-leighpark
- MustDoVLDB-WC: An SQL server sort of equivalent for VLDB's; may or may not be bloggy but likely a useful cross check if nothing else
- Ths actually arose from a presentation
- MustDoVLDB-WC: An SQL server sort of equivalent for VLDB's; may or may not be bloggy but likely a useful cross check if nothing else
- Don may have assumed database growth implies more users accessing it ... which may not be always true ... That said bigger Data warehouse more access required
- simple useful vldb and backup ref from Don ... ...
- mysql 8.0 merge engine for vldb
- jan 2018:: reviewed sqlserver blog ... vldb kicking in at 3TB to 5TB
- ..a blog but some interesting pointers
Content to be added to Article
There is some content to be added to the article. Some are waiting simply to link cites in the references above in a suitable manner.
Performance
- Performance issues in VLDBs will also be applicable and solutions will useful for sub-VLDBs, but for VLDB the issues are more pronounced.
Objects
- In a typically VLDB only a small proportion of the objects are likely to contribute to the VLDB. In in content store database these may relate to documents store in or without the database. Sometimes they will relate to transactional tables like a Bank online system where there will be a large number of financial transactions (that can be archived and retained after a suitable period of months). (currently not references covering)