We're looking to re-deploy a fresh setup of SQL 2012 (latest builds of course) in our environment, since we currently have 2012 RTM (19 versions behind), and it's really all messed up.
The easiest way since we're not dependent on SCCM for anything currently, in my opinion, would be to start over with an internal team from scratch. I've deployed it in previous environments too so I'm familiar with the install/config process.
What I'm looking to find out, however, is if we really need a "SQL Database guy" who needs to run maintenance or anything on it.
He's a DBA and is insisting that for our SCCM, we should deploy to a full SQL database that he has access to.
Since this is a small organization of 500 computers, I'm wondering if that is really necessary, and if we'd be best off just using SQL Express locally and make sure nobody even thinks about touching or messing with the database.
I'm worried if someone has access to the database for "maintenance" (whatever that entails-- I don't know) then we could have more margin for error and make backups/restores more difficult.