June 28, 2004 at 1:50 pm
June 28, 2004 at 1:58 pm
Some other threads:
http://www.sqlservercentral.com/forums/shwmessage.aspx?messageid=120949
http://www.sqlservercentral.com/forums/shwmessage.aspx?messageid=111280
http://www.sqlservercentral.com/columnists/chedgate/fragmentation101.asp
http://www.sqlservercentral.com/columnists/ckempster/mappingdatabasefileobjectsandfragmentation.asp
June 28, 2004 at 2:00 pm
I have found that defraging a drive is always a good idea. Keep in mind that SQL Databases are always open and are almost always written to in some way or another. I would look to have sql server not on when I did it. So your taking big time down time if you are defraging (is that two gs?) a large drive.
June 30, 2004 at 7:00 am
I have recently tried defragging a W2003 test server running SQL2K SP3a, while SQL was active and using the defrag tool supplied with W2003.
It worked.
Even so, I would not want to do this in production. The consequences if this did cause a problem are too great. I would always want to stop SQL Server while defragging in production.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply