Revision as of 19:11, 7 October 2018 edit Djm-leighpark (talk \| contribs) Extended confirmed users, Pending changes reviewers 24,518 edits →Potentially usable references: Added ref ← Previous edit		Revision as of 21:10, 7 October 2018 edit undo Djm-leighpark (talk \| contribs) Extended confirmed users, Pending changes reviewers 24,518 edits m →Potentially usable references: tweaks Next edit →
Line 2: == Potentially usable references == * [https://web.archive.org/web/20080529020704/http://www.computerworld.com/action/article.do?command=viewArticleBasic&taxonomyName=databases&articleId=9087918&taxonomyId=53&intsrc=kc_feat May 2008 Computer weekly about largest databases at the time] 06:36, 4 October 2018 (UTC) Line 12 ⟶ 11: * [https://dev.mysql.com/doc/refman/8.0/en/storage-engines.html mysql 8.0 merge engine for vldb] * [https://blogs.msdn.microsoft.com/sqlcat/2018/01/22/sql-server-vldb-in-azure-dba-tasks-made-simple/ jan 2018:: reviewed sqlserver blog ... vldb kicking in at 3TB to 5TB] * Widlake: [https://mwidlake.wordpress.com/2009/09/18/what-is-a-vldb/ ..a blog but some interesting pointers] * RedBrick1996: [https://web.archive.org/web/19971010114605/http://www.redbrick.com/rbs-g/whitepapers/tenreq_wp.html Redbrick.com - 1996 - referenced by Connolly/Begg ... does not mention VLDB but indicates VLDB problems well below 1TB] == Content to be added to Article ==

Talk:Very large database/Notes: Difference between revisions