Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
cmoughan
Starting Member
2 Posts |
 Posted - 2004-10-21 : 15:29:48
|
| Hey Everyone,I know a total of zero about SQL. I was hired at a company as a Network Admin (I'm MCSE and BA Networking from PSU). I was given the task of DB maintenance. It's SQL 2000 on a Win2K server. There hasn't been ANY maintenance done on the DB in about...EVER! It suffers from extreme slowness at times and contain vital daily info for the company to run.What are some steps I can take:A) Immediately to help this suffering beastB) In the near future to help maintainC) Long term to make it easier for meI know there are no quick fixes, and from what I gather the Maintenance Wizard is garbage. But What can I do to get on the proper path to Shangri-La (sp?).Thanks for your help.Chris |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2004-10-21 : 16:31:10
|
| You can start with creating maintenance jobs using these that I wrote:http://weblogs.sqlteam.com/tarad/archive/2004/07/02/1705.aspxFor performance, well I'd run Performance Monitor to determine if you have hardware bottlenecks. I'd soak up all the info from www.sql-server-performance.com as well. Long term, they need to hire someone with SQL Server experience or send you to training.Tara |
 |
|
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
Posted - 2004-10-21 : 21:49:05
|
| i feel for you, that was exactly my dilemma when i first joined my current company.question, when you say db maintenance, will that be database administration or just server maintenance? being a network admin, you might encounter some conflict of interest if you'll engage in DBA work.on DBA side, suggestions:1. document mdf (data files) and ldf (log files) locations for each database2. perform HDD cleanup, backup those files that are not needed anymore3. determine HDD capacity for locations of mdf and ldf4. determine the amount of space needed to maintain your ldf at a reasonable size.5. create maintenance plan for backup and restore database, you may want to determine a) if you need point in time recovery per each database, critical level of database (if all database should have frequent backups), b)alerts for responding to log files reaching their limit (i prefer to allow the data files to grow dynamically instead of restricting them)this is just for starters, aside from the network jobs you'll be checking. also, you may want to buy a good book on sql administration if they can't send you to training.for your other questions, i suggest, deal with one task at a time...--------------------keeping it simple... |
|
|
|
Kristen
Test
22859 Posts |
Posted - 2004-10-22 : 01:41:01
|
| I would strongly recommend you get someone knowledgeable in for the day to help you make a plan, look at the database server, and probably to set up some quick-win routines - that may prevent the whole system falling flat on its face in a couple of days time!I'm self taught, but I've been doing it for a while, and I have a fair idea of where my knowledge runs out ... that said, we faced an issue, a short while ago, where one of the SQL system databases had grown to nearly 1 GB and the MS-provided process for clearing it down (once I managed to find out what that was!) would have taken weeks of continuous CPU usage - I kid you not!So that's why I think that, given your honest opinon of your current skills, and the reliance your company has on the data, that some sort of "expert" identify what needs doing, and in what order, would be a good idea.Kristen |
|
|
|
cmoughan
Starting Member
2 Posts |
Posted - 2004-10-22 : 09:52:25
|
| Thank you all so much for your replies. After some searching and poking around I have found that the DB is almost 5GB in size. It has been running for approx. 4 years and the server rarely gets rebooted. I am looking into some SQL classes for the future, but am currently looking for a professional to assist with this one. It will be tough, though. My boss is very paranoid about his data, and it will be a fight to get someone in here.Thank you all again very much. |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2004-10-22 : 12:25:28
|
| The SQL Server rarely getting rebooted is a good thing. You initially take a hit on performance when SQL Server is rebooted. We only reboot when whatever service pack or maintenance requires it or there is no other to fix a problem.Tara |
|
|
|
Kristen
Test
22859 Posts |
Posted - 2004-10-22 : 23:57:22
|
| Good Luck! Come back and ask some questions along the way ... it will be good to see how you are getting along, and as a case study of what sort of problems you encounter. "I was given the task of DB maintenance" is a pretty common cry for help around these parts!Kristen |
|
|
|
derrickleggett
Pointy Haired Yak DBA
4184 Posts |
Posted - 2004-10-23 : 13:47:14
|
My boss is very paranoid about his data, and it will be a fight to get someone in here. That's probably because he's an idiot and they'd fire him if they knew what he did.You might want to take a look at the SQL Server Operations Guide:http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/sqlops4.mspxMeanOldDBAderrickleggett@hotmail.comWhen life gives you a lemon, fire the DBA. |
|
|
|
|
|
|
|
|
clueless about SQL