lookiisland.blogg.se - 90 day plan new job

90 DAY PLAN NEW JOB HOW TO

And for those tables that have no indexes except maybe that unigueidentifier that the consultants put on every table because of replication but didn’t make it a ROWGUID so then a column name rowguid was added as well onto the tables that were replicated (oy!) and what about all those floats, and then when I said something about that decimal (18, 8) (oy, oy, oy). This will give you future data to look at what indexes are actually being used. So, I’ll follow up with a blog for this script as well. I have a trick where I check the startup time where I stored it the night before and only keep last night if the server restarted.

I would setup sp_BlitzIndex to log to table at midnight every night.

90 DAY PLAN NEW JOB HOW TO

I’ll follow up with a blog post with a script on how to do that.

For documentation purposes, I highly recommend using PowerShell to run Glenn Alan Berry’s diagnostic queries in notebooks against every server to get a snapshot of everything.

This is the part where I go through a cleanup anything I find that needs to be configured, set up to run that I want to collect data on, etc. Below I’ll give examples of some of the things I did at some of the various jobs, these won’t be limited to my last four in four years. So where should you begin? There are three aspects I suggest taking a look at one is of course strictly the technical database-related work you were hired for, the second would be documentation processes and finding ways to improve them, and the third is figure out the one thing about your new job you are the weakest at and go out get educated on it. In one company in particular the development team and administrative team didn’t work together and made my job difficult. In a couple of the companies, I went to in the last four years the list of things that needed working on was massive. You’ve had time to access the system with the tools mentioned in the first blog post and have a list of things to fix and may not even know where to begin with that list. The flow of processes and maybe the not flow of processes. Days 31 – 60*īy now you have a sense of how the team works and how teams work with your team.

Currently, I’m not completely through it so I’ve just rolling it forward the half-completed stuff and moving forward with my plan. I didn’t’ get through all that stuff at each company in my first 30 days. Sometimes things take longer after different companies. Also, note as you are making all these improvements keep metrics and documentation to show your manager at the end of this time period.Īlso, if you haven’t made it through everything, I outlined in the first post for the first 30 days don’t panic it is OK. I’ve also done the opposite and became a well-respected employee that people felt was approachable and valued team member. I have gone into companies and just got lost in the shuffle by not being assertive enough and making my presence known and getting into the weeds. I believe this is vital to establishing your career at the company.

In my first post, I reference that by the end of your first 30 days you should have a 90-day plan of things to tackle at your job and how to proceed with the company.