Any concerns about doing this? Never been done in year and half. Thanks.
make your question more clear ?
You have not Defragged Indexes in 1.5 years ?
or you have not defragged the physical Drive in 1.5 years?
Either way, I'd say..."OUCH"
you need to schedule a time to do this, yes.
Depending on the nature of the problem, this may require some down time.
Greg Jackson
PDX, Oregon
|||Ah, you're right. What I meant to ask was ok to defrag the physical drives.
Indexes and what not get degragged each night with backup. Thanks.
"pdxJaxon" wrote:
> make your question more clear ?
> You have not Defragged Indexes in 1.5 years ?
> or you have not defragged the physical Drive in 1.5 years?
> Either way, I'd say..."OUCH"
> you need to schedule a time to do this, yes.
> Depending on the nature of the problem, this may require some down time.
>
> Greg Jackson
> PDX, Oregon
>
>
|||You shouldn't need to defrag drives unless you use a lot of grow and shrink. Anyhow, do backup (for
safety), stop SQL Server and do the defrag.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"mb" <mb@.discussions.microsoft.com> wrote in message
news:D2A482D5-6657-42A2-86B4-030493EC1B8F@.microsoft.com...[vbcol=seagreen]
> Ah, you're right. What I meant to ask was ok to defrag the physical drives.
> Indexes and what not get degragged each night with backup. Thanks.
> "pdxJaxon" wrote:
Showing posts with label half. Show all posts
Showing posts with label half. Show all posts
Wednesday, March 28, 2012
Ok to degragment my SQL 2000 server?
Any concerns about doing this? Never been done in year and half. Thanks.make your question more clear ?
You have not Defragged Indexes in 1.5 years ?
or you have not defragged the physical Drive in 1.5 years?
Either way, I'd say..."OUCH"
you need to schedule a time to do this, yes.
Depending on the nature of the problem, this may require some down time.
Greg Jackson
PDX, Oregon|||Ah, you're right. What I meant to ask was ok to defrag the physical drives.
Indexes and what not get degragged each night with backup. Thanks.
"pdxJaxon" wrote:
> make your question more clear ?
> You have not Defragged Indexes in 1.5 years ?
> or you have not defragged the physical Drive in 1.5 years?
> Either way, I'd say..."OUCH"
> you need to schedule a time to do this, yes.
> Depending on the nature of the problem, this may require some down time.
>
> Greg Jackson
> PDX, Oregon
>
>|||You shouldn't need to defrag drives unless you use a lot of grow and shrink.
Anyhow, do backup (for
safety), stop SQL Server and do the defrag.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"mb" <mb@.discussions.microsoft.com> wrote in message
news:D2A482D5-6657-42A2-86B4-030493EC1B8F@.microsoft.com...[vbcol=seagreen]
> Ah, you're right. What I meant to ask was ok to defrag the physical drive
s.
> Indexes and what not get degragged each night with backup. Thanks.
> "pdxJaxon" wrote:
>sql
You have not Defragged Indexes in 1.5 years ?
or you have not defragged the physical Drive in 1.5 years?
Either way, I'd say..."OUCH"
you need to schedule a time to do this, yes.
Depending on the nature of the problem, this may require some down time.
Greg Jackson
PDX, Oregon|||Ah, you're right. What I meant to ask was ok to defrag the physical drives.
Indexes and what not get degragged each night with backup. Thanks.
"pdxJaxon" wrote:
> make your question more clear ?
> You have not Defragged Indexes in 1.5 years ?
> or you have not defragged the physical Drive in 1.5 years?
> Either way, I'd say..."OUCH"
> you need to schedule a time to do this, yes.
> Depending on the nature of the problem, this may require some down time.
>
> Greg Jackson
> PDX, Oregon
>
>|||You shouldn't need to defrag drives unless you use a lot of grow and shrink.
Anyhow, do backup (for
safety), stop SQL Server and do the defrag.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"mb" <mb@.discussions.microsoft.com> wrote in message
news:D2A482D5-6657-42A2-86B4-030493EC1B8F@.microsoft.com...[vbcol=seagreen]
> Ah, you're right. What I meant to ask was ok to defrag the physical drive
s.
> Indexes and what not get degragged each night with backup. Thanks.
> "pdxJaxon" wrote:
>sql
Ok to degragment my SQL 2000 server?
Any concerns about doing this? Never been done in year and half. Thanks.make your question more clear ?
You have not Defragged Indexes in 1.5 years ?
or you have not defragged the physical Drive in 1.5 years?
Either way, I'd say..."OUCH"
you need to schedule a time to do this, yes.
Depending on the nature of the problem, this may require some down time.
Greg Jackson
PDX, Oregon|||Ah, you're right. What I meant to ask was ok to defrag the physical drives.
Indexes and what not get degragged each night with backup. Thanks.
"pdxJaxon" wrote:
> make your question more clear ?
> You have not Defragged Indexes in 1.5 years ?
> or you have not defragged the physical Drive in 1.5 years?
> Either way, I'd say..."OUCH"
> you need to schedule a time to do this, yes.
> Depending on the nature of the problem, this may require some down time.
>
> Greg Jackson
> PDX, Oregon
>
>|||You shouldn't need to defrag drives unless you use a lot of grow and shrink. Anyhow, do backup (for
safety), stop SQL Server and do the defrag.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"mb" <mb@.discussions.microsoft.com> wrote in message
news:D2A482D5-6657-42A2-86B4-030493EC1B8F@.microsoft.com...
> Ah, you're right. What I meant to ask was ok to defrag the physical drives.
> Indexes and what not get degragged each night with backup. Thanks.
> "pdxJaxon" wrote:
>> make your question more clear ?
>> You have not Defragged Indexes in 1.5 years ?
>> or you have not defragged the physical Drive in 1.5 years?
>> Either way, I'd say..."OUCH"
>> you need to schedule a time to do this, yes.
>> Depending on the nature of the problem, this may require some down time.
>>
>> Greg Jackson
>> PDX, Oregon
>>
You have not Defragged Indexes in 1.5 years ?
or you have not defragged the physical Drive in 1.5 years?
Either way, I'd say..."OUCH"
you need to schedule a time to do this, yes.
Depending on the nature of the problem, this may require some down time.
Greg Jackson
PDX, Oregon|||Ah, you're right. What I meant to ask was ok to defrag the physical drives.
Indexes and what not get degragged each night with backup. Thanks.
"pdxJaxon" wrote:
> make your question more clear ?
> You have not Defragged Indexes in 1.5 years ?
> or you have not defragged the physical Drive in 1.5 years?
> Either way, I'd say..."OUCH"
> you need to schedule a time to do this, yes.
> Depending on the nature of the problem, this may require some down time.
>
> Greg Jackson
> PDX, Oregon
>
>|||You shouldn't need to defrag drives unless you use a lot of grow and shrink. Anyhow, do backup (for
safety), stop SQL Server and do the defrag.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"mb" <mb@.discussions.microsoft.com> wrote in message
news:D2A482D5-6657-42A2-86B4-030493EC1B8F@.microsoft.com...
> Ah, you're right. What I meant to ask was ok to defrag the physical drives.
> Indexes and what not get degragged each night with backup. Thanks.
> "pdxJaxon" wrote:
>> make your question more clear ?
>> You have not Defragged Indexes in 1.5 years ?
>> or you have not defragged the physical Drive in 1.5 years?
>> Either way, I'd say..."OUCH"
>> you need to schedule a time to do this, yes.
>> Depending on the nature of the problem, this may require some down time.
>>
>> Greg Jackson
>> PDX, Oregon
>>
Subscribe to:
Posts (Atom)