May 4, 2007 at 7:06 am
Hi all, I started a new job at a firm recently as a developer with a few years of Access/VB programming experience under my belt. I am now branching out into SQL Server admin. As we're a small shop everyone wears multiple hats and I was given the admin hat to wear, (no one actively had this role in the past). In the past I've always had a DBA or someone similar do my backend database work when I was doing my projects so I consider myself a complete rookie when it comes to SQL server, (however, I am capable of doing basic stuff, creating databases, queries, making simple DTS packages, etc). I basically don't know where to start in my administration duties. I guess I'm just looking for some input on what kinds of things would you do/setup/implement if you were given an opportunity like this.
One glaring hole that I do recognise is that we have no formal disaster/ recovery plans in place. I'd like to start out by creating one but don't know how to begin. Any advice on how to go about setting one up? I'm just in the phase of compiling data on all our databases so I can get a feel for what's out there so at this point I really don't know how many databases there are or the size of them.
Thanks for the input!!!
May 7, 2007 at 4:35 am
There's a lot of places where you can find info on this subject.
Here's one as a starter:
http://sqljunkies.com/Article/F30B1E5F-F50F-40A8-96F2-476CEAD46C79.scuk
If you google on 'sql server disaster planning' you'll get several more links.
The subject is huge, and not easily covered in just one thread
/Kenneth
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply