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 |
|
poser
Posting Yak Master
124 Posts |
 Posted - 2011-09-08 : 08:21:38
|
| I've inherited a mess <sigh>We have SQL 2005 running on a SAN. They have a lot of disk space issues...I guess before when they were filling up log and data space, they just kept adding ndf files. Both the database and the logs are on the same drive 'K'. They are not set to auto grow and I think they have only backed up the log files and never truncated the logs and let it go back to the OS. I think they have made changes to their code so as not to need all the log space (maybe)...Is there a good way to get rid of all 8 of the ndf(s) (and all are on the same 'K' drive) and start over again with just the ldf to see what really is happening?We are having tons of I/O errors....Thanks /P |
|
|
russell
Pyro-ma-ni-yak
5072 Posts |
Posted - 2011-09-08 : 08:54:26
|
| Sounds like you need to review the backup schedules..ndfs are not log files.Don't truncate the log files.Turning off auto-grow is a crash waiting to happen.What are the specific i/o errors?Be very careful. From your questions, it seems you don't understand some of the basics here. Don't go around making drastic changes unless you know exactly what you're doing. We'll be glad to help, but you may need to bring in a consultant experienced in these issues. |
 |
|
|
manju3606
Yak Posting Veteran
78 Posts |
Posted - 2011-09-08 : 16:36:09
|
| Hi Poser,Ressell is right , and what kind of I/O errors... you havingManju |
|
|
|
Kristen
Test
22859 Posts |
Posted - 2011-09-08 : 17:20:41
|
| If you are having I/O errors suggest you do a DBCC CHECKDB at the earliest opportunity in case there are corruptions to the database. |
|
|
|
|
|
|
I/O issues