Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Job Worries over Automation


Job Worries over Automation

Author
Message
Eric M Russell
Eric M Russell
SSCarpal Tunnel
SSCarpal Tunnel (4.6K reputation)SSCarpal Tunnel (4.6K reputation)SSCarpal Tunnel (4.6K reputation)SSCarpal Tunnel (4.6K reputation)SSCarpal Tunnel (4.6K reputation)SSCarpal Tunnel (4.6K reputation)SSCarpal Tunnel (4.6K reputation)SSCarpal Tunnel (4.6K reputation)

Group: General Forum Members
Points: 4571 Visits: 9495
Even if automation pushes an IT professional out of one job, it will open the door for another job, wether within the same organization or another. I'm sure there are a lot of here who are thankful were not still sorting cards and pecking out COBOL one line at a time anymore. In the interim we've outgrown a handful of jobs and were blessed with new challenges and new rewards with each. At least those of us who innovated did.


"The universe is complicated and for the most part beyond your control, but your life is only as complicated as you choose it to be."
SQLBill
SQLBill
Hall of Fame
Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)

Group: General Forum Members
Points: 3451 Visits: 1015
My first job as a SQL Server DBA was for a company that had U.S. government contracts. We worked in a secure facility, so the main vendor couldn't access anything. We were one of only a few clients where the vendor didn't have full control over the databases and server. So for everyone else, adminstration was 'automatic'. They had a program in their app that controlled the backups and other maintenance work. When an update needed done, it got pushed automatically to the database. Except for us. I did all the admin work and they had to send me any new code, then I tested it and applied it if it passed testing. At first they griped about this, until I reported some issues that they didn't catch. At first they ignored me until other clients where it was automatically pushed and installed began complaining. Then it became an 'unwritten' policy to send me the updates/changes before pushing them out to other clients. I would do my testing and provide them feedback. Once everything looked good, then they pushed it to their other clients. It was nice for them because they got real-world testing before pushing it out automatically. It was nice for me as I knew the code I finally installed in production actually worked and I got the 'pat on the back feeling' that I was able to help the vendor and keep other companies from having issues with the upgrades.

-SQLBill



Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search