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 123»»»

SQL Developer to SQL DBA Expand / Collapse
Author
Message
Posted Thursday, February 14, 2013 1:21 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, May 07, 2013 4:10 AM
Points: 8, Visits: 61
Any tips on making this career change?

Has anyone done this?

Many thanks,
Post #1419857
Posted Thursday, February 14, 2013 3:03 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Tuesday, April 30, 2013 5:59 AM
Points: 1,075, Visits: 5,114
Must read "How to become an Exceptional DBA" by Brad McGehee
Post #1419911
Posted Thursday, February 14, 2013 4:10 AM


SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: 2 days ago @ 3:02 AM
Points: 446, Visits: 348
Suresh B. (2/14/2013)
Must read "How to become an Exceptional DBA" by Brad McGehee


Not a bad read, here's a link to my copy of the ebook (pdf format): https://dl.dropbox.com/u/52486810/How_To_Become_An_Exceptional_DBA_Ebook.pdf



MCITP
MCTS - E-Business Card
Twitter: WWDMark

Try not! Do or do not, there is no try

email: info@weekendwebdesign.co.uk
Website: www.weekendwebdesign.co.uk
Post #1419947
Posted Thursday, February 14, 2013 4:14 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Friday, April 12, 2013 3:51 AM
Points: 5,075, Visits: 4,831
WWDMark (2/14/2013)
Suresh B. (2/14/2013)
Must read "How to become an Exceptional DBA" by Brad McGehee


Not a bad read, here's a link to my copy of the ebook (pdf format): https://dl.dropbox.com/u/52486810/How_To_Become_An_Exceptional_DBA_Ebook.pdf


Also available from the books section http://www.sqlservercentral.com/Books/




Want an answer fast? Try here
How to post data/code for the best help - Jeff Moden
Need a string splitter, try this - Jeff Moden
How to post performance problems - Gail Shaw
CrossTabs-Part1 & Part2 - Jeff Moden
SQL Server Backup, Integrity Check, and Index and Statistics Maintenance - Ola Hallengren
Managing Transaction Logs - Gail Shaw
Troubleshooting SQL Server: A Guide for the Accidental DBA - Jonathan Kehayias and Ted Krueger

Post #1419955
Posted Thursday, February 14, 2013 4:17 AM
SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Friday, May 03, 2013 5:35 AM
Points: 803, Visits: 2,122
Also worth a read is this http://www.red-gate.com/community/books/accidental-dba or you can buy it from amazon, just follow the amazon link.


Edit : Also on that link that Anthony sent


_________________________________________________________________________
SSC Guide to Posting and Best Practices
Post #1419958
Posted Thursday, February 14, 2013 4:18 AM


SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Yesterday @ 9:30 AM
Points: 484, Visits: 2,122
mr.neil.bryan (2/14/2013)
Any tips on making this career change?

Has anyone done this?

Many thanks,


Yup, I made this decision in July last year however, as hard as I tired I couldn't secure a full on DBA job so I took a 15k paycut and settled for a 50% DEV 50% DBA job. Now 6 months into my new role and I've learnt more about SQL Server than I did in 4 years in my previous role!

I am now given the opportunity to work with SQL Server 2005, 2008, 2008R2 and 2012. I do backups, restores, server installation/configuration etc.. I built my own DBA repository and was given the opportunity to invest in some great third part tools to monitory our SQL Server environments. All in all I feel like I made the right choice.
I love it... some days lunch time comes and goes and I don't even know about it that's how much fun it is.

The only thing I'm not working on is stuff like replication, clustering etc... That I guess will be for another adventure.

Good luck!


-----------------------------------
http://www.SQL4n00bs.com
Post #1419959
Posted Thursday, February 14, 2013 4:41 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 4:50 AM
Points: 13,371, Visits: 25,143
Brad's books is extremely good. You should also check out Thomas LaRock's book DBA Survivor. It covers the job from a different point of view.

----------------------------------------------------
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood..." Theodore Roosevelt
The Scary DBA
Author of: SQL Server 2012 Query Performance Tuning
SQL Server 2008 Query Performance Tuning Distilled
and
SQL Server Execution Plans

Product Evangelist for Red Gate Software
Post #1419975
Posted Thursday, February 14, 2013 11:16 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Yesterday @ 2:38 PM
Points: 1,318, Visits: 1,763
That's a significant change!

In order, here's a quick list of the most important things to do first:

1) Make sure the DBA role will fit you. As a developer, you get to see things through to production; often as a DBA you don't get those 'payoff' moment(s). Can you be happy in the new role?

2) Study indexes: how they work, and how they're built, particularly clustered indexes since they are the most critical aspect of db performance. You can have a big impact immediately as a DBA by tuning indexes, esp. getting rid of dopey clus indexes on identities and replacing them with clustered indexes on the join column(s) when appropriate (which it very often is).

3) Starting learing the Dynamic Management views and functions. They are the life blood now behind most DBA activities. This one alone will take quite a bit of time, so it will overlap other tasks.

4) Learn to use Profiler. Not used as much now as it used to be, because of the DM views and functions, but anyone will expect a DBA to know how to use it, and it is still necessary at times.

5) Learn how to add simple "Severity Level" alerts in SQL. They are easy to set up and can provide a quick heads up of issues when you're getting started. Since you'll want to use email for these, it also gives you a lead into learning how to set up db mail, operators, etc., which you do in conjunction with setting up the Alerts.


SQL DBA,SQL Server MVP('07, '08, '09)
One man with courage makes a majority. Andrew Jackson
Post #1420224
Posted Thursday, February 14, 2013 4:18 PM


SSC-Insane

SSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-Insane

Group: General Forum Members
Last Login: Today @ 7:10 PM
Points: 21,588, Visits: 27,380
ScottPletcher (2/14/2013)
That's a significant change!

In order, here's a quick list of the most important things to do first:

1) Make sure the DBA role will fit you. As a developer, you get to see things through to production; often as a DBA you don't get those 'payoff' moment(s). Can you be happy in the new role?

2) Study indexes: how they work, and how they're built, particularly clustered indexes since they are the most critical aspect of db performance. You can have a big impact immediately as a DBA by tuning indexes, esp. getting rid of dopey clus indexes on identities and replacing them with clustered indexes on the join column(s) when appropriate (which it very often is).

3) Starting learing the Dynamic Management views and functions. They are the life blood now behind most DBA activities. This one alone will take quite a bit of time, so it will overlap other tasks.

4) Learn to use Profiler. Not used as much now as it used to be, because of the DM views and functions, but anyone will expect a DBA to know how to use it, and it is still necessary at times.

5) Learn how to add simple "Severity Level" alerts in SQL. They are easy to set up and can provide a quick heads up of issues when you're getting started. Since you'll want to use email for these, it also gives you a lead into learning how to set up db mail, operators, etc., which you do in conjunction with setting up the Alerts.



Careful changing clustered indexes on tables. There may be significant reasons for their selection (or possibily not). Be sure if you do this that you have researched all the possibile implications of such changes. You don't want to get bit.



Lynn Pettis

For better assistance in answering your questions, click here
For tips to get better help with Performance Problems, click here
For Running Totals and its variations, click here or when working with partitioned tables
For more about Tally Tables, click here
For more about Cross Tabs and Pivots, click here and here
Managing Transaction Logs

SQL Musings from the Desert Fountain Valley SQL (My Mirror Blog)
Post #1420337
Posted Thursday, February 14, 2013 11:07 PM


SSC-Dedicated

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

Group: General Forum Members
Last Login: Today @ 6:14 PM
Points: 32,892, Visits: 26,763
ScottPletcher (2/14/2013)
That's a significant change!

In order, here's a quick list of the most important things to do first:

1) Make sure the DBA role will fit you. As a developer, you get to see things through to production; often as a DBA you don't get those 'payoff' moment(s). Can you be happy in the new role?

2) Study indexes: how they work, and how they're built, particularly clustered indexes since they are the most critical aspect of db performance. You can have a big impact immediately as a DBA by tuning indexes, esp. getting rid of dopey clus indexes on identities and replacing them with clustered indexes on the join column(s) when appropriate (which it very often is).

3) Starting learing the Dynamic Management views and functions. They are the life blood now behind most DBA activities. This one alone will take quite a bit of time, so it will overlap other tasks.

4) Learn to use Profiler. Not used as much now as it used to be, because of the DM views and functions, but anyone will expect a DBA to know how to use it, and it is still necessary at times.

5) Learn how to add simple "Severity Level" alerts in SQL. They are easy to set up and can provide a quick heads up of issues when you're getting started. Since you'll want to use email for these, it also gives you a lead into learning how to set up db mail, operators, etc., which you do in conjunction with setting up the Alerts.


Oh, be careful now. All of that stuff is really nice to know but, if they know nothing else, these are the two things all DBAs MUST absolutely know.

1. Learn how to do Point-in-Time Backups,Tail-Log Backups, and Point-In-Time Restores. Buy a copy of the SQL Server Developer's Edition and practice for hours every day for a month until you can do both in your sleep or when you have the worst hangover ever. You'll someday be required to do these tasks at 3 in the morning when you're both asleep and hungover.

2. Learn how to control all aspects of security. Don't forget to protect your backups. They ARE at risk and someone can rip off everything you have stored in your databases if they can get to your backups. Same thing here. Practice it until you puke.

The primary jobs of a DBA are to protect the data and protect the server. EVERYTHING else is secondary.

mr.neil.bryan (2/14/2013)
Any tips on making this career change?

Has anyone done this?

Many thanks,


Yes. See above. The true test of your metal will be 1) can you recover from a disaster and 2) can you keep the bad guys out even if the come from within.

The DBA is the "Gate Keeper". Protect the data, protect the server.


--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."

For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/

For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
Post #1420392
« Prev Topic | Next Topic »

Add to briefcase 123»»»

Permissions Expand / Collapse