August 31, 2010 at 8:58 pm
Hello Guys,
I am starting a new job as a DBA next week.
Since i have grown and lived with my current company's database, i do not have any problems working with DB.
But i am worried about new position.
What are the things i need to be careful or what are the things i need to learn or know on my first week, i am not necessarily talking about technology, but about new enviroment, new DB, new people 🙂 etc.
What you have done on your first day, second day, third day .... 10th day at your new job?
I appreciate your suggestions. Many of you might have moved to the new company as a DBA many times,so you can talk from your experiece.
This is the first time i am leaving my company and joining new company.
August 31, 2010 at 10:58 pm
Day 1 - Verify that all databases are backed up. If not, back them up.
September 1, 2010 at 1:00 am
Verify the consistency of your databases as well.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
September 1, 2010 at 1:27 am
1 Whats where - how many DB's and associated apps
2 Whats backed up
3 New maintainence plans to backup and alerts to you for drive space sizes etc
4 As above
5 As Above
6 Service pack levels and recommendations to your new employers who will think you are ace 🙂
7 Get under the bonnet and check AWE settings and other configurable settings which you can recomend to change
8 Test revovery from newely greated maintainace plans
9 Document everything you have done in the past few days
10 Sit back and have a cuppa
September 1, 2010 at 2:50 am
If you database is large or having frequently changing data then better to have a Scheduled Transaction Log Backup/
This will help during recovery secenorio.
September 1, 2010 at 3:06 am
That's got nothing to do with the original question about what to do on your 1st day etc......if your db Is large do a tl backup....duhhhh
September 1, 2010 at 8:33 am
@homebrew and cirquedeSQL are correct
Other basic things u can check are
*Deleting the olderr backup files if the disk space falls below 40%(checking all servers disk space too)
*Checking if log shipping/database mirroring is set up and working(u shld hav gud restoration plan)
*Check for any jobs which might be failing for last few days
Regards,
Sushant
Regards
Sushant Kumar
MCTS,MCP
September 1, 2010 at 8:51 am
i am not necessarily talking about technology, but about new enviroment, new DB, new people 🙂 etc.
What you have done on your first day, second day, third day .... 10th day at your new job?
I appreciate your suggestions. Many of you might have moved to the new company as a DBA many times,so you can talk from your experiece.
This is the first time i am leaving my company and joining new company.
If you're used to working with DB's then telling you things like backup strategies should be like teaching Grandma to suck eggs. As a contractor I move around quite a bit, and first thing (once you've found the loos and the best place for a sandwich), is to familiarise yourself with the environment, then introduce yourself to the users. Make sure you get to know the people who use your databases (within reason, you don't need to introduce yourself to everyone in the whole place). If there are any other DBAs there, get to know them.
September 1, 2010 at 10:05 am
It is very useful to have an inventory of your database servers including Express version installed on desktops.
You should be acquainted with hardware as well as OS settings and SQL settings in each instance and server.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
September 1, 2010 at 11:10 am
After I verify everything is working as it should (Backups being taken regularly, replication/log shipping/mirroring working OK, no outstanding issues/problems), I set up a centralized reporting database and feed data from all servers into that. In one database, I keep CPU usage, Page Life Expectancy, BC Hit Ratio, # of Blocks, Failed Jobs, Long Running Jobs, Replication Latency, and servers with low disk space. When everything is consolidated, you can set up a clean front-end to view it all, and then you have at-a-glance status of all important metrics on every server.
September 2, 2010 at 6:53 am
Derrick Smith (9/1/2010)
After I verify everything is working as it should (Backups being taken regularly, replication/log shipping/mirroring working OK, no outstanding issues/problems), I set up a centralized reporting database and feed data from all servers into that. In one database, I keep CPU usage, Page Life Expectancy, BC Hit Ratio, # of Blocks, Failed Jobs, Long Running Jobs, Replication Latency, and servers with low disk space. When everything is consolidated, you can set up a clean front-end to view it all, and then you have at-a-glance status of all important metrics on every server.
What do you use to get all the information into your reporting database?
September 2, 2010 at 7:22 am
LightVader (9/2/2010)
Derrick Smith (9/1/2010)
After I verify everything is working as it should (Backups being taken regularly, replication/log shipping/mirroring working OK, no outstanding issues/problems), I set up a centralized reporting database and feed data from all servers into that. In one database, I keep CPU usage, Page Life Expectancy, BC Hit Ratio, # of Blocks, Failed Jobs, Long Running Jobs, Replication Latency, and servers with low disk space. When everything is consolidated, you can set up a clean front-end to view it all, and then you have at-a-glance status of all important metrics on every server.What do you use to get all the information into your reporting database?
There are many useful custom ways to do it. For instance, check out the series of "Server Overview" articles[/url].
Wayne
Microsoft Certified Master: SQL Server 2008
Author - SQL Server T-SQL Recipes
September 2, 2010 at 7:30 am
Andeavour (9/1/2010)
If you're used to working with DB's then telling you things like backup strategies should be like teaching Grandma to suck eggs.
Dude, what???
---------------------------------------------------------
How best to post your question[/url]
How to post performance problems[/url]
Tally Table:What it is and how it replaces a loop[/url]
"stewsterl 80804 (10/16/2009)I guess when you stop and try to understand the solution provided you not only learn, but save yourself some headaches when you need to make any slight changes."
September 2, 2010 at 9:22 am
Don't tell me you've never heard the phrase?
In the UK (maybe only in the North, I'm not sure) we have a saying when someone is telling you something you already know (especially in a slightly patronising way), that you're "teaching your grandmother to suck eggs".
I've no idea of the origin, and I guess it's a particularly English phrase...
September 2, 2010 at 9:25 am
Here you go...
http://www.worldwidewords.org/qa/qa-tea1.htm
It does look odd, but its meaning is clear enough: don’t give needless assistance or presume to offer advice to an expert. As that prolific author, Anon, once wrote:
Teach not thy parent’s mother to extract
The embryo juices of the bird by suction.
The good old lady can that feat enact,
Quite irrespective of your kind instruction.
Viewing 15 posts - 1 through 15 (of 33 total)
You must be logged in to reply to this topic. Login to reply