One of my clients has the concept of a Playground on their database platform. The definition of this environment (for them) is as follows:
- Used for prototyping a new application – build it yourself and see if it works!
- Used for a proof of concept of software that would require a database or repository. I keep wondering who has time for this type of fun!
- The platform can be used for NO more than 3 months for one application, and then it must deleted from the Playground or put in production.
What has happened is:
- The business users are building real applications out there using data (based on views) from the production database.
- Most of the applications, in the Playground, have been there more than 30 days.
- None of these projects are ever planned for the production environment. Why — because they work in the Playground.
What the Playground has caused:
- Because the users were given the freedom to build anything they wanted, with no thought of data quality or data integration – the practice continues.
- Since all work is project based, the project just needs more money to fund more people. More people to keep the equipment on the Playground in tip top shape.
I think the Playground needs audited, managed properly, and then monitored on an on-going basis. Maybe the Playground should not be backed up every night – would that push people into production? What about reducing access instead of opening it up to anyone? I am pretty sure if we ‘delete they will come’! I do love a good delete!