Hi Stephen. What exactly are you placing under source control? SQL scripts? DB dumps? We definitely keep any DB related code under source control.
How can we enforce it when users can just modify the database directly?
I would responde, "We have bigger issues than source control policies if end users are modifying the database directly." :-)
It would be too much trouble to get everyone on-board.
That is where a strong CTO comes in handy. I don't believe tech organizations should be democracies. A good CTO solicits opinions and then sets non-optional policies based on his or her best judgment.
My goal is to put all stored procedures, UDFs and scripts for creating tables and views under source control.
Fortunately I've gotten their attention and we'll be having a conference call regarding this on Monday (tomorrow).
As for the CTO thing, well, we don't have one. My employer operates more as a staffing agency than a development shop. I've been on assignment at our largest (and sometimes only) client, Schlumberger, for almost 7 years now. They do have a CTO, but from what I can tell, the IT landscape would be best described as a semi-connected archipelago.