Developer to DBA role

This is probably a wide open question but:
I'm coming from a developer role for the pass 12 years. I've created
everything from, components, web app, windows apps, mobile device
applications, etc. Now I'm getting ready to take over work on our databases,
Our DBA has left and I'm kind of stepping in to take on that role. So my
question is, coming from developer background, what do I need to know beyond
creating stored procedures and select statements to be a successful DBA? I
know from in the pass in working with DBA's that they do more then just
create stored procedures and database, what do I need to know such as,
replication, mirroring, security, performance, etc. where do I begin, is
there anything out there to help me get an understanding of a DBA role, or
should I just 'fly by the seam of my pants' on this one? (probably not a
good idea, but willing to try it)
thanks for any help and or suggestions you may have to offer, (good or bad
are accepted)just to add I know how to create users in the database, SSIS packages, I
guess its more on triggers, indexes, performance issues, replication,
mirroring, etc, suff like that I guess is what i'm looking for.
and other things a DBA does within this role.
"Mike" <Mike@.community.nospam.com> wrote in message
news:%23G$Syd3rHHA.1168@.TK2MSFTNGP03.phx.gbl...
> This is probably a wide open question but:
> I'm coming from a developer role for the pass 12 years. I've created
> everything from, components, web app, windows apps, mobile device
> applications, etc. Now I'm getting ready to take over work on our
> databases, Our DBA has left and I'm kind of stepping in to take on that
> role. So my question is, coming from developer background, what do I need
> to know beyond creating stored procedures and select statements to be a
> successful DBA? I know from in the pass in working with DBA's that they do
> more then just create stored procedures and database, what do I need to
> know such as, replication, mirroring, security, performance, etc. where do
> I begin, is there anything out there to help me get an understanding of a
> DBA role, or should I just 'fly by the seam of my pants' on this one?
> (probably not a good idea, but willing to try it)
>
> thanks for any help and or suggestions you may have to offer, (good or
> bad are accepted)
>
>|||http://groups.google.com/group/microsoft.public.sqlserver.programming/browse_thread/thread/f696a9ae540bf1a0/01482ed3de91192f?hl=en#01482ed3de91192f|||I was in the same boat. Microsoft has some really good training
classes and I'd highly recommend getting into one of those as soon as
you can. They'll cover a broad range of your day to day operations
like backups and security. Also, get familiar with some networking
knowledge as well. You're going to be walking the line between
hardware and software. But, the first thing is with only SQL Dev
experience I'd see what, if any, training classes you can get into. If
anything the book can be used for reference for TSQL statements.|||First and most importantly, you need to be able to put the system back the
way it was yesterday, data and all. Fully document the system and make sure
your recovery strategy is in place and tested.
Second, all developers are now your natural enemy. They write code to
destroy the data and performance. It is your job to limit the damage they
can do. See requirement #1.
Performance monitoring and tuning must now be regular parts of your routine.
Security just became your problem. You don't want to be the next headline
on data lost or hacked.
There are lots more, but this should keep you up nights for the next few
months.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Mike" <Mike@.community.nospam.com> wrote in message
news:OinW2i3rHHA.632@.TK2MSFTNGP03.phx.gbl...
> just to add I know how to create users in the database, SSIS packages, I
> guess its more on triggers, indexes, performance issues, replication,
> mirroring, etc, suff like that I guess is what i'm looking for.
> and other things a DBA does within this role.
>
> "Mike" <Mike@.community.nospam.com> wrote in message
> news:%23G$Syd3rHHA.1168@.TK2MSFTNGP03.phx.gbl...
>> This is probably a wide open question but:
>> I'm coming from a developer role for the pass 12 years. I've created
>> everything from, components, web app, windows apps, mobile device
>> applications, etc. Now I'm getting ready to take over work on our
>> databases, Our DBA has left and I'm kind of stepping in to take on that
>> role. So my question is, coming from developer background, what do I need
>> to know beyond creating stored procedures and select statements to be a
>> successful DBA? I know from in the pass in working with DBA's that they
>> do more then just create stored procedures and database, what do I need
>> to know such as, replication, mirroring, security, performance, etc.
>> where do I begin, is there anything out there to help me get an
>> understanding of a DBA role, or should I just 'fly by the seam of my
>> pants' on this one? (probably not a good idea, but willing to try it)
>>
>> thanks for any help and or suggestions you may have to offer, (good or
>> bad are accepted)
>>
>|||Thanks, I'm now second guessing myself for taken this task on and learn
something new.
> First and most importantly, you need to be able to put the system back the
> way it was yesterday, data and all. Fully document the system and make
> sure your recovery strategy is in place and tested.
I can say I was successful in restoring all the databases when the
server actually crashed. I learned that process hands on. The only thing
though I had to add all of the logins again manually. Is there a way to back
up the 'Security' folder so I can all Login ID and Privilages or no?
> Second, all developers are now your natural enemy. They write code to
> destroy the data and performance. It is your job to limit the damage they
> can do. See requirement #1.
Coming from development, I admit I either brought down a DB or locked a db
in my development days.
> Security just became your problem. You don't want to be the next headline
> on data lost or hacked.
this part I like because I handled alot of the security for the
applications I developed. Though this is a different level of security.
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:OtZbfu3rHHA.1476@.TK2MSFTNGP06.phx.gbl...
> First and most importantly, you need to be able to put the system back the
> way it was yesterday, data and all. Fully document the system and make
> sure your recovery strategy is in place and tested.
> Second, all developers are now your natural enemy. They write code to
> destroy the data and performance. It is your job to limit the damage they
> can do. See requirement #1.
> Performance monitoring and tuning must now be regular parts of your
> routine.
> Security just became your problem. You don't want to be the next headline
> on data lost or hacked.
> There are lots more, but this should keep you up nights for the next few
> months.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
>
> "Mike" <Mike@.community.nospam.com> wrote in message
> news:OinW2i3rHHA.632@.TK2MSFTNGP03.phx.gbl...
>> just to add I know how to create users in the database, SSIS packages, I
>> guess its more on triggers, indexes, performance issues, replication,
>> mirroring, etc, suff like that I guess is what i'm looking for.
>> and other things a DBA does within this role.
>>
>> "Mike" <Mike@.community.nospam.com> wrote in message
>> news:%23G$Syd3rHHA.1168@.TK2MSFTNGP03.phx.gbl...
>> This is probably a wide open question but:
>> I'm coming from a developer role for the pass 12 years. I've created
>> everything from, components, web app, windows apps, mobile device
>> applications, etc. Now I'm getting ready to take over work on our
>> databases, Our DBA has left and I'm kind of stepping in to take on that
>> role. So my question is, coming from developer background, what do I
>> need to know beyond creating stored procedures and select statements to
>> be a successful DBA? I know from in the pass in working with DBA's that
>> they do more then just create stored procedures and database, what do I
>> need to know such as, replication, mirroring, security, performance,
>> etc. where do I begin, is there anything out there to help me get an
>> understanding of a DBA role, or should I just 'fly by the seam of my
>> pants' on this one? (probably not a good idea, but willing to try it)
>>
>> thanks for any help and or suggestions you may have to offer, (good or
>> bad are accepted)
>>
>>
>|||Thanks, I'm going to be looking online this weekend for classes in my area.
"Pawn" <TheRealPawn@.gmail.com> wrote in message
news:1181932262.511711.220810@.q66g2000hsg.googlegroups.com...
>I was in the same boat. Microsoft has some really good training
> classes and I'd highly recommend getting into one of those as soon as
> you can. They'll cover a broad range of your day to day operations
> like backups and security. Also, get familiar with some networking
> knowledge as well. You're going to be walking the line between
> hardware and software. But, the first thing is with only SQL Dev
> experience I'd see what, if any, training classes you can get into. If
> anything the book can be used for reference for TSQL statements.
>|||what about replication, mirroring, or clustering? Or should I not worry
about that until the time comes? According to the mgr none of the above are
used Just backups of the db's on a nightly basis.
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:OtZbfu3rHHA.1476@.TK2MSFTNGP06.phx.gbl...
> First and most importantly, you need to be able to put the system back the
> way it was yesterday, data and all. Fully document the system and make
> sure your recovery strategy is in place and tested.
> Second, all developers are now your natural enemy. They write code to
> destroy the data and performance. It is your job to limit the damage they
> can do. See requirement #1.
> Performance monitoring and tuning must now be regular parts of your
> routine.
> Security just became your problem. You don't want to be the next headline
> on data lost or hacked.
> There are lots more, but this should keep you up nights for the next few
> months.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
>
> "Mike" <Mike@.community.nospam.com> wrote in message
> news:OinW2i3rHHA.632@.TK2MSFTNGP03.phx.gbl...
>> just to add I know how to create users in the database, SSIS packages, I
>> guess its more on triggers, indexes, performance issues, replication,
>> mirroring, etc, suff like that I guess is what i'm looking for.
>> and other things a DBA does within this role.
>>
>> "Mike" <Mike@.community.nospam.com> wrote in message
>> news:%23G$Syd3rHHA.1168@.TK2MSFTNGP03.phx.gbl...
>> This is probably a wide open question but:
>> I'm coming from a developer role for the pass 12 years. I've created
>> everything from, components, web app, windows apps, mobile device
>> applications, etc. Now I'm getting ready to take over work on our
>> databases, Our DBA has left and I'm kind of stepping in to take on that
>> role. So my question is, coming from developer background, what do I
>> need to know beyond creating stored procedures and select statements to
>> be a successful DBA? I know from in the pass in working with DBA's that
>> they do more then just create stored procedures and database, what do I
>> need to know such as, replication, mirroring, security, performance,
>> etc. where do I begin, is there anything out there to help me get an
>> understanding of a DBA role, or should I just 'fly by the seam of my
>> pants' on this one? (probably not a good idea, but willing to try it)
>>
>> thanks for any help and or suggestions you may have to offer, (good or
>> bad are accepted)
>>
>>
>|||Hey, not ALL developers are bad. Just the great majority. Coming out
of the trenches yourself you probably get along well with them so when
you see a performance problem they will most likely be very receptive
to your suggestions on how to fix it. SQL Profiler and Performance
Monitor have just become some of your best friends. Though they do add
overhead to the server so use them sparingly.
This site may help you figure out some more details about performance
monitors:
http://www.sql-server-performance.com/
Here's a link on what your day-to-day's may include:
http://www.databasedesign-resource.com/sql-server-dba.html
On Jun 15, 2:33 pm, "Geoff N. Hiten" <SQLCrafts...@.gmail.com> wrote:
> First and most importantly, you need to be able to put the system back the
> way it was yesterday, data and all. Fully document the system and make sure
> your recovery strategy is in place and tested.
> Second, all developers are now your natural enemy. They write code to
> destroy the data and performance. It is your job to limit the damage they
> can do. See requirement #1.
> Performance monitoring and tuning must now be regular parts of your routine.
> Security just became your problem. You don't want to be the next headline
> on data lost or hacked.
> There are lots more, but this should keep you up nights for the next few
> months.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
> "Mike" <M...@.community.nospam.com> wrote in message
> news:OinW2i3rHHA.632@.TK2MSFTNGP03.phx.gbl...
> > just to add I know how to create users in the database, SSIS packages, I
> > guess its more on triggers, indexes, performance issues, replication,
> > mirroring, etc, suff like that I guess is what i'm looking for.
> > and other things a DBA does within this role.
> > "Mike" <M...@.community.nospam.com> wrote in message
> >news:%23G$Syd3rHHA.1168@.TK2MSFTNGP03.phx.gbl...
> >> This is probably a wide open question but:
> >> I'm coming from a developer role for the pass 12 years. I've created
> >> everything from, components, web app, windows apps, mobile device
> >> applications, etc. Now I'm getting ready to take over work on our
> >> databases, Our DBA has left and I'm kind of stepping in to take on that
> >> role. So my question is, coming from developer background, what do I need
> >> to know beyond creating stored procedures and select statements to be a
> >> successful DBA? I know from in the pass in working with DBA's that they
> >> do more then just create stored procedures and database, what do I need
> >> to know such as, replication, mirroring, security, performance, etc.
> >> where do I begin, is there anything out there to help me get an
> >> understanding of a DBA role, or should I just 'fly by the seam of my
> >> pants' on this one? (probably not a good idea, but willing to try it)
> >> thanks for any help and or suggestions you may have to offer, (good or
> >> bad are accepted)|||thanks I greatly appreciate the information.
This Database stuff is a whole new world to me (from a true dba perspective)
and I was willing to give it a shot.
"Pawn" <TheRealPawn@.gmail.com> wrote in message
news:1181933280.917354.9000@.p77g2000hsh.googlegroups.com...
> Hey, not ALL developers are bad. Just the great majority. Coming out
> of the trenches yourself you probably get along well with them so when
> you see a performance problem they will most likely be very receptive
> to your suggestions on how to fix it. SQL Profiler and Performance
> Monitor have just become some of your best friends. Though they do add
> overhead to the server so use them sparingly.
> This site may help you figure out some more details about performance
> monitors:
> http://www.sql-server-performance.com/
> Here's a link on what your day-to-day's may include:
> http://www.databasedesign-resource.com/sql-server-dba.html
> On Jun 15, 2:33 pm, "Geoff N. Hiten" <SQLCrafts...@.gmail.com> wrote:
>> First and most importantly, you need to be able to put the system back
>> the
>> way it was yesterday, data and all. Fully document the system and make
>> sure
>> your recovery strategy is in place and tested.
>> Second, all developers are now your natural enemy. They write code to
>> destroy the data and performance. It is your job to limit the damage
>> they
>> can do. See requirement #1.
>> Performance monitoring and tuning must now be regular parts of your
>> routine.
>> Security just became your problem. You don't want to be the next
>> headline
>> on data lost or hacked.
>> There are lots more, but this should keep you up nights for the next few
>> months.
>> --
>> Geoff N. Hiten
>> Senior Database Administrator
>> Microsoft SQL Server MVP
>> "Mike" <M...@.community.nospam.com> wrote in message
>> news:OinW2i3rHHA.632@.TK2MSFTNGP03.phx.gbl...
>> > just to add I know how to create users in the database, SSIS packages,
>> > I
>> > guess its more on triggers, indexes, performance issues, replication,
>> > mirroring, etc, suff like that I guess is what i'm looking for.
>> > and other things a DBA does within this role.
>> > "Mike" <M...@.community.nospam.com> wrote in message
>> >news:%23G$Syd3rHHA.1168@.TK2MSFTNGP03.phx.gbl...
>> >> This is probably a wide open question but:
>> >> I'm coming from a developer role for the pass 12 years. I've created
>> >> everything from, components, web app, windows apps, mobile device
>> >> applications, etc. Now I'm getting ready to take over work on our
>> >> databases, Our DBA has left and I'm kind of stepping in to take on
>> >> that
>> >> role. So my question is, coming from developer background, what do I
>> >> need
>> >> to know beyond creating stored procedures and select statements to be
>> >> a
>> >> successful DBA? I know from in the pass in working with DBA's that
>> >> they
>> >> do more then just create stored procedures and database, what do I
>> >> need
>> >> to know such as, replication, mirroring, security, performance, etc.
>> >> where do I begin, is there anything out there to help me get an
>> >> understanding of a DBA role, or should I just 'fly by the seam of my
>> >> pants' on this one? (probably not a good idea, but willing to try it)
>> >> thanks for any help and or suggestions you may have to offer, (good
>> >> or
>> >> bad are accepted)
>
>|||> Is there a way to back up the 'Security' folder so I can all Login ID and Privilages or no?
You need to "get" the architecture of SQL Server. Logins are in the master database, so with proper
backup of master, you have your logins. Having said that, Google for sp_help_revlogin.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Mike" <Mike@.community.nospam.com> wrote in message news:eeD1Sz3rHHA.5032@.TK2MSFTNGP02.phx.gbl...
> Thanks, I'm now second guessing myself for taken this task on and learn something new.
>> First and most importantly, you need to be able to put the system back the way it was yesterday,
>> data and all. Fully document the system and make sure your recovery strategy is in place and
>> tested.
> I can say I was successful in restoring all the databases when the server actually crashed. I
> learned that process hands on. The only thing though I had to add all of the logins again
> manually. Is there a way to back up the 'Security' folder so I can all Login ID and Privilages or
> no?
>
>> Second, all developers are now your natural enemy. They write code to destroy the data and
>> performance. It is your job to limit the damage they can do. See requirement #1.
> Coming from development, I admit I either brought down a DB or locked a db in my development
> days.
>
>> Security just became your problem. You don't want to be the next headline on data lost or
>> hacked.
> this part I like because I handled alot of the security for the applications I developed.
> Though this is a different level of security.
>
> "Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
> news:OtZbfu3rHHA.1476@.TK2MSFTNGP06.phx.gbl...
>> First and most importantly, you need to be able to put the system back the way it was yesterday,
>> data and all. Fully document the system and make sure your recovery strategy is in place and
>> tested.
>> Second, all developers are now your natural enemy. They write code to destroy the data and
>> performance. It is your job to limit the damage they can do. See requirement #1.
>> Performance monitoring and tuning must now be regular parts of your routine.
>> Security just became your problem. You don't want to be the next headline on data lost or
>> hacked.
>> There are lots more, but this should keep you up nights for the next few months.
>> --
>> Geoff N. Hiten
>> Senior Database Administrator
>> Microsoft SQL Server MVP
>>
>>
>>
>> "Mike" <Mike@.community.nospam.com> wrote in message news:OinW2i3rHHA.632@.TK2MSFTNGP03.phx.gbl...
>> just to add I know how to create users in the database, SSIS packages, I guess its more on
>> triggers, indexes, performance issues, replication, mirroring, etc, suff like that I guess is
>> what i'm looking for.
>> and other things a DBA does within this role.
>>
>> "Mike" <Mike@.community.nospam.com> wrote in message
>> news:%23G$Syd3rHHA.1168@.TK2MSFTNGP03.phx.gbl...
>> This is probably a wide open question but:
>> I'm coming from a developer role for the pass 12 years. I've created everything from,
>> components, web app, windows apps, mobile device applications, etc. Now I'm getting ready to
>> take over work on our databases, Our DBA has left and I'm kind of stepping in to take on that
>> role. So my question is, coming from developer background, what do I need to know beyond
>> creating stored procedures and select statements to be a successful DBA? I know from in the
>> pass in working with DBA's that they do more then just create stored procedures and database,
>> what do I need to know such as, replication, mirroring, security, performance, etc. where do I
>> begin, is there anything out there to help me get an understanding of a DBA role, or should I
>> just 'fly by the seam of my pants' on this one? (probably not a good idea, but willing to try
>> it)
>>
>> thanks for any help and or suggestions you may have to offer, (good or bad are accepted)
>>
>>
>>
>|||As a trainer, I know the (MS) SQL Server courses inside out. Here's my recommendation:
2780, which is an admin class. Sure, you might know bits here and there already, but if you are
about to shift position, they (your managers) would want to invest a bit. Make sure you get the 5
days revision of the course (B rev), and preferably from a reputable instructor. Added value differs
a lot. I have difficulties managing to teach this class for the specified time, while other say
there is way too much time allocated.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Mike" <Mike@.community.nospam.com> wrote in message news:OziQgz3rHHA.3500@.TK2MSFTNGP04.phx.gbl...
> Thanks, I'm going to be looking online this weekend for classes in my area.
>
> "Pawn" <TheRealPawn@.gmail.com> wrote in message
> news:1181932262.511711.220810@.q66g2000hsg.googlegroups.com...
>>I was in the same boat. Microsoft has some really good training
>> classes and I'd highly recommend getting into one of those as soon as
>> you can. They'll cover a broad range of your day to day operations
>> like backups and security. Also, get familiar with some networking
>> knowledge as well. You're going to be walking the line between
>> hardware and software. But, the first thing is with only SQL Dev
>> experience I'd see what, if any, training classes you can get into. If
>> anything the book can be used for reference for TSQL statements.
>|||Unless you are currently using or expect to use a technology, I would not
> worry about it on day one. Getting a handle on managing, recovering, and
> operating the server AS IS should be your top priority. Learn about what
> new technologies can and cannot do so you can make intelligent
> recommendations, but unless they are part of your current environment,
> they are not part of your current problem set.
Ok and as of now nothing is really used (replication, mirroring, etc)
> As for the developer comments, I have worked as a developer, a system
> admin, and as a DBA over the course of my career. Each has a different
> perspective on the system and different goals. Sometimes those goals are
> in wildly different directions.
Myself as well, I started out as a helpdesk person many years ago when I
started in the corporate IT world, and done everything in IT you can think
of from helpdesk, sys admin, email server admin, developer, architecture,
and now the new task of DBA (I'm ready for a new challange)
> Don't rely on luck to restore a system. Have a plan and practice it.
> Test your backups regularly. Training classes will help give you the
> knowledge to build an effective operations and recovery plan, but you have
> to do the heavy lifting. Remember, management does not care about
> backups, they care about restores.
I'm actually building a test server with SQL on it that has not app
connected to it. I want to get more familiar with the OS crashing, the DB
crashing, etc and work on restoring the DB as close to possible as it was
prior to the 'crash'
> Good luck. I figure we will see you around here quite a bit in the months
> to come. :)
thanks, I need some luck, yeah. I'll probably live here for the next few
months with tons of questions.
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:uNeVj83rHHA.1168@.TK2MSFTNGP03.phx.gbl...
> Unless you are currently using or expect to use a technology, I would not
> worry about it on day one. Getting a handle on managing, recovering, and
> operating the server AS IS should be your top priority. Learn about what
> new technologies can and cannot do so you can make intelligent
> recommendations, but unless they are part of your current environment,
> they are not part of your current problem set.
> As for the developer comments, I have worked as a developer, a system
> admin, and as a DBA over the course of my career. Each has a different
> perspective on the system and different goals. Sometimes those goals are
> in wildly different directions.
> Don't rely on luck to restore a system. Have a plan and practice it.
> Test your backups regularly. Training classes will help give you the
> knowledge to build an effective operations and recovery plan, but you have
> to do the heavy lifting. Remember, management does not care about
> backups, they care about restores.
> Good luck. I figure we will see you around here quite a bit in the months
> to come. :)
>
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "Mike" <Mike@.community.nospam.com> wrote in message
> news:O70I913rHHA.4548@.TK2MSFTNGP03.phx.gbl...
>> what about replication, mirroring, or clustering? Or should I not worry
>> about that until the time comes? According to the mgr none of the above
>> are used Just backups of the db's on a nightly basis.
>>
>> "Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
>> news:OtZbfu3rHHA.1476@.TK2MSFTNGP06.phx.gbl...
>> First and most importantly, you need to be able to put the system back
>> the way it was yesterday, data and all. Fully document the system and
>> make sure your recovery strategy is in place and tested.
>> Second, all developers are now your natural enemy. They write code to
>> destroy the data and performance. It is your job to limit the damage
>> they can do. See requirement #1.
>> Performance monitoring and tuning must now be regular parts of your
>> routine.
>> Security just became your problem. You don't want to be the next
>> headline on data lost or hacked.
>> There are lots more, but this should keep you up nights for the next few
>> months.
>> --
>> Geoff N. Hiten
>> Senior Database Administrator
>> Microsoft SQL Server MVP
>>
>>
>>
>> "Mike" <Mike@.community.nospam.com> wrote in message
>> news:OinW2i3rHHA.632@.TK2MSFTNGP03.phx.gbl...
>> just to add I know how to create users in the database, SSIS packages,
>> I guess its more on triggers, indexes, performance issues, replication,
>> mirroring, etc, suff like that I guess is what i'm looking for.
>> and other things a DBA does within this role.
>>
>> "Mike" <Mike@.community.nospam.com> wrote in message
>> news:%23G$Syd3rHHA.1168@.TK2MSFTNGP03.phx.gbl...
>> This is probably a wide open question but:
>> I'm coming from a developer role for the pass 12 years. I've created
>> everything from, components, web app, windows apps, mobile device
>> applications, etc. Now I'm getting ready to take over work on our
>> databases, Our DBA has left and I'm kind of stepping in to take on
>> that role. So my question is, coming from developer background, what
>> do I need to know beyond creating stored procedures and select
>> statements to be a successful DBA? I know from in the pass in working
>> with DBA's that they do more then just create stored procedures and
>> database, what do I need to know such as, replication, mirroring,
>> security, performance, etc. where do I begin, is there anything out
>> there to help me get an understanding of a DBA role, or should I just
>> 'fly by the seam of my pants' on this one? (probably not a good idea,
>> but willing to try it)
>>
>> thanks for any help and or suggestions you may have to offer, (good
>> or bad are accepted)
>>
>>
>>
>>
>|||Unless you are currently using or expect to use a technology, I would not
worry about it on day one. Getting a handle on managing, recovering, and
operating the server AS IS should be your top priority. Learn about what
new technologies can and cannot do so you can make intelligent
recommendations, but unless they are part of your current environment, they
are not part of your current problem set.
As for the developer comments, I have worked as a developer, a system admin,
and as a DBA over the course of my career. Each has a different perspective
on the system and different goals. Sometimes those goals are in wildly
different directions.
Don't rely on luck to restore a system. Have a plan and practice it. Test
your backups regularly. Training classes will help give you the knowledge
to build an effective operations and recovery plan, but you have to do the
heavy lifting. Remember, management does not care about backups, they care
about restores.
Good luck. I figure we will see you around here quite a bit in the months
to come. :)
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Mike" <Mike@.community.nospam.com> wrote in message
news:O70I913rHHA.4548@.TK2MSFTNGP03.phx.gbl...
> what about replication, mirroring, or clustering? Or should I not worry
> about that until the time comes? According to the mgr none of the above
> are used Just backups of the db's on a nightly basis.
>
> "Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
> news:OtZbfu3rHHA.1476@.TK2MSFTNGP06.phx.gbl...
>> First and most importantly, you need to be able to put the system back
>> the way it was yesterday, data and all. Fully document the system and
>> make sure your recovery strategy is in place and tested.
>> Second, all developers are now your natural enemy. They write code to
>> destroy the data and performance. It is your job to limit the damage
>> they can do. See requirement #1.
>> Performance monitoring and tuning must now be regular parts of your
>> routine.
>> Security just became your problem. You don't want to be the next
>> headline on data lost or hacked.
>> There are lots more, but this should keep you up nights for the next few
>> months.
>> --
>> Geoff N. Hiten
>> Senior Database Administrator
>> Microsoft SQL Server MVP
>>
>>
>>
>> "Mike" <Mike@.community.nospam.com> wrote in message
>> news:OinW2i3rHHA.632@.TK2MSFTNGP03.phx.gbl...
>> just to add I know how to create users in the database, SSIS packages, I
>> guess its more on triggers, indexes, performance issues, replication,
>> mirroring, etc, suff like that I guess is what i'm looking for.
>> and other things a DBA does within this role.
>>
>> "Mike" <Mike@.community.nospam.com> wrote in message
>> news:%23G$Syd3rHHA.1168@.TK2MSFTNGP03.phx.gbl...
>> This is probably a wide open question but:
>> I'm coming from a developer role for the pass 12 years. I've created
>> everything from, components, web app, windows apps, mobile device
>> applications, etc. Now I'm getting ready to take over work on our
>> databases, Our DBA has left and I'm kind of stepping in to take on that
>> role. So my question is, coming from developer background, what do I
>> need to know beyond creating stored procedures and select statements to
>> be a successful DBA? I know from in the pass in working with DBA's that
>> they do more then just create stored procedures and database, what do I
>> need to know such as, replication, mirroring, security, performance,
>> etc. where do I begin, is there anything out there to help me get an
>> understanding of a DBA role, or should I just 'fly by the seam of my
>> pants' on this one? (probably not a good idea, but willing to try it)
>>
>> thanks for any help and or suggestions you may have to offer, (good or
>> bad are accepted)
>>
>>
>>
>|||2072A is the one that I took but I don't think it's offered anymore
On Jun 15, 3:04 pm, "Tibor Karaszi"
<tibor_please.no.email_kara...@.hotmail.nomail.com> wrote:
> As a trainer, I know the (MS) SQL Server courses inside out. Here's my recommendation:
> 2780, which is an admin class. Sure, you might know bits here and there already, but if you are
> about to shift position, they (your managers) would want to invest a bit. Make sure you get the 5
> days revision of the course (B rev), and preferably from a reputable instructor. Added value differs
> a lot. I have difficulties managing to teach this class for the specified time, while other say
> there is way too much time allocated.
> --
> Tibor Karaszi, SQL Server MVPhttp://www.karaszi.com/sqlserver/default.asphttp://sqlblog.com/blogs/tibor_karaszi
> "Mike" <M...@.community.nospam.com> wrote in messagenews:OziQgz3rHHA.3500@.TK2MSFTNGP04.phx.gbl...
> > Thanks, I'm going to be looking online this weekend for classes in my area.
> > "Pawn" <TheRealP...@.gmail.com> wrote in message
> >news:1181932262.511711.220810@.q66g2000hsg.googlegroups.com...
> >>I was in the same boat. Microsoft has some really good training
> >> classes and I'd highly recommend getting into one of those as soon as
> >> you can. They'll cover a broad range of your day to day operations
> >> like backups and security. Also, get familiar with some networking
> >> knowledge as well. You're going to be walking the line between
> >> hardware and software. But, the first thing is with only SQL Dev
> >> experience I'd see what, if any, training classes you can get into. If
> >> anything the book can be used for reference for TSQL statements.|||And for my first SQL task at hand is to convert all 10 servers running SQL
2000 to SQL 2005 and each server has a range from 10 to 125 databases on
them.
So this is to start Monday and end by July 1. So I guess I'm hitting the DB
world running.
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:uNeVj83rHHA.1168@.TK2MSFTNGP03.phx.gbl...
> Unless you are currently using or expect to use a technology, I would not
> worry about it on day one. Getting a handle on managing, recovering, and
> operating the server AS IS should be your top priority. Learn about what
> new technologies can and cannot do so you can make intelligent
> recommendations, but unless they are part of your current environment,
> they are not part of your current problem set.
> As for the developer comments, I have worked as a developer, a system
> admin, and as a DBA over the course of my career. Each has a different
> perspective on the system and different goals. Sometimes those goals are
> in wildly different directions.
> Don't rely on luck to restore a system. Have a plan and practice it.
> Test your backups regularly. Training classes will help give you the
> knowledge to build an effective operations and recovery plan, but you have
> to do the heavy lifting. Remember, management does not care about
> backups, they care about restores.
> Good luck. I figure we will see you around here quite a bit in the months
> to come. :)
>
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "Mike" <Mike@.community.nospam.com> wrote in message
> news:O70I913rHHA.4548@.TK2MSFTNGP03.phx.gbl...
>> what about replication, mirroring, or clustering? Or should I not worry
>> about that until the time comes? According to the mgr none of the above
>> are used Just backups of the db's on a nightly basis.
>>
>> "Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
>> news:OtZbfu3rHHA.1476@.TK2MSFTNGP06.phx.gbl...
>> First and most importantly, you need to be able to put the system back
>> the way it was yesterday, data and all. Fully document the system and
>> make sure your recovery strategy is in place and tested.
>> Second, all developers are now your natural enemy. They write code to
>> destroy the data and performance. It is your job to limit the damage
>> they can do. See requirement #1.
>> Performance monitoring and tuning must now be regular parts of your
>> routine.
>> Security just became your problem. You don't want to be the next
>> headline on data lost or hacked.
>> There are lots more, but this should keep you up nights for the next few
>> months.
>> --
>> Geoff N. Hiten
>> Senior Database Administrator
>> Microsoft SQL Server MVP
>>
>>
>>
>> "Mike" <Mike@.community.nospam.com> wrote in message
>> news:OinW2i3rHHA.632@.TK2MSFTNGP03.phx.gbl...
>> just to add I know how to create users in the database, SSIS packages,
>> I guess its more on triggers, indexes, performance issues, replication,
>> mirroring, etc, suff like that I guess is what i'm looking for.
>> and other things a DBA does within this role.
>>
>> "Mike" <Mike@.community.nospam.com> wrote in message
>> news:%23G$Syd3rHHA.1168@.TK2MSFTNGP03.phx.gbl...
>> This is probably a wide open question but:
>> I'm coming from a developer role for the pass 12 years. I've created
>> everything from, components, web app, windows apps, mobile device
>> applications, etc. Now I'm getting ready to take over work on our
>> databases, Our DBA has left and I'm kind of stepping in to take on
>> that role. So my question is, coming from developer background, what
>> do I need to know beyond creating stored procedures and select
>> statements to be a successful DBA? I know from in the pass in working
>> with DBA's that they do more then just create stored procedures and
>> database, what do I need to know such as, replication, mirroring,
>> security, performance, etc. where do I begin, is there anything out
>> there to help me get an understanding of a DBA role, or should I just
>> 'fly by the seam of my pants' on this one? (probably not a good idea,
>> but willing to try it)
>>
>> thanks for any help and or suggestions you may have to offer, (good
>> or bad are accepted)
>>
>>
>>
>>
>|||Thanks, I'll be looking over the weekend and even next week for SQL courses
in my area.
I've seen online courses and I've even taken some of them for .NET. How
would they work for the SQL side of the house?
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:1E9EE097-CD31-4291-A4D1-874541D7BC6B@.microsoft.com...
> As a trainer, I know the (MS) SQL Server courses inside out. Here's my
> recommendation:
> 2780, which is an admin class. Sure, you might know bits here and there
> already, but if you are about to shift position, they (your managers)
> would want to invest a bit. Make sure you get the 5 days revision of the
> course (B rev), and preferably from a reputable instructor. Added value
> differs a lot. I have difficulties managing to teach this class for the
> specified time, while other say there is way too much time allocated.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Mike" <Mike@.community.nospam.com> wrote in message
> news:OziQgz3rHHA.3500@.TK2MSFTNGP04.phx.gbl...
>> Thanks, I'm going to be looking online this weekend for classes in my
>> area.
>>
>> "Pawn" <TheRealPawn@.gmail.com> wrote in message
>> news:1181932262.511711.220810@.q66g2000hsg.googlegroups.com...
>>I was in the same boat. Microsoft has some really good training
>> classes and I'd highly recommend getting into one of those as soon as
>> you can. They'll cover a broad range of your day to day operations
>> like backups and security. Also, get familiar with some networking
>> knowledge as well. You're going to be walking the line between
>> hardware and software. But, the first thing is with only SQL Dev
>> experience I'd see what, if any, training classes you can get into. If
>> anything the book can be used for reference for TSQL statements.
>>
>|||On Jun 15, 3:12 pm, "Mike" <M...@.community.nospam.com> wrote:
> Thanks, I'll be looking over the weekend and even next week for SQL courses
> in my area.
> I've seen online courses and I've even taken some of them for .NET. How
> would they work for the SQL side of the house?
> "Tibor Karaszi" <tibor_please.no.email_kara...@.hotmail.nomail.com> wrote in
> messagenews:1E9EE097-CD31-4291-A4D1-874541D7BC6B@.microsoft.com...
>
> > As a trainer, I know the (MS) SQL Server courses inside out. Here's my
> > recommendation:
> > 2780, which is an admin class. Sure, you might know bits here and there
> > already, but if you are about to shift position, they (your managers)
> > would want to invest a bit. Make sure you get the 5 days revision of the
> > course (B rev), and preferably from a reputable instructor. Added value
> > differs a lot. I have difficulties managing to teach this class for the
> > specified time, while other say there is way too much time allocated.
> > --
> > Tibor Karaszi, SQL Server MVP
> >http://www.karaszi.com/sqlserver/default.asp
> >http://sqlblog.com/blogs/tibor_karaszi
> > "Mike" <M...@.community.nospam.com> wrote in message
> >news:OziQgz3rHHA.3500@.TK2MSFTNGP04.phx.gbl...
> >> Thanks, I'm going to be looking online this weekend for classes in my
> >> area.
> >> "Pawn" <TheRealP...@.gmail.com> wrote in message
> >>news:1181932262.511711.220810@.q66g2000hsg.googlegroups.com...
> >>I was in the same boat. Microsoft has some really good training
> >> classes and I'd highly recommend getting into one of those as soon as
> >> you can. They'll cover a broad range of your day to day operations
> >> like backups and security. Also, get familiar with some networking
> >> knowledge as well. You're going to be walking the line between
> >> hardware and software. But, the first thing is with only SQL Dev
> >> experience I'd see what, if any, training classes you can get into. If
> >> anything the book can be used for reference for TSQL statements.- Hide quoted text -
> - Show quoted text -
Wrox press has a good book on SQL 2005 Administration. It basically
covers the basics of a lot of things...|||Yes, 2072 is for 2000, and 2780 is the successor for 2005. 2780 was initially 3 days, covering same
areas as 2072, since customers requested shorter courses. This wasn't doable (3 days), of course, so
after some lobbying a revision B of the course was (is) released upped to 5 days.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Pawn" <TheRealPawn@.gmail.com> wrote in message
news:1181934688.597868.276400@.n2g2000hse.googlegroups.com...
> 2072A is the one that I took but I don't think it's offered anymore
> On Jun 15, 3:04 pm, "Tibor Karaszi"
> <tibor_please.no.email_kara...@.hotmail.nomail.com> wrote:
>> As a trainer, I know the (MS) SQL Server courses inside out. Here's my recommendation:
>> 2780, which is an admin class. Sure, you might know bits here and there already, but if you are
>> about to shift position, they (your managers) would want to invest a bit. Make sure you get the 5
>> days revision of the course (B rev), and preferably from a reputable instructor. Added value
>> differs
>> a lot. I have difficulties managing to teach this class for the specified time, while other say
>> there is way too much time allocated.
>> --
>> Tibor Karaszi, SQL Server
>> MVPhttp://www.karaszi.com/sqlserver/default.asphttp://sqlblog.com/blogs/tibor_karaszi
>> "Mike" <M...@.community.nospam.com> wrote in messagenews:OziQgz3rHHA.3500@.TK2MSFTNGP04.phx.gbl...
>> > Thanks, I'm going to be looking online this weekend for classes in my area.
>> > "Pawn" <TheRealP...@.gmail.com> wrote in message
>> >news:1181932262.511711.220810@.q66g2000hsg.googlegroups.com...
>> >>I was in the same boat. Microsoft has some really good training
>> >> classes and I'd highly recommend getting into one of those as soon as
>> >> you can. They'll cover a broad range of your day to day operations
>> >> like backups and security. Also, get familiar with some networking
>> >> knowledge as well. You're going to be walking the line between
>> >> hardware and software. But, the first thing is with only SQL Dev
>> >> experience I'd see what, if any, training classes you can get into. If
>> >> anything the book can be used for reference for TSQL statements.
>|||Obviously SQL Server has been designed & built by developers (c:
Regards,
Regards,
Greg Linwood
SQL Server MVP
http://blogs.sqlserver.org.au/blogs/greg_linwood
http://www.SQLBenchmarkPro.com
"Pawn" <TheRealPawn@.gmail.com> wrote in message
news:1181933280.917354.9000@.p77g2000hsh.googlegroups.com...
> Hey, not ALL developers are bad. Just the great majority. Coming out
> of the trenches yourself you probably get along well with them so when
> you see a performance problem they will most likely be very receptive
> to your suggestions on how to fix it. SQL Profiler and Performance
> Monitor have just become some of your best friends. Though they do add
> overhead to the server so use them sparingly.
> This site may help you figure out some more details about performance
> monitors:
> http://www.sql-server-performance.com/
> Here's a link on what your day-to-day's may include:
> http://www.databasedesign-resource.com/sql-server-dba.html
> On Jun 15, 2:33 pm, "Geoff N. Hiten" <SQLCrafts...@.gmail.com> wrote:
>> First and most importantly, you need to be able to put the system back
>> the
>> way it was yesterday, data and all. Fully document the system and make
>> sure
>> your recovery strategy is in place and tested.
>> Second, all developers are now your natural enemy. They write code to
>> destroy the data and performance. It is your job to limit the damage
>> they
>> can do. See requirement #1.
>> Performance monitoring and tuning must now be regular parts of your
>> routine.
>> Security just became your problem. You don't want to be the next
>> headline
>> on data lost or hacked.
>> There are lots more, but this should keep you up nights for the next few
>> months.
>> --
>> Geoff N. Hiten
>> Senior Database Administrator
>> Microsoft SQL Server MVP
>> "Mike" <M...@.community.nospam.com> wrote in message
>> news:OinW2i3rHHA.632@.TK2MSFTNGP03.phx.gbl...
>> > just to add I know how to create users in the database, SSIS packages,
>> > I
>> > guess its more on triggers, indexes, performance issues, replication,
>> > mirroring, etc, suff like that I guess is what i'm looking for.
>> > and other things a DBA does within this role.
>> > "Mike" <M...@.community.nospam.com> wrote in message
>> >news:%23G$Syd3rHHA.1168@.TK2MSFTNGP03.phx.gbl...
>> >> This is probably a wide open question but:
>> >> I'm coming from a developer role for the pass 12 years. I've created
>> >> everything from, components, web app, windows apps, mobile device
>> >> applications, etc. Now I'm getting ready to take over work on our
>> >> databases, Our DBA has left and I'm kind of stepping in to take on
>> >> that
>> >> role. So my question is, coming from developer background, what do I
>> >> need
>> >> to know beyond creating stored procedures and select statements to be
>> >> a
>> >> successful DBA? I know from in the pass in working with DBA's that
>> >> they
>> >> do more then just create stored procedures and database, what do I
>> >> need
>> >> to know such as, replication, mirroring, security, performance, etc.
>> >> where do I begin, is there anything out there to help me get an
>> >> understanding of a DBA role, or should I just 'fly by the seam of my
>> >> pants' on this one? (probably not a good idea, but willing to try it)
>> >> thanks for any help and or suggestions you may have to offer, (good
>> >> or
>> >> bad are accepted)
>
>|||This is very good advice - it often isn't clear to a developer moving into a
DBA role how important protecting the system, data & the company's uptime is
until they experience a failure. When disaster calls, some get lucky due to
their predecessors following good procedures but some new DBAs get fired for
not performing their #1 responsibility. I agree with Geoff - make sure you
fully understand, document & know how to restore your system in case you
need to. Also, make sure your employer knows you're spending time protecting
them & do your best to actually practice restoring your system (just as a
dev tests code, DBAs should test restoring systems).
Everything else is of secondary (although significant) importance.
Regards,
Regards,
Greg Linwood
SQL Server MVP
http://blogs.sqlserver.org.au/blogs/greg_linwood
http://www.SQLBenchmarkPro.com
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:OtZbfu3rHHA.1476@.TK2MSFTNGP06.phx.gbl...
> First and most importantly, you need to be able to put the system back the
> way it was yesterday, data and all. Fully document the system and make
> sure your recovery strategy is in place and tested.
> Second, all developers are now your natural enemy. They write code to
> destroy the data and performance. It is your job to limit the damage they
> can do. See requirement #1.
> Performance monitoring and tuning must now be regular parts of your
> routine.
> Security just became your problem. You don't want to be the next headline
> on data lost or hacked.
> There are lots more, but this should keep you up nights for the next few
> months.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
>
> "Mike" <Mike@.community.nospam.com> wrote in message
> news:OinW2i3rHHA.632@.TK2MSFTNGP03.phx.gbl...
>> just to add I know how to create users in the database, SSIS packages, I
>> guess its more on triggers, indexes, performance issues, replication,
>> mirroring, etc, suff like that I guess is what i'm looking for.
>> and other things a DBA does within this role.
>>
>> "Mike" <Mike@.community.nospam.com> wrote in message
>> news:%23G$Syd3rHHA.1168@.TK2MSFTNGP03.phx.gbl...
>> This is probably a wide open question but:
>> I'm coming from a developer role for the pass 12 years. I've created
>> everything from, components, web app, windows apps, mobile device
>> applications, etc. Now I'm getting ready to take over work on our
>> databases, Our DBA has left and I'm kind of stepping in to take on that
>> role. So my question is, coming from developer background, what do I
>> need to know beyond creating stored procedures and select statements to
>> be a successful DBA? I know from in the pass in working with DBA's that
>> they do more then just create stored procedures and database, what do I
>> need to know such as, replication, mirroring, security, performance,
>> etc. where do I begin, is there anything out there to help me get an
>> understanding of a DBA role, or should I just 'fly by the seam of my
>> pants' on this one? (probably not a good idea, but willing to try it)
>>
>> thanks for any help and or suggestions you may have to offer, (good or
>> bad are accepted)
>>
>>
>