Policy for creating new databases
Posted on 2003-03-04
Our company is growing large and frequently we have users who are not in IT developing databases only to find out later that they should have used something else or they have duplicated something that already existed. We haved decided we want to lock everything down so that only IT can create a new db and we will have policies for creating new db's. I'm not asking how to lock down the server but rather if any of you monkeys have policies of your own that I can steal and tweak for my own use and become the company hero... something to get me started. So for example the policy will say if you want a database then 1) what do you want it to do? 2) who is it for? 3) does it exist somewhere else etc etc etc.
Anybody doing something like this?