Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 12»»

Pro Active DBA Expand / Collapse
Author
Message
Posted Monday, September 16, 2013 2:32 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, March 4, 2014 2:02 AM
Points: 5, Visits: 33
Hi Guys,

I've recently been appointed to maintain my companies internal DB's. Must also stress the point that the DB's are quit critical, in the sense of CRM, Payroll etc.

I'm also very new to the administration environment of sql, however i've been working on it for the past 4 years now. But my experience was purely based on writing queries, scheduling backups, really basic stuff.

My purpose of this posting is, what can i do to be pro active in this new position? There is no handovers from previous dba's as all were actually outsourced. I'm the first internal dba appointed. I've got a chart of SQL Duties which is daily, weekly, monthly and yearly checks. I can also schedule the outsourced dba to be onsite, but i want to be prepared for that visit.

Any suggestions or advise? And i'm busy doing SQL 2012 courses and exams, but the process is "slowly but surely"

Would be nice for professional advise.
Post #1494961
Posted Wednesday, September 25, 2013 5:01 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Today @ 6:42 AM
Points: 2,837, Visits: 3,956
jacop (9/16/2013)
what can i do to be pro active in this new position?


In your daily list , there must be some monitoring job , some check list or some minor mintenance task .. do them efficiently and carefully.


-------Bhuvnesh----------
I work only to learn Sql Server...though my company pays me for getting their stuff done
Post #1498256
Posted Wednesday, September 25, 2013 8:16 AM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: Administrators
Last Login: Today @ 5:13 PM
Points: 33,100, Visits: 15,210
You might check this out: http://www.sqlservercentral.com/articles/books/67441






Follow me on Twitter: @way0utwest

Forum Etiquette: How to post data/code on a forum to get the best help
Post #1498387
Posted Monday, September 30, 2013 5:39 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Wednesday, March 19, 2014 5:28 AM
Points: 102, Visits: 1,050
This article will help you !

http://www.sqlservercentral.com/articles/Monitoring/67546/


Regards,
Kumar
Post #1499941
Posted Monday, September 30, 2013 5:46 PM


SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Yesterday @ 5:08 PM
Points: 178, Visits: 567
Whats the absolutely worst thing that could happen to your databases? What phone call would make your heart drop? OK now manage that risk by putting into place processes to reduce that risk.

So for starters make sure your backups work - don't just backup, run restores so you know they work.

Next is probably an application slowdown, so take some baselines now on resource usage so you have something to measure against when a slowdown occurs.
Post #1500226
Posted Tuesday, October 1, 2013 5:17 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: 2 days ago @ 6:11 AM
Points: 128, Visits: 240
Might I suggest Rodney Landrum's SQL Tacklebox located here:

http://www.red-gate.com/community/books/sql-server-tacklebox


He includes a boatload of scripts - downloadable as a zip file - for documenting and monitoring SQL Server instances using T-SQL and SSIS. At the very least it will give you a handle on what you've got running loose in your shop. And you can't beat the price!


____________
Just my $0.02 from over here in the cheap seats of the peanut gallery - please adjust for inflation and/or your local currency.
Post #1500342
Posted Wednesday, October 2, 2013 1:37 PM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Monday, July 28, 2014 12:02 PM
Points: 30, Visits: 869
A little knowledge is a dangerous thing....be careful.

First off, my advice is: Change nothing.

Monitor monitor monitor. Get to know the environment. Check all of the agent jobs, what do they do, when do they run, how long, what is the history - solid runs or occational failures. Do you need to deal with the failures? How?

Is a backup process in place? Are the indexes being maintained (http://ola.hallengren.com/)? Is there a process for monitoring disk use and datafile use/growth?

Brent Ozars sp_Blitz is a good starting point for digging around, but again dont change a thing based on this output. That wonky setting may be there for a reason.

Get the daily operational stuff down. Then you can look at improvements.
Post #1500900
Posted Thursday, October 3, 2013 2:00 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Today @ 6:42 AM
Points: 2,837, Visits: 3,956
Tony Savoie (10/2/2013)
dont change a thing based on this output. That wonky setting may be there for a reason.
i had good(even bad too ) experience on this


-------Bhuvnesh----------
I work only to learn Sql Server...though my company pays me for getting their stuff done
Post #1501041
Posted Thursday, October 3, 2013 2:23 AM


Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Today @ 9:48 AM
Points: 330, Visits: 3,214
www.SQLSkills.com
Some of this stuff is going to be a bit above your level at this point, but two resources I would recommend you digest right now would be their CommonSQLServerMyths pdf. There's a lot of SQL Server - bluntly, some of it poor and/or downright dangerous, this is a good primer on some of the commonest "wisdom" to discount.
Also their accidental DBA advice posts from a couple of months back will be of value.
Plus, their bad advice rollup http://www.sqlskills.com/blogs/paul/category/bad-advice/

They also sell training courses on the Pluralsight, some links here. http://www.sqlskills.com/blogs/paul/new-online-course-detecting-and-correcting-database-corruption/ as well as any other training your company is providing you with, you should try and get them to swing for this as well IMO. (I am nothing to do with SQLSkills, btw and have no links with them).
www.brentozar.com is also a good resource - also provide excellent tools and free and paid for online training


I'm a DBA.
I'm not paid to solve problems. I'm paid to prevent them.
Post #1501051
Posted Thursday, October 3, 2013 7:47 AM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: General Forum Members
Last Login: Today @ 8:58 PM
Points: 36,794, Visits: 31,253
Tony Savoie (10/2/2013)
A little knowledge is a dangerous thing....be careful.

First off, my advice is: Change nothing.

Monitor monitor monitor. Get to know the environment. Check all of the agent jobs, what do they do, when do they run, how long, what is the history - solid runs or occational failures. Do you need to deal with the failures? How?

Is a backup process in place? Are the indexes being maintained (http://ola.hallengren.com/)? Is there a process for monitoring disk use and datafile use/growth?

Brent Ozars sp_Blitz is a good starting point for digging around, but again dont change a thing based on this output. That wonky setting may be there for a reason.

Get the daily operational stuff down. Then you can look at improvements.


+10,000!!!!


--Jeff Moden
"RBAR is pronounced "ree-bar" and is a "Modenism" for "Row-By-Agonizing-Row".

First step towards the paradigm shift of writing Set Based code:
Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column."

(play on words) "Just because you CAN do something in T-SQL, doesn't mean you SHOULDN'T." --22 Aug 2013

Helpful Links:
How to post code problems
How to post performance problems
Post #1501189
« Prev Topic | Next Topic »

Add to briefcase 12»»

Permissions Expand / Collapse