Click here to monitor SSC
SQLServerCentral is supported by Redgate
Log in  ::  Register  ::  Not logged in
Home       Members    Calendar    Who's On

Add to briefcase «««123

Job Worries over Automation Expand / Collapse
Posted Thursday, October 17, 2013 10:17 AM

SSCarpal Tunnel

SSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal Tunnel

Group: General Forum Members
Last Login: Today @ 7:21 AM
Points: 4,130, Visits: 9,229
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."
Post #1505804
Posted Thursday, October 17, 2013 1:54 PM
Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Tuesday, December 6, 2016 2:42 PM
Points: 3,413, Visits: 998
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.


Post #1505892
« Prev Topic | Next Topic »

Add to briefcase «««123

Permissions Expand / Collapse