Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

MOUG17: Three Types of Table Compression

238 views

Published on

Midwest Oracle Users Group Training Day 2017 Presentation by Tim Gorman, Oracle Ace Director.

Published in: Technology
  • Be the first to comment

MOUG17: Three Types of Table Compression

  1. 1. © 2017 Delphix. All Rights Reserved Tim Gorman | Technical Manager | Delphix Optimizing Testing Using Data Virtualization
  2. 2. © 2017 Delphix. All Rights Reserved As a developer, my job is to create new functionality and fix bugs As a tester, my job is to make sure software works as designed As a DBA, my job is to create databases, protect them, and keep applications running optimally This presentation is about all these things, but mostly it is about change
  3. 3. © 2017 Delphix. All Rights Reserved Are you too busy to change? Inertia 3
  4. 4. © 2017 Delphix. All Rights Reserved Virtualization is the conversion of the data center from hardware into automatable software Server virtualization is the norm for systems administration today But server virtualization only virtualizes CPU, RAM, and network (a.k.a. compute) It does not virtualize storage or databases
  5. 5. © 2017 Delphix. All Rights Reserved Data virtualization is the rest of the virtualization solution If you aren’t absolutely amazed by the benefits of server virtualization… …then that is because data virtualization is missing You only have the partial solution
  6. 6. © 2017 Delphix. All Rights Reserved Stop for a moment and consider… What are the distortions that have arisen in SDLC prior to the advent of virtualization? Specifically, how many non-production environments can your organization support for SDLC? Is that enough to carry on SDLC in bare survival mode? New functionality or fixes into production every few months? Or years?
  7. 7. © 2017 Delphix. All Rights Reserved New functionality and fixes need to be delivered to users in production within hours or days, at most weeks, not months or years Is such a tempo possible supporting PROD with: • a single instance of DEV • a single instance of SIT • a single instance of UAT The litmus test: Can your IT infrastructure support two-week sprints with environments newly refreshed from production?
  8. 8. © 2017 Delphix. All Rights Reserved Moore’s Law predicts a doubling of processing power every year (18 months, 2 years, etc). And this has proven true… …but we cannot rely on faster and faster systems to power us to meet new requirements To achieve continuous delivery, we need infrastructure to become smarter, more efficient, not just more powerful So, let’s start with some lessons in efficiency…
  9. 9. © 2017 Delphix. All Rights Reserved The Goal: Theory of Constraints • Long build cycles are wasteful • QA/Testing is the first victim • Improvement not made at the constraint is an illusion 9
  10. 10. © 2017 Delphix. All Rights Reserved The Goal: Theory of Constraints • Long build cycles are wasteful • QA/Testing is the first victim • Improvement not made at the constraint is an illusion 10
  11. 11. © 2017 Delphix. All Rights Reserved The Goal: Theory of Constraints • Long build cycles are wasteful • QA/Testing is the first victim • Improvement not made at the constraint is an illusion 11
  12. 12. © 2017 Delphix. All Rights Reserved Factory floor 12
  13. 13. © 2017 Delphix. All Rights Reserved Factory floor constraint 13
  14. 14. © 2017 Delphix. All Rights Reserved Tune before constraint constraint Tuning here Stock piling 14
  15. 15. © 2017 Delphix. All Rights Reserved Tune after constraint constraint Tuning here Starvation 15
  16. 16. © 2017 Delphix. All Rights Reserved Factory floor: optimizing at the constraint constraint Goal: find constraint and optimize it 16
  17. 17. © 2017 Delphix. All Rights Reserved Does the Theory of Constraints work for IT ? • Goals Clarify • Metrics Define • Constraints Identify • Priorities Set • Iterations Fast • CI • Cloud • Agile • Kanban • Kata “IT is the factory floor of this century” 17
  18. 18. © 2017 Delphix. All Rights Reserved The Phoenix Project: “The Goal” applied to IT “IT is the factory floor of this century” What is the constraint in IT ? 18
  19. 19. © 2017 Delphix. All Rights Reserved The Phoenix Project: top 5 constraints in IT? 1. QA setup 2. Dev/Build setup 3. Code Architecture 4. Development 5. Product management - Gene Kim, author of “The Phoenix Project” “One of the most powerful things that organizations can do is to enable development and testing to get environment they need when they need it“ 19
  20. 20. © 2017 Delphix. All Rights Reserved Data is the constraint 60% Projects Over Schedule 85% delayed waiting for data Data is the Constraint CIO Magazine Survey: …only getting worse… Gartner: Data Doomsday, by 2017 1/3rd IT in crisis 20
  21. 21. © 2017 Delphix. All Rights Reserved • Data Constraint • Attempted solutions • Solution • Use Cases In this presentation :
  22. 22. © 2017 Delphix. All Rights Reserved 22 • PROD is what we care most about… The problem PROD
  23. 23. © 2017 Delphix. All Rights Reserved 23 • PROD is what we care most about… – But behind every PROD… • There is QATEST… The problem PROD QATEST
  24. 24. © 2017 Delphix. All Rights Reserved 24 • PROD is what we care most about… – But behind every PROD… • There is QATEST, DEV… The problem PROD QATEST UAT
  25. 25. © 2017 Delphix. All Rights Reserved 25 • PROD is what we care most about… – But behind every PROD… • There is QATEST, DEV… • …and other project-specific environments to support The problem PROD QATEST UAT
  26. 26. © 2017 Delphix. All Rights Reserved 26 • Also, as PROD grows… The problem PROD PROD
  27. 27. © 2017 Delphix. All Rights Reserved 27 UATQATEST • Also, as PROD grows… – Then so do the supporting non-PROD environments… The problem PROD
  28. 28. © 2017 Delphix. All Rights Reserved 28 The problem CEO COO CFO CMO CSO CIO • And so inevitably the situation shifts from this…
  29. 29. © 2017 Delphix. All Rights Reserved 29 The problem CEO COO CFO CMO CSO CIO Storage Administrator • To this… * Inspired by Connor McDonald (http://connormcdonald.wordpress.com/)
  30. 30. © 2017 Delphix. All Rights Reserved IT generally unaware of the problem 30
  31. 31. © 2017 Delphix. All Rights Reserved Companies unaware of the problem TesterBoss, Storage Admin, DBA 31
  32. 32. © 2017 Delphix. All Rights Reserved Life in IT without adequate QA/Test… silos 32
  33. 33. © 2017 Delphix. All Rights Reserved • Data constraint • Attempted solutions • Solution • Use Cases In this presentation:
  34. 34. © 2017 Delphix. All Rights Reserved 34 • Some try to mitigate the problem by copying subsets of PROD… • …but it is difficult and time-consuming and expensive to create referentially-correct subsets of databases. Leads to buggy code… Attempting to solve the problem… PROD QATEST DEV UAT
  35. 35. © 2017 Delphix. All Rights Reserved 35 • Some try to mitigate the problem by copying subsets of PROD… • …but it is difficult and time-consuming and expensive to create referentially-correct subsets of databases. Leads to buggy code… Attempting to solve the problem… PROD QATEST DEV UAT
  36. 36. © 2017 Delphix. All Rights Reserved 36 • Some try to mitigate the problem by copying subsets of PROD… • …but it is difficult and time-consuming and expensive to create referentially-correct subsets of databases. Leads to buggy code… Attempting to solve the problem… PROD QATEST DEV UAT
  37. 37. © 2017 Delphix. All Rights Reserved 37 • Cloning production to non-product inevitably performed infrequently… …meaning that schemas and data are older, dirtier due to previous testing, and too small to accurately represent reality Attempting to solve the problem… PROD QATEST DEV UAT
  38. 38. © 2017 Delphix. All Rights Reserved 38 • Cloning production to non-product inevitably performed infrequently… • …meaning that schemas and data are older, dirtier due to previous testing, and too small to accurately represent reality Attempting to solve the problem… PROD QATEST DEV UAT
  39. 39. © 2017 Delphix. All Rights Reserved 39 PROD • Creating snapshots with mirror splits… – Mirror the volume one extra copy Attempting to solve the problem… PROD PROD
  40. 40. © 2017 Delphix. All Rights Reserved 40 PROD • Creating snapshots with mirror splits… – Mirror the volume one extra copy – Then cease writes to that extra copy at a specific time and make it separately addressable as a separate volume Attempting to solve the problem… PROD PROD
  41. 41. © 2017 Delphix. All Rights Reserved 41 PROD • Creating snapshots with mirror splits… – Mirror the volume one extra copy – Then cease writes to that extra copy at a specific time and make it separately addressable as a separate volume – To create another snapshot, “re-silver” the volume into the mirror set Attempting to solve the problem… PROD PROD
  42. 42. © 2017 Delphix. All Rights Reserved 42 PROD • Creating snapshots with mirror splits… – Mirror the volume one extra copy – Then cease writes to that extra copy at a specific time and make it separately addressable as a separate volume – To create another snapshot, “re-silver” the volume into the mirror set – And it’s ready to split again Attempting to solve the problem… PROD PROD
  43. 43. © 2017 Delphix. All Rights Reserved 43 PROD • Creating snapshots with mirror splits… – Mirror the volume one extra copy – Then cease writes to that extra copy at a specific time and make it separately addressable as a separate volume – To create another snapshot, “re-silver” the volume into the mirror set – And it’s ready to split again – While we’ve solved the problem of quickly creating new copies Attempting to solve the problem… PROD PROD
  44. 44. © 2017 Delphix. All Rights Reserved 44 PROD • Creating snapshots with mirror splits… – Mirror the volume one extra copy – Then cease writes to that extra copy at a specific time and make it separately addressable as a separate volume – To create another snapshot, “re-silver” the volume into the mirror set – And it’s ready to split again – While we’ve solved the problem of quickly creating new copies • But we haven’t solved the problem of using a full image Attempting to solve the problem… PROD PROD
  45. 45. © 2017 Delphix. All Rights Reserved 45 PROD • Creating snapshots with mirror splits… – Mirror the volume one extra copy – Then cease writes to that extra copy at a specific time and make it separately addressable as a separate volume – To create another snapshot, “re-silver” the volume into the mirror set – And it’s ready to split again – While we’ve solved the problem of quickly creating new copies • But we haven’t solved the problem of using a full image • And re-silvering is not a fast operation, so we need time to “reload” Attempting to solve the problem… PROD PROD
  46. 46. © 2017 Delphix. All Rights Reserved 46 Attempting to solve the problem… CEO COO CFO CMO CSO CIO Storage Administrator We’re still at square one… …and it gets even worse Because now we have to predict the size of everything with perfect accuracy and then pre-allocate for copies as well as volumes
  47. 47. © 2017 Delphix. All Rights Reserved 47 Attempting to solve the problem… CEO COO CFO CMO CSO CIO Storage Administrator We’re still at square one… …and it gets even worse Because now we have to predict the size of everything with perfect accuracy and then pre-allocate for copies as well as volumes
  48. 48. © 2017 Delphix. All Rights Reserved 48 Attempting to solve the problem… CEO COO CFO CMO CSO CIO Storage Administrator We’re still at square one… …and it gets even worse Because now we have to predict the size of everything with perfect accuracy and then pre-allocate for copies as well as volumes
  49. 49. © 2017 Delphix. All Rights Reserved 49 Attempting to solve the problem… CEO COO CFO CMO CSO CIO Storage Administrator We’re still at square one… …and it gets even worse Because now we have to predict the size of everything with perfect accuracy and then pre-allocate for copies as well as volumes
  50. 50. © 2017 Delphix. All Rights Reserved 50 Attempting to solve the problem… CEO COO CFO CMO CSO CIO Storage Administrator We’re still at square one… …and it gets even worse Because now we have to predict the size of everything with perfect accuracy and then pre-allocate for copies as well as volumes
  51. 51. © 2017 Delphix. All Rights Reserved 51 So, in a perfect world what we’d like to see is something like this… Attempting to solve the problem… PROD QAT for Tom QAT for Dick UAT for Sally DEV for Harry QAT for Becky
  52. 52. © 2017 Delphix. All Rights Reserved 52 Attempting to solve the problem… PROD DEV/QA T/UAT Tom Dick Sally Harry Becky …but, in the real world we see this…
  53. 53. © 2017 Delphix. All Rights Reserved 53 • It’s not easy for developers and testers to share environments simultaneously – Changes made by each user conflict with one another • So it becomes necessary to serialize access to the limited number of environments – Each user queues at the resource, so their project takes more time elapsed – Each user destructively changes the resource • And now we need a way to reset or clean up the environment between each use – Reset or clean up takes time, which causes further delays between uses Attempting to solve the problem…
  54. 54. © 2017 Delphix. All Rights Reserved 54 • It’s not easy for developers and testers to share environments simultaneously – Changes made by each user conflict with one another • So it becomes necessary to serialize access to the limited number of environments – Each user queues at the resource, so their project takes more time elapsed – Each user destructively changes the resource • And now we need a way to reset or clean up the environment between each use – Reset or clean up takes time, which causes further delays between uses Attempting to solve the problem…
  55. 55. © 2017 Delphix. All Rights Reserved 55 • It’s not easy for developers and testers to share environments simultaneously – Changes made by each user conflict with one another • So it becomes necessary to serialize access to the limited number of environments – Each user queues at the resource, so their project takes more time elapsed – Each user destructively changes the resource • And now we need a way to reset or clean up the environment between each use – Reset or clean up takes time, which causes further delays between uses Attempting to solve the problem…
  56. 56. © 2017 Delphix. All Rights Reserved 56 • It’s not easy for developers and testers to share environments simultaneously – Changes made by each user conflict with one another • So it becomes necessary to serialize access to the limited number of environments – Each user queues at the resource, so their project takes more time elapsed – Each user destructively changes the resource • And now we need a way to reset or clean up the environment between each use – Reset or clean up takes time, which causes further delays between uses Attempting to solve the problem…
  57. 57. © 2017 Delphix. All Rights Reserved 57 • It’s not easy for developers and testers to share environments simultaneously – Changes made by each user conflict with one another • So it becomes necessary to serialize access to the limited number of environments – Each user queues at the resource, so their project takes more time elapsed – Each user destructively changes the resource • And now we need a way to reset or clean up the environment between each use – Reset or clean up takes time, which causes further delays between uses Attempting to solve the problem…
  58. 58. © 2017 Delphix. All Rights Reserved 58 • It’s not easy for developers and testers to share environments simultaneously – Changes made by each user conflict with one another • So it becomes necessary to serialize access to the limited number of environments – Each user queues at the resource, so their project takes more time elapsed – Each user destructively changes the resource • And now we need a way to reset or clean up the environment between each use – Reset or clean up takes time, which causes further delays between uses Attempting to solve the problem…
  59. 59. © 2017 Delphix. All Rights Reserved 59 • It’s not easy for developers and testers to share environments simultaneously – Changes made by each user conflict with one another • So it becomes necessary to serialize access to the limited number of environments – Each user queues at the resource, so their project takes more time elapsed – Each user destructively changes the resource • And now we need a way to reset or clean up the environment between each use – Reset or clean up takes time, which causes further delays between uses Attempting to solve the problem…
  60. 60. © 2017 Delphix. All Rights Reserved 60 • It’s not easy for developers and testers to share environments simultaneously – Changes made by each user conflict with one another • So it becomes necessary to serialize access to the limited number of environments – Each user queues at the resource, so their project takes more time elapsed – Each user destructively changes the resource • And now we need a way to reset or clean up the environment between each use – Reset or clean up takes time, which causes further delays between uses Attempting to solve the problem…
  61. 61. © 2017 Delphix. All Rights Reserved • Data constraint • Attempted solutions • Solution • Use Cases In this presentation:
  62. 62. © 2017 Delphix. All Rights Reserved 62 • The biggest problem with cloning environments and databases is all the duplication Most (if not all) of the blocks comprising the database or file-system exactly the same What if we store only one copy of each version of a block? Copy-on-write (COW) Never modify a block, but insert a new version instead Then let the storage figure out what we’re supposed to be seeing? The storage maintains the relationships and versions on retrieval And then make it portable so that ANY platform (Unix/Linux, Windows) can use it? NFS (network file system) A solution…
  63. 63. © 2017 Delphix. All Rights Reserved 63 • The biggest problem with cloning environments and databases is all the duplication – Most (if not all) of the blocks comprising the database or file-system exactly the same What if we store only one copy of each version of a block? Copy-on-write (COW) Never modify a block, but insert a new version instead Then let the storage figure out what we’re supposed to be seeing? The storage maintains the relationships and versions on retrieval And then make it portable so that ANY platform (Unix/Linux, Windows) can use it? NFS (network file system) A solution…
  64. 64. © 2017 Delphix. All Rights Reserved 64 • The biggest problem with cloning environments and databases is all the duplication – Most (if not all) of the blocks comprising the database or file-system exactly the same • What if we store only one copy of each version of a block? Copy-on-write (COW) Never modify a block, but insert a new version instead Then let the storage figure out what we’re supposed to be seeing? The storage maintains the relationships and versions on retrieval And then make it portable so that ANY platform (Unix/Linux, Windows) can use it? NFS (network file system) A solution…
  65. 65. © 2017 Delphix. All Rights Reserved 65 • The biggest problem with cloning environments and databases is all the duplication – Most (if not all) of the blocks comprising the database or file-system exactly the same • What if we store only one copy of each version of a block? – Copy-on-write (COW) • Never modify a block, but insert a new version instead Then let the storage figure out what we’re supposed to be seeing? The storage maintains the relationships and versions on retrieval And then make it portable so that ANY platform (Unix/Linux, Windows) can use it? NFS (network file system) A solution…
  66. 66. © 2017 Delphix. All Rights Reserved 66 • The biggest problem with cloning environments and databases is all the duplication – Most (if not all) of the blocks comprising the database or file-system exactly the same • What if we store only one copy of each version of a block? – Copy-on-write (COW) • Never modify a block, but insert a new version instead • Then let the storage figure out what we’re supposed to be seeing? The storage maintains the relationships and versions on retrieval And then make it portable so that ANY platform (Unix/Linux, Windows) can use it? NFS (network file system) A solution…
  67. 67. © 2017 Delphix. All Rights Reserved 67 • The biggest problem with cloning environments and databases is all the duplication – Most (if not all) of the blocks comprising the database or file-system exactly the same • What if we store only one copy of each version of a block? – Copy-on-write (COW) • Never modify a block, but insert a new version instead • Then let the storage figure out what we’re supposed to be seeing? – The storage maintains the relationships and versions on retrieval And then make it portable so that ANY platform (Unix/Linux, Windows) can use it? NFS (network file system) A solution…
  68. 68. © 2017 Delphix. All Rights Reserved 68 • The biggest problem with cloning environments and databases is all the duplication – Most (if not all) of the blocks comprising the database or file-system exactly the same • What if we store only one copy of each version of a block? – Copy-on-write (COW) • Never modify a block, but insert a new version instead • Then let the storage figure out what we’re supposed to be seeing? – The storage maintains the relationships and versions on retrieval • And then make it portable so that ANY platform (Unix/Linux, Windows) can use it? NFS (network file system) A solution…
  69. 69. © 2017 Delphix. All Rights Reserved 69 • The biggest problem with cloning environments and databases is all the duplication – Most (if not all) of the blocks comprising the database or file-system exactly the same • What if we store only one copy of each version of a block? – Copy-on-write (COW) • Never modify a block, but insert a new version instead • Then let the storage figure out what we’re supposed to be seeing? – The storage maintains the relationships and versions on retrieval • And then make it portable so that ANY platform (Unix/Linux, Windows) can use it? – NFS (network file system – Unix/Linux), iSCSI (Windows) A solution…
  70. 70. © 2017 Delphix. All Rights Reserved 70 • Cloning the old way… A solution… PROD DEV
  71. 71. © 2017 Delphix. All Rights Reserved 71 • Cloning the smart way… A solution… PROD DEV PROD Copy
  72. 72. © 2017 Delphix. All Rights Reserved 72 PROD Copy • Cloning the smart way… – As changes are made to the clone, only those changed blocks are stored… A solution… DEVPROD
  73. 73. © 2017 Delphix. All Rights Reserved 73 • Cloning the smart way… – As changes are made to the clone, only those changed blocks are stored… • Takes less storage, faster to copy • The cost of the clone has gone way down in terms of storage and time A solution… DEV PROD CopyPROD
  74. 74. © 2017 Delphix. All Rights Reserved 74 • Overall architecture • Internal file-system How does it work?
  75. 75. © 2017 Delphix. All Rights Reserved 75 Overall architecture VM/AppliancePROD
  76. 76. © 2017 Delphix. All Rights Reserved 76 Overall architecture VM/AppliancePROD Command and control (SSH/JDBC)
  77. 77. © 2017 Delphix. All Rights Reserved 77 Overall architecture VM/AppliancePROD Command and control (SSH/JDBC) Initial FULL and forever INCREMENTAL backups (RMAN)
  78. 78. © 2017 Delphix. All Rights Reserved 78 Overall architecture VM/Appliance VDB 1Command and control (SSH/JDBC)
  79. 79. © 2017 Delphix. All Rights Reserved 79 Overall architecture VM/Appliance VDB 1 NFS Command and control (SSH/JDBC)
  80. 80. © 2017 Delphix. All Rights Reserved 80 Overall architecture VM/Appliance NFS Command and control (SSH/JDBC) VDB 4 VDB 3 VDB 2 VDB 1
  81. 81. © 2017 Delphix. All Rights Reserved 81 Overall architecture VM/Appliance NFS Command and control (SSH/JDBC) VDB 4 VDB 3 VDB 2 VDB 1 PROD Command and control (SSH/JDBC) Initial FULL and forever INCREMENTAL backups (RMAN)
  82. 82. © 2017 Delphix. All Rights Reserved Snapshot 1 – initial load a b c d e f g h i We start with a full backup. Includes transaction logs needed for recovery. Jonathan Lewis © 2015 Sn #1 82
  83. 83. © 2017 Delphix. All Rights Reserved Snapshot 2 – incoming new changes b' c' a b c d e f g h i After initial link/load, Delphix is incremental forever Jonathan Lewis © 2015 83 Sn #1
  84. 84. © 2017 Delphix. All Rights Reserved Apply Snapshot 2 a b c d e f g h ib' c' The Delphix appliance unpacks the backup and "overwrites" the initial backup with the changed blocks. DxFS makes new copies of the changed blocks, never updates a block 84Jonathan Lewis © 2015 Sn #1 Sn #2
  85. 85. © 2017 Delphix. All Rights Reserved Snapshot 3 – more incoming changes a b c d e f g h ib' c' 85Jonathan Lewis © 2015 i' Sn #1 Sn #2
  86. 86. © 2017 Delphix. All Rights Reserved Apply Snapshot 3 a b c d e f g h ib' c' 86Jonathan Lewis © 2015 i' Sn #1 Sn #2 Sn #3
  87. 87. © 2017 Delphix. All Rights Reserved Retention policies – dropping snapshots a b c d e f g h ib' c' 87Jonathan Lewis © 2015 i' Sn #1 Sn #2 Sn #3
  88. 88. © 2017 Delphix. All Rights Reserved Retention policies – dropping snapshots a d e f g h ib' c' 88Jonathan Lewis © 2015 i' Sn #2 Sn #3
  89. 89. © 2017 Delphix. All Rights Reserved Creating a VDB a d e f g h ib' c' 89Jonathan Lewis © 2015 i' Sn #2 Sn #3VDB Sn #1
  90. 90. © 2017 Delphix. All Rights Reserved Creating a VDB a d e f g h ib' c' 90Jonathan Lewis © 2015 i' Sn #2 Sn #3VDB Sn #1
  91. 91. © 2017 Delphix. All Rights Reserved Changes to a VDB a d e f g h ib' c' 91Jonathan Lewis © 2015 i' Sn #2 Sn #3 a‘' VDB Sn #1
  92. 92. © 2017 Delphix. All Rights Reserved Changes to a VDB a d e f g h ib' c' 92Jonathan Lewis © 2015 i' Sn #2 Sn #3 a‘' VDB Sn #2 VDB Sn #1
  93. 93. © 2017 Delphix. All Rights Reserved Changes to a VDB a d e f g h ib' c' 93Jonathan Lewis © 2015 i' Sn #2 Sn #3 a‘' VDB Sn #2 VDB Sn #1
  94. 94. © 2017 Delphix. All Rights Reserved Changing reality 94
  95. 95. © 2017 Delphix. All Rights Reserved Changing reality 95
  96. 96. © 2017 Delphix. All Rights Reserved Changing reality 96
  97. 97. © 2017 Delphix. All Rights Reserved Database Virtualization 97
  98. 98. © 2017 Delphix. All Rights Reserved • Data constraint • Attempted solutions • Solution • Use cases In this presentation:
  99. 99. © 2017 Delphix. All Rights Reserved Working with Virtual Data • Unlimited • Full size • Self Service • Secure • Cloud onramp Developing Testing Prod Support
  100. 100. © 2017 Delphix. All Rights Reserved Working with Virtual Data: Unlimited GIF by Steve Karam 100
  101. 101. © 2017 Delphix. All Rights Reserved Working with Virtual Data: Full size 101
  102. 102. © 2017 Delphix. All Rights Reserved Working with Virtual Data: Self Service 102 Tester
  103. 103. © 2017 Delphix. All Rights Reserved Working with Virtual Data: Self Service 103
  104. 104. © 2017 Delphix. All Rights Reserved Working with Virtual Data: Secure 104 • Encryption is technology that allows only authorized uses to view data • Masking is technology that changes the data irreversibly while maintaining relational integrity and data distribution patterns – It is not simply scrambling data – It is an art and a science in its own right
  105. 105. © 2017 Delphix. All Rights Reserved Working with Virtual Data: cloud onramp 105 The cloud is largely a no-fly zone for proprietary UNIX. Migrating from UNIX to Linux (U2L) is often the first step of a cloud migration. Data virtualization makes U2L easier for testing and validation.
  106. 106. © 2017 Delphix. All Rights Reserved Testing with Virtual Data • Fast, parallel • Rewind • A/B testing • Sharing
  107. 107. © 2017 Delphix. All Rights Reserved Testing with Virtual Data: Rewind Instance QA Prod Production Time Flow 107
  108. 108. © 2017 Delphix. All Rights Reserved Testing with Virtual Data: A/B testing Instance Instance Instance Index 1 Index 2 Production Time Flow 108
  109. 109. © 2017 Delphix. All Rights Reserved Testing with Virtual Data: sharing Instance Jane’s VDB timeflow 109 Dialogue between QA tester (Jane) and developer (Mary)… Jane: Mary, I’ve found a data problem in version 3.2.2a. Mary: Can you bookmark that and share it? Jane: It is named “Jane 3.2.2a 3pm”, look for dups in tables ABC and XYZ. Mary: Hmm, I restored your bookmark and I see the problem. Thanks! Instance Mary’s branch Jane 3.2.2a 3pm
  110. 110. © 2017 Delphix. All Rights Reserved • Problem: Data is the constraint • Solution: Virtualize the data • Results • 80/20 rule reversed for testing • From 80% wait/20% work to 20% wait/80% work • Higher quality, better testing results • Virtualization => Automation Summary
  111. 111. © 2017 Delphix. All Rights Reserved 111 “The Goal: A Process Of Ongoing Improvement” in 1984 by Eliyahu Goldratt “The Phoenix Project: A Novel About IT, DevOps, And Helping Your Business Win” in 2012 by Gene Kim, Kevin Behr, George Spafford Questions? tim.gorman@delphix.com http://community.Delphix.com +1 (303) 885-4526Thank you for your attention! Tim.Gorman@delphix.com +1 (303) 885-4526 @TimothyJGorman

×