|So today I've experienced what a lot of people are complaining about...
Up to now I've always been a sysadmin on all servers and databases, just because we had small teams where everyone did everything (and I did deployments, mostly).
I now work for a company that has developers and admins and (somewhat) clear roles for both of them.
So I deploy an application (using VSTS, which, apparently, has more rights than me).
And it doesn't work...
Ask an admin if he can check out a log file for me, yes there, no not there, that other folder, yeah, that one.
Then ask if he can change a config for me, yes that config, that value, no, with an A, not an E, yeah, like that.
Then ask if he can check that same log file for me, yes that folder, over there.
Then ask if he can install a certificate for me, yes I really need it, it's from a third party we need to run our business, yes really, on the local computer, no not the user account, yeah, like that.
Then ask if he can, again, check that log file for me.
Then ask if he can run a SQL script for me, that database, no that one, seems the schema is new, just type CREATE SCHEMA, no just do it, you need to type GO after a CREATE SCHEMA, no GO, yeah there, try again...
Log file again.
Things are getting messy, turned out the IIS app pool didn't have sufficient rights for the certificate.
Great, that works... Next application
I'm not complaining that the sysadmin doesn't know how to do his job, but this took an entire afternoon while it should've taken about an hour.
I'm a developer, I've written the software, designed the database, deployed it to our test environment...
Just let me do my job on other environments as well
Computers are my job, I kind of know how they work...