June 8, 2005 at 8:18 pm
i just started a new job as a junior dba. the company i work for is growing really fast and looking for a senior dba, but until then: it's just me. i have a lot of academic experience, but not a lot of hands-on.
there isn't a lot of documentation, and no backup testing schedule or disaster recovery, so i'm working on getting that into place. there aren't any user complaints re: the db, so i'm thinking of setting up a general baseline performance monitor.
in the meantime, does anyone have real-world advice? mistakes that newbies tend to make? ways of reassuring or impressing my bosses? any don't-do-this or watch-out-for-that stories? ideas on covering my bases? your advice is appreciated!
June 8, 2005 at 8:38 pm
Naomi,
Good luck. Getting your recovery capability together is a good start. I don't want to overwhelm you with information right now, but do wish to share some thoughts.
* You will want to monitor growth and disk space.
* Try to get some standards in place as soon as possible. For example, file layouts, naming conventions, service accounts, Service Pack levels, etc. This will pay off down the road.
* Document your passwords.
* Establish an approach for creating new databases and for migrating code to production.
* Get a handle if you can on the business reasons for the databases.
* Start monitoring and metric gathering. Start simple unless you have some 3rd party tools to work with.
* Document your SQL Server Agent job schedules.
One of the wonderful things about being a DBA is that there is always more that can be done. This site is a wonderful resource for ideas. I'm one of those DBA's that even goes as far as to when and how the statistics are created. It is good to know when and what is happening to your databases.
"Keep Your Stick On the Ice" ..Red Green
June 9, 2005 at 2:15 am
There are quite a few useful threads here on the forum. So, if you have time you might want to browse them. See if this also helps: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsql2k/html/sql_id_com_admn2.asp
--
Frank Kalis
Microsoft SQL Server MVP
Webmaster: http://www.insidesql.org/blogs
My blog: http://www.insidesql.org/blogs/frankkalis/[/url]
June 10, 2005 at 10:14 am
Hello Naomie,
If you want you can also dowload and try the: Best Practice Analyzer from Microsoft.
It scans your server and gives you an interesting report. After that you can choose to apply or not the "best practice" thats lack on your environment.
You can find it at this URL: http://www.microsoft.com/downloads/details.aspx?FamilyId=B352EB1F-D3CA-44EE-893E-9E07339C1F22&displaylang=en
Regards,
Carl
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply