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 |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2003-03-27 : 07:47:26
|
| Phil writes "I recently attented an MCDBA class and am feeling pretty smart. While I was gone to the class our server crashed like 6 times. I'm hoping one of you guys can clue me in as to why it's crashing. I learned about filegroups in the class I went to. I know that we have only 1 Primary filegroup for all the data, logfiles, etc. I came back thinking that if I put everything into different filegroups that would fix everything. The other part of this equation is that we are replacing our problem server with a new one. The new server will have RAID-10 on it. The network admin guys said that since we have RAID-10 that we don't need to worry about putting things into different filegroups. Is this correct?Also, I heard that I could lookup dumps or whatever on microsoft.com/technet. Has anybody else ever attempted this? In general, what is your guys experience in figuring out why a server crashes.Any input would be appreciated.Thanks,Phil" |
|
|
Page47
Master Smack Fu Yak Hacker
2878 Posts |
Posted - 2003-03-27 : 08:40:42
|
| Phil..Phil..Phil..the MCDBA...First, on the RAID. RAID-10 is a good choice for databases with a high write:read ratio. Congrats on that that setup. Most network admin guys will throw a RAID-5 at a transactional database and (wrongly) tell you it's the best way to go.On filegroups. What did you learn in your class were the benefits of multiple filegroups? I'd bet some of the 'advantages' bullet points are things that a RAID does not replace. Things like doing backups on the filegroup level and parallelizing disk I/O by being precise about index placement in filegroups. Review your MCDBA material for more.Finally, on the crashing. You should start by defining "crash". You need to isolate a OS vs. SQL Server problem. A hardware vs. software problem. Use Event Logs and SQL Server Logs to begin this process. You might want to work multi-laterally with your Network Admins to pinpoint the source of failure.Jay White{0} |
 |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-03-27 : 12:47:33
|
| It has been my experience that the server crashes usually are not related to SQL Server. But you will want to check the Event Log to determine what the problem. Things to look for is to check if it did a blue screen. If it did, then should have the error in there too. The error will not be understandable, but just type in the error number (is a hexadecimal string) into MS' knowledge base (support.microsoft.com) and you should get back some information. If it didn't blue screen, then what did it do? Did it just lock up? Or what? I am not sure why you thought that putting everything into filegroups would fix everything, especially since fixing everything refers to fixing the server from crashing. Anyway, if you provide some more information for us, then we might be able to help you out. Otherwise, work with your server admin and find the relevant knowledge base articles.Tara |
|
|
|
|
|
|
|
|
problem server