Msg 9002, Level 17, State 4, Line 2

I'm trying to clear some data from a SQL DB table, but i'm getting this
error:
I'm just running a Delete Query using Date Diff function. I read in some
web site that this maybe a problem with SQL Server Management Tools. I
appreciate any help to get around this and any suggestions would be great.
Msg 9002, Level 17, State 4, Line 2
The transaction log for database 'EventSentry' is full. To find out why
space in the log cannot be reused, see the log_reuse_wait_desc column in
sys.databases
Thanks for answering.Fialoa,
Your delete transaction is writting too many log records and filling it up.
If you want to be able to recover then you need to make the log bigger or
make your delete statement work on a smaller subset.
Chris
"fiaola" <fiaola@.mail.com> wrote in message
news:uLj2q0WUIHA.4768@.TK2MSFTNGP02.phx.gbl...
> I'm trying to clear some data from a SQL DB table, but i'm getting this
> error:
> I'm just running a Delete Query using Date Diff function. I read in some
> web site that this maybe a problem with SQL Server Management Tools. I
> appreciate any help to get around this and any suggestions would be great.
> Msg 9002, Level 17, State 4, Line 2
> The transaction log for database 'EventSentry' is full. To find out why
> space in the log cannot be reused, see the log_reuse_wait_desc column in
> sys.databases
> Thanks for answering.
>|||Hi fiaola
SQL Server has to log every data modification operation, every insert,
update and delete. If the log is full, nothing can be written to it and no
data modifications can be done. This has nothing to do with the tool you are
using.
Just do what the messages says. Look at the sys.databases view and tell us
what the log_reuse_wait_desc says. Also look at the recovery model
SELECT log_reuse_wait_desc, recovery_model_desc
FROM sys.databases
WHERE name = 'EventSentry'
HTH
Kalen Delaney, SQL Server MVP
www.InsideSQLServer.com
http://blog.kalendelaney.com
"fiaola" <fiaola@.mail.com> wrote in message
news:uLj2q0WUIHA.4768@.TK2MSFTNGP02.phx.gbl...
> I'm trying to clear some data from a SQL DB table, but i'm getting this
> error:
> I'm just running a Delete Query using Date Diff function. I read in some
> web site that this maybe a problem with SQL Server Management Tools. I
> appreciate any help to get around this and any suggestions would be great.
> Msg 9002, Level 17, State 4, Line 2
> The transaction log for database 'EventSentry' is full. To find out why
> space in the log cannot be reused, see the log_reuse_wait_desc column in
> sys.databases
> Thanks for answering.
>|||Thanks for the quick reply, here are the results.
Log_Reuse_Wait_Desc = NOTHING
Recovery_Model_Desc = SIMPLE
"Kalen Delaney" <replies@.public_newsgroups.com> wrote in message
news:eMohs$WUIHA.4768@.TK2MSFTNGP02.phx.gbl...
> Hi fiaola
> SQL Server has to log every data modification operation, every insert,
> update and delete. If the log is full, nothing can be written to it and no
> data modifications can be done. This has nothing to do with the tool you
> are using.
> Just do what the messages says. Look at the sys.databases view and tell us
> what the log_reuse_wait_desc says. Also look at the recovery model
> SELECT log_reuse_wait_desc, recovery_model_desc
> FROM sys.databases
> WHERE name = 'EventSentry'
>
> --
> HTH
> Kalen Delaney, SQL Server MVP
> www.InsideSQLServer.com
> http://blog.kalendelaney.com
>
> "fiaola" <fiaola@.mail.com> wrote in message
> news:uLj2q0WUIHA.4768@.TK2MSFTNGP02.phx.gbl...
>> I'm trying to clear some data from a SQL DB table, but i'm getting this
>> error:
>> I'm just running a Delete Query using Date Diff function. I read in some
>> web site that this maybe a problem with SQL Server Management Tools. I
>> appreciate any help to get around this and any suggestions would be
>> great.
>> Msg 9002, Level 17, State 4, Line 2
>> The transaction log for database 'EventSentry' is full. To find out why
>> space in the log cannot be reused, see the log_reuse_wait_desc column in
>> sys.databases
>> Thanks for answering.
>>
>|||It might just be that your log is not big enough for the operation you were
doing.
How big is your log file, and is it set to autogrow?
You can get the information in the sys.files view in the database that is
having the problems.
--
HTH
Kalen Delaney, SQL Server MVP
www.InsideSQLServer.com
http://blog.kalendelaney.com
"fiaola" <fiaola@.mail.com> wrote in message
news:uH1ss$YUIHA.5816@.TK2MSFTNGP06.phx.gbl...
> Thanks for the quick reply, here are the results.
> Log_Reuse_Wait_Desc = NOTHING
> Recovery_Model_Desc = SIMPLE
> "Kalen Delaney" <replies@.public_newsgroups.com> wrote in message
> news:eMohs$WUIHA.4768@.TK2MSFTNGP02.phx.gbl...
>> Hi fiaola
>> SQL Server has to log every data modification operation, every insert,
>> update and delete. If the log is full, nothing can be written to it and
>> no data modifications can be done. This has nothing to do with the tool
>> you are using.
>> Just do what the messages says. Look at the sys.databases view and tell
>> us what the log_reuse_wait_desc says. Also look at the recovery model
>> SELECT log_reuse_wait_desc, recovery_model_desc
>> FROM sys.databases
>> WHERE name = 'EventSentry'
>>
>> --
>> HTH
>> Kalen Delaney, SQL Server MVP
>> www.InsideSQLServer.com
>> http://blog.kalendelaney.com
>>
>> "fiaola" <fiaola@.mail.com> wrote in message
>> news:uLj2q0WUIHA.4768@.TK2MSFTNGP02.phx.gbl...
>> I'm trying to clear some data from a SQL DB table, but i'm getting this
>> error:
>> I'm just running a Delete Query using Date Diff function. I read in
>> some web site that this maybe a problem with SQL Server Management
>> Tools. I appreciate any help to get around this and any suggestions
>> would be great.
>> Msg 9002, Level 17, State 4, Line 2
>> The transaction log for database 'EventSentry' is full. To find out why
>> space in the log cannot be reused, see the log_reuse_wait_desc column in
>> sys.databases
>> Thanks for answering.
>>
>>
>|||Modify your delete to do it in batches. Pick date ranges that will only
delete 1-5% of the table at once max for each range and then you will
probably be ok.
--
Kevin G. Boles
Indicium Resources, Inc.
SQL Server MVP
kgboles a earthlink dt net
"fiaola" <fiaola@.mail.com> wrote in message
news:uLj2q0WUIHA.4768@.TK2MSFTNGP02.phx.gbl...
> I'm trying to clear some data from a SQL DB table, but i'm getting this
> error:
> I'm just running a Delete Query using Date Diff function. I read in some
> web site that this maybe a problem with SQL Server Management Tools. I
> appreciate any help to get around this and any suggestions would be great.
> Msg 9002, Level 17, State 4, Line 2
> The transaction log for database 'EventSentry' is full. To find out why
> space in the log cannot be reused, see the log_reuse_wait_desc column in
> sys.databases
> Thanks for answering.
>|||But we still don't know how big the log is. I've seen logs that are set at
the default 1 MB with no autogrow.
--
HTH
Kalen Delaney, SQL Server MVP
www.InsideSQLServer.com
http://blog.kalendelaney.com
"TheSQLGuru" <kgboles@.earthlink.net> wrote in message
news:13o71gecmi9nmfb@.corp.supernews.com...
> Modify your delete to do it in batches. Pick date ranges that will only
> delete 1-5% of the table at once max for each range and then you will
> probably be ok.
> --
> Kevin G. Boles
> Indicium Resources, Inc.
> SQL Server MVP
> kgboles a earthlink dt net
>
> "fiaola" <fiaola@.mail.com> wrote in message
> news:uLj2q0WUIHA.4768@.TK2MSFTNGP02.phx.gbl...
>> I'm trying to clear some data from a SQL DB table, but i'm getting this
>> error:
>> I'm just running a Delete Query using Date Diff function. I read in some
>> web site that this maybe a problem with SQL Server Management Tools. I
>> appreciate any help to get around this and any suggestions would be
>> great.
>> Msg 9002, Level 17, State 4, Line 2
>> The transaction log for database 'EventSentry' is full. To find out why
>> space in the log cannot be reused, see the log_reuse_wait_desc column in
>> sys.databases
>> Thanks for answering.
>>
>|||Problem fixed. Yes, i had to change the query to process less data and i
have set my logs to Autogrow for any future problems.
Thanks for your help. This is a GREAT news group with fast response.
"Kalen Delaney" <replies@.public_newsgroups.com> wrote in message
news:u3AgCjgUIHA.4584@.TK2MSFTNGP03.phx.gbl...
> But we still don't know how big the log is. I've seen logs that are set at
> the default 1 MB with no autogrow.
> --
> HTH
> Kalen Delaney, SQL Server MVP
> www.InsideSQLServer.com
> http://blog.kalendelaney.com
>
> "TheSQLGuru" <kgboles@.earthlink.net> wrote in message
> news:13o71gecmi9nmfb@.corp.supernews.com...
>> Modify your delete to do it in batches. Pick date ranges that will only
>> delete 1-5% of the table at once max for each range and then you will
>> probably be ok.
>> --
>> Kevin G. Boles
>> Indicium Resources, Inc.
>> SQL Server MVP
>> kgboles a earthlink dt net
>>
>> "fiaola" <fiaola@.mail.com> wrote in message
>> news:uLj2q0WUIHA.4768@.TK2MSFTNGP02.phx.gbl...
>> I'm trying to clear some data from a SQL DB table, but i'm getting this
>> error:
>> I'm just running a Delete Query using Date Diff function. I read in
>> some web site that this maybe a problem with SQL Server Management
>> Tools. I appreciate any help to get around this and any suggestions
>> would be great.
>> Msg 9002, Level 17, State 4, Line 2
>> The transaction log for database 'EventSentry' is full. To find out why
>> space in the log cannot be reused, see the log_reuse_wait_desc column in
>> sys.databases
>> Thanks for answering.
>>
>>
>|||Good point. I haven't seen tlogs set with no autogrow that I recall.
Almost every client I have been at still has the defaults for data/log size
and growths (2MB and 1MB growth for data and 1MB and 10% growth for tlog,
IIRC). Makes me look good when I have them defrag the hard drive and pick
up a big perf gain. :-)
--
Kevin G. Boles
Indicium Resources, Inc.
SQL Server MVP
kgboles a earthlink dt net
"Kalen Delaney" <replies@.public_newsgroups.com> wrote in message
news:u3AgCjgUIHA.4584@.TK2MSFTNGP03.phx.gbl...
> But we still don't know how big the log is. I've seen logs that are set at
> the default 1 MB with no autogrow.
> --
> HTH
> Kalen Delaney, SQL Server MVP
> www.InsideSQLServer.com
> http://blog.kalendelaney.com
>
> "TheSQLGuru" <kgboles@.earthlink.net> wrote in message
> news:13o71gecmi9nmfb@.corp.supernews.com...
>> Modify your delete to do it in batches. Pick date ranges that will only
>> delete 1-5% of the table at once max for each range and then you will
>> probably be ok.
>> --
>> Kevin G. Boles
>> Indicium Resources, Inc.
>> SQL Server MVP
>> kgboles a earthlink dt net
>>
>> "fiaola" <fiaola@.mail.com> wrote in message
>> news:uLj2q0WUIHA.4768@.TK2MSFTNGP02.phx.gbl...
>> I'm trying to clear some data from a SQL DB table, but i'm getting this
>> error:
>> I'm just running a Delete Query using Date Diff function. I read in
>> some web site that this maybe a problem with SQL Server Management
>> Tools. I appreciate any help to get around this and any suggestions
>> would be great.
>> Msg 9002, Level 17, State 4, Line 2
>> The transaction log for database 'EventSentry' is full. To find out why
>> space in the log cannot be reused, see the log_reuse_wait_desc column in
>> sys.databases
>> Thanks for answering.
>>
>>
>|||You're welcome. I'm glad our suggestions helped.
--
HTH
Kalen Delaney, SQL Server MVP
www.InsideSQLServer.com
http://blog.kalendelaney.com
"fiaola" <fiaola@.mail.com> wrote in message
news:ubRniqiUIHA.536@.TK2MSFTNGP06.phx.gbl...
> Problem fixed. Yes, i had to change the query to process less data and i
> have set my logs to Autogrow for any future problems.
> Thanks for your help. This is a GREAT news group with fast response.
> "Kalen Delaney" <replies@.public_newsgroups.com> wrote in message
> news:u3AgCjgUIHA.4584@.TK2MSFTNGP03.phx.gbl...
>> But we still don't know how big the log is. I've seen logs that are set
>> at the default 1 MB with no autogrow.
>> --
>> HTH
>> Kalen Delaney, SQL Server MVP
>> www.InsideSQLServer.com
>> http://blog.kalendelaney.com
>>
>> "TheSQLGuru" <kgboles@.earthlink.net> wrote in message
>> news:13o71gecmi9nmfb@.corp.supernews.com...
>> Modify your delete to do it in batches. Pick date ranges that will only
>> delete 1-5% of the table at once max for each range and then you will
>> probably be ok.
>> --
>> Kevin G. Boles
>> Indicium Resources, Inc.
>> SQL Server MVP
>> kgboles a earthlink dt net
>>
>> "fiaola" <fiaola@.mail.com> wrote in message
>> news:uLj2q0WUIHA.4768@.TK2MSFTNGP02.phx.gbl...
>> I'm trying to clear some data from a SQL DB table, but i'm getting this
>> error:
>> I'm just running a Delete Query using Date Diff function. I read in
>> some web site that this maybe a problem with SQL Server Management
>> Tools. I appreciate any help to get around this and any suggestions
>> would be great.
>> Msg 9002, Level 17, State 4, Line 2
>> The transaction log for database 'EventSentry' is full. To find out why
>> space in the log cannot be reused, see the log_reuse_wait_desc column
>> in sys.databases
>> Thanks for answering.
>>
>>
>>
>|||Kevin,
We also try and size our data and log files with limited growth. I have seen
problems with an unlimited log and percent full log alerts.
How much improvement would a disk defrag give you on todays raided disks?
Thanks
Chris
"TheSQLGuru" <kgboles@.earthlink.net> wrote in message
news:13o7ttr3dli55fd@.corp.supernews.com...
> Good point. I haven't seen tlogs set with no autogrow that I recall.
> Almost every client I have been at still has the defaults for data/log
> size and growths (2MB and 1MB growth for data and 1MB and 10% growth for
> tlog, IIRC). Makes me look good when I have them defrag the hard drive
> and pick up a big perf gain. :-)
> --
> Kevin G. Boles
> Indicium Resources, Inc.
> SQL Server MVP
> kgboles a earthlink dt net
>
> "Kalen Delaney" <replies@.public_newsgroups.com> wrote in message
> news:u3AgCjgUIHA.4584@.TK2MSFTNGP03.phx.gbl...
>> But we still don't know how big the log is. I've seen logs that are set
>> at the default 1 MB with no autogrow.
>> --
>> HTH
>> Kalen Delaney, SQL Server MVP
>> www.InsideSQLServer.com
>> http://blog.kalendelaney.com
>>
>> "TheSQLGuru" <kgboles@.earthlink.net> wrote in message
>> news:13o71gecmi9nmfb@.corp.supernews.com...
>> Modify your delete to do it in batches. Pick date ranges that will only
>> delete 1-5% of the table at once max for each range and then you will
>> probably be ok.
>> --
>> Kevin G. Boles
>> Indicium Resources, Inc.
>> SQL Server MVP
>> kgboles a earthlink dt net
>>
>> "fiaola" <fiaola@.mail.com> wrote in message
>> news:uLj2q0WUIHA.4768@.TK2MSFTNGP02.phx.gbl...
>> I'm trying to clear some data from a SQL DB table, but i'm getting this
>> error:
>> I'm just running a Delete Query using Date Diff function. I read in
>> some web site that this maybe a problem with SQL Server Management
>> Tools. I appreciate any help to get around this and any suggestions
>> would be great.
>> Msg 9002, Level 17, State 4, Line 2
>> The transaction log for database 'EventSentry' is full. To find out why
>> space in the log cannot be reused, see the log_reuse_wait_desc column
>> in sys.databases
>> Thanks for answering.
>>
>>
>>
>|||Limiting your log size is fine, but you should also make sure you have a
good idea of how big it needs to be and then add a generous percentage extra
before setting the upper limit.
--
HTH
Kalen Delaney, SQL Server MVP
www.InsideSQLServer.com
http://blog.kalendelaney.com
"Chris Wood" <anonymous@.microsoft.com> wrote in message
news:u0Spi6uUIHA.4768@.TK2MSFTNGP02.phx.gbl...
> Kevin,
> We also try and size our data and log files with limited growth. I have
> seen problems with an unlimited log and percent full log alerts.
> How much improvement would a disk defrag give you on todays raided disks?
> Thanks
> Chris
> "TheSQLGuru" <kgboles@.earthlink.net> wrote in message
> news:13o7ttr3dli55fd@.corp.supernews.com...
>> Good point. I haven't seen tlogs set with no autogrow that I recall.
>> Almost every client I have been at still has the defaults for data/log
>> size and growths (2MB and 1MB growth for data and 1MB and 10% growth for
>> tlog, IIRC). Makes me look good when I have them defrag the hard drive
>> and pick up a big perf gain. :-)
>> --
>> Kevin G. Boles
>> Indicium Resources, Inc.
>> SQL Server MVP
>> kgboles a earthlink dt net
>>
>> "Kalen Delaney" <replies@.public_newsgroups.com> wrote in message
>> news:u3AgCjgUIHA.4584@.TK2MSFTNGP03.phx.gbl...
>> But we still don't know how big the log is. I've seen logs that are set
>> at the default 1 MB with no autogrow.
>> --
>> HTH
>> Kalen Delaney, SQL Server MVP
>> www.InsideSQLServer.com
>> http://blog.kalendelaney.com
>>
>> "TheSQLGuru" <kgboles@.earthlink.net> wrote in message
>> news:13o71gecmi9nmfb@.corp.supernews.com...
>> Modify your delete to do it in batches. Pick date ranges that will
>> only delete 1-5% of the table at once max for each range and then you
>> will probably be ok.
>> --
>> Kevin G. Boles
>> Indicium Resources, Inc.
>> SQL Server MVP
>> kgboles a earthlink dt net
>>
>> "fiaola" <fiaola@.mail.com> wrote in message
>> news:uLj2q0WUIHA.4768@.TK2MSFTNGP02.phx.gbl...
>> I'm trying to clear some data from a SQL DB table, but i'm getting
>> this error:
>> I'm just running a Delete Query using Date Diff function. I read in
>> some web site that this maybe a problem with SQL Server Management
>> Tools. I appreciate any help to get around this and any suggestions
>> would be great.
>> Msg 9002, Level 17, State 4, Line 2
>> The transaction log for database 'EventSentry' is full. To find out
>> why space in the log cannot be reused, see the log_reuse_wait_desc
>> column in sys.databases
>> Thanks for answering.
>>
>>
>>
>>
>|||Kalen,
We do that as best we can. We have alerts fired if the data file expands and
then we would look at the log size too. We also would get messages if the
log does get full.
My question is to see how much improvement we might get by defragging.
Thanks
Chris
"Kalen Delaney" <replies@.public_newsgroups.com> wrote in message
news:OAAg9h1UIHA.2268@.TK2MSFTNGP02.phx.gbl...
> Limiting your log size is fine, but you should also make sure you have a
> good idea of how big it needs to be and then add a generous percentage
> extra before setting the upper limit.
> --
> HTH
> Kalen Delaney, SQL Server MVP
> www.InsideSQLServer.com
> http://blog.kalendelaney.com
>
> "Chris Wood" <anonymous@.microsoft.com> wrote in message
> news:u0Spi6uUIHA.4768@.TK2MSFTNGP02.phx.gbl...
>> Kevin,
>> We also try and size our data and log files with limited growth. I have
>> seen problems with an unlimited log and percent full log alerts.
>> How much improvement would a disk defrag give you on todays raided disks?
>> Thanks
>> Chris
>> "TheSQLGuru" <kgboles@.earthlink.net> wrote in message
>> news:13o7ttr3dli55fd@.corp.supernews.com...
>> Good point. I haven't seen tlogs set with no autogrow that I recall.
>> Almost every client I have been at still has the defaults for data/log
>> size and growths (2MB and 1MB growth for data and 1MB and 10% growth for
>> tlog, IIRC). Makes me look good when I have them defrag the hard drive
>> and pick up a big perf gain. :-)
>> --
>> Kevin G. Boles
>> Indicium Resources, Inc.
>> SQL Server MVP
>> kgboles a earthlink dt net
>>
>> "Kalen Delaney" <replies@.public_newsgroups.com> wrote in message
>> news:u3AgCjgUIHA.4584@.TK2MSFTNGP03.phx.gbl...
>> But we still don't know how big the log is. I've seen logs that are set
>> at the default 1 MB with no autogrow.
>> --
>> HTH
>> Kalen Delaney, SQL Server MVP
>> www.InsideSQLServer.com
>> http://blog.kalendelaney.com
>>
>> "TheSQLGuru" <kgboles@.earthlink.net> wrote in message
>> news:13o71gecmi9nmfb@.corp.supernews.com...
>> Modify your delete to do it in batches. Pick date ranges that will
>> only delete 1-5% of the table at once max for each range and then you
>> will probably be ok.
>> --
>> Kevin G. Boles
>> Indicium Resources, Inc.
>> SQL Server MVP
>> kgboles a earthlink dt net
>>
>> "fiaola" <fiaola@.mail.com> wrote in message
>> news:uLj2q0WUIHA.4768@.TK2MSFTNGP02.phx.gbl...
>> I'm trying to clear some data from a SQL DB table, but i'm getting
>> this error:
>> I'm just running a Delete Query using Date Diff function. I read in
>> some web site that this maybe a problem with SQL Server Management
>> Tools. I appreciate any help to get around this and any suggestions
>> would be great.
>> Msg 9002, Level 17, State 4, Line 2
>> The transaction log for database 'EventSentry' is full. To find out
>> why space in the log cannot be reused, see the log_reuse_wait_desc
>> column in sys.databases
>> Thanks for answering.
>>
>>
>>
>>
>>
>|||I had a client with 300K+ file fragments when I arrived. 18% throughput
improvement from OS file defrag operation. It was on a small RAID10 set (6
drives IIRC).
--
Kevin G. Boles
Indicium Resources, Inc.
SQL Server MVP
kgboles a earthlink dt net
"Chris Wood" <anonymous@.microsoft.com> wrote in message
news:u0Spi6uUIHA.4768@.TK2MSFTNGP02.phx.gbl...
> Kevin,
> We also try and size our data and log files with limited growth. I have
> seen problems with an unlimited log and percent full log alerts.
> How much improvement would a disk defrag give you on todays raided disks?
> Thanks
> Chris
> "TheSQLGuru" <kgboles@.earthlink.net> wrote in message
> news:13o7ttr3dli55fd@.corp.supernews.com...
>> Good point. I haven't seen tlogs set with no autogrow that I recall.
>> Almost every client I have been at still has the defaults for data/log
>> size and growths (2MB and 1MB growth for data and 1MB and 10% growth for
>> tlog, IIRC). Makes me look good when I have them defrag the hard drive
>> and pick up a big perf gain. :-)
>> --
>> Kevin G. Boles
>> Indicium Resources, Inc.
>> SQL Server MVP
>> kgboles a earthlink dt net
>>
>> "Kalen Delaney" <replies@.public_newsgroups.com> wrote in message
>> news:u3AgCjgUIHA.4584@.TK2MSFTNGP03.phx.gbl...
>> But we still don't know how big the log is. I've seen logs that are set
>> at the default 1 MB with no autogrow.
>> --
>> HTH
>> Kalen Delaney, SQL Server MVP
>> www.InsideSQLServer.com
>> http://blog.kalendelaney.com
>>
>> "TheSQLGuru" <kgboles@.earthlink.net> wrote in message
>> news:13o71gecmi9nmfb@.corp.supernews.com...
>> Modify your delete to do it in batches. Pick date ranges that will
>> only delete 1-5% of the table at once max for each range and then you
>> will probably be ok.
>> --
>> Kevin G. Boles
>> Indicium Resources, Inc.
>> SQL Server MVP
>> kgboles a earthlink dt net
>>
>> "fiaola" <fiaola@.mail.com> wrote in message
>> news:uLj2q0WUIHA.4768@.TK2MSFTNGP02.phx.gbl...
>> I'm trying to clear some data from a SQL DB table, but i'm getting
>> this error:
>> I'm just running a Delete Query using Date Diff function. I read in
>> some web site that this maybe a problem with SQL Server Management
>> Tools. I appreciate any help to get around this and any suggestions
>> would be great.
>> Msg 9002, Level 17, State 4, Line 2
>> The transaction log for database 'EventSentry' is full. To find out
>> why space in the log cannot be reused, see the log_reuse_wait_desc
>> column in sys.databases
>> Thanks for answering.
>>
>>
>>
>>
>|||kevin,
What can we use to see how many file fragments there are? Running W2K3 SP2.
Thanks
Chris
"TheSQLGuru" <kgboles@.earthlink.net> wrote in message
news:13od5m2iv7ec365@.corp.supernews.com...
>I had a client with 300K+ file fragments when I arrived. 18% throughput
>improvement from OS file defrag operation. It was on a small RAID10 set (6
>drives IIRC).
> --
> Kevin G. Boles
> Indicium Resources, Inc.
> SQL Server MVP
> kgboles a earthlink dt net
>
> "Chris Wood" <anonymous@.microsoft.com> wrote in message
> news:u0Spi6uUIHA.4768@.TK2MSFTNGP02.phx.gbl...
>> Kevin,
>> We also try and size our data and log files with limited growth. I have
>> seen problems with an unlimited log and percent full log alerts.
>> How much improvement would a disk defrag give you on todays raided disks?
>> Thanks
>> Chris
>> "TheSQLGuru" <kgboles@.earthlink.net> wrote in message
>> news:13o7ttr3dli55fd@.corp.supernews.com...
>> Good point. I haven't seen tlogs set with no autogrow that I recall.
>> Almost every client I have been at still has the defaults for data/log
>> size and growths (2MB and 1MB growth for data and 1MB and 10% growth for
>> tlog, IIRC). Makes me look good when I have them defrag the hard drive
>> and pick up a big perf gain. :-)
>> --
>> Kevin G. Boles
>> Indicium Resources, Inc.
>> SQL Server MVP
>> kgboles a earthlink dt net
>>
>> "Kalen Delaney" <replies@.public_newsgroups.com> wrote in message
>> news:u3AgCjgUIHA.4584@.TK2MSFTNGP03.phx.gbl...
>> But we still don't know how big the log is. I've seen logs that are set
>> at the default 1 MB with no autogrow.
>> --
>> HTH
>> Kalen Delaney, SQL Server MVP
>> www.InsideSQLServer.com
>> http://blog.kalendelaney.com
>>
>> "TheSQLGuru" <kgboles@.earthlink.net> wrote in message
>> news:13o71gecmi9nmfb@.corp.supernews.com...
>> Modify your delete to do it in batches. Pick date ranges that will
>> only delete 1-5% of the table at once max for each range and then you
>> will probably be ok.
>> --
>> Kevin G. Boles
>> Indicium Resources, Inc.
>> SQL Server MVP
>> kgboles a earthlink dt net
>>
>> "fiaola" <fiaola@.mail.com> wrote in message
>> news:uLj2q0WUIHA.4768@.TK2MSFTNGP02.phx.gbl...
>> I'm trying to clear some data from a SQL DB table, but i'm getting
>> this error:
>> I'm just running a Delete Query using Date Diff function. I read in
>> some web site that this maybe a problem with SQL Server Management
>> Tools. I appreciate any help to get around this and any suggestions
>> would be great.
>> Msg 9002, Level 17, State 4, Line 2
>> The transaction log for database 'EventSentry' is full. To find out
>> why space in the log cannot be reused, see the log_reuse_wait_desc
>> column in sys.databases
>> Thanks for answering.
>>
>>
>>
>>
>>
>|||Hi Chris
Actually my comment was primarily directly at the OP. You've been around
long enough that I'm sure you've figured out most of the important stuff.
:-)
--
HTH
Kalen Delaney, SQL Server MVP
www.InsideSQLServer.com
http://blog.kalendelaney.com
"Chris Wood" <anonymous@.microsoft.com> wrote in message
news:O9J8RU7UIHA.5264@.TK2MSFTNGP02.phx.gbl...
> Kalen,
> We do that as best we can. We have alerts fired if the data file expands
> and then we would look at the log size too. We also would get messages if
> the log does get full.
> My question is to see how much improvement we might get by defragging.
> Thanks
> Chris
> "Kalen Delaney" <replies@.public_newsgroups.com> wrote in message
> news:OAAg9h1UIHA.2268@.TK2MSFTNGP02.phx.gbl...
>> Limiting your log size is fine, but you should also make sure you have a
>> good idea of how big it needs to be and then add a generous percentage
>> extra before setting the upper limit.
>> --
>> HTH
>> Kalen Delaney, SQL Server MVP
>> www.InsideSQLServer.com
>> http://blog.kalendelaney.com
>>
>> "Chris Wood" <anonymous@.microsoft.com> wrote in message
>> news:u0Spi6uUIHA.4768@.TK2MSFTNGP02.phx.gbl...
>> Kevin,
>> We also try and size our data and log files with limited growth. I have
>> seen problems with an unlimited log and percent full log alerts.
>> How much improvement would a disk defrag give you on todays raided
>> disks?
>> Thanks
>> Chris
>> "TheSQLGuru" <kgboles@.earthlink.net> wrote in message
>> news:13o7ttr3dli55fd@.corp.supernews.com...
>> Good point. I haven't seen tlogs set with no autogrow that I recall.
>> Almost every client I have been at still has the defaults for data/log
>> size and growths (2MB and 1MB growth for data and 1MB and 10% growth
>> for tlog, IIRC). Makes me look good when I have them defrag the hard
>> drive and pick up a big perf gain. :-)
>> --
>> Kevin G. Boles
>> Indicium Resources, Inc.
>> SQL Server MVP
>> kgboles a earthlink dt net
>>
>> "Kalen Delaney" <replies@.public_newsgroups.com> wrote in message
>> news:u3AgCjgUIHA.4584@.TK2MSFTNGP03.phx.gbl...
>> But we still don't know how big the log is. I've seen logs that are
>> set at the default 1 MB with no autogrow.
>> --
>> HTH
>> Kalen Delaney, SQL Server MVP
>> www.InsideSQLServer.com
>> http://blog.kalendelaney.com
>>
>> "TheSQLGuru" <kgboles@.earthlink.net> wrote in message
>> news:13o71gecmi9nmfb@.corp.supernews.com...
>> Modify your delete to do it in batches. Pick date ranges that will
>> only delete 1-5% of the table at once max for each range and then you
>> will probably be ok.
>> --
>> Kevin G. Boles
>> Indicium Resources, Inc.
>> SQL Server MVP
>> kgboles a earthlink dt net
>>
>> "fiaola" <fiaola@.mail.com> wrote in message
>> news:uLj2q0WUIHA.4768@.TK2MSFTNGP02.phx.gbl...
>>> I'm trying to clear some data from a SQL DB table, but i'm getting
>>> this error:
>>> I'm just running a Delete Query using Date Diff function. I read in
>>> some web site that this maybe a problem with SQL Server Management
>>> Tools. I appreciate any help to get around this and any suggestions
>>> would be great.
>>> Msg 9002, Level 17, State 4, Line 2
>>>
>>> The transaction log for database 'EventSentry' is full. To find out
>>> why space in the log cannot be reused, see the log_reuse_wait_desc
>>> column in sys.databases
>>>
>>> Thanks for answering.
>>>
>>>
>>
>>
>>
>>
>>
>|||I would recommend diskkeeper. There are many others from symantec,
perfectdisk (raxco maybe?), mcaffee probably has one, one built into windows
(downgraded version of diskkeeper IIRC).
--
Kevin G. Boles
Indicium Resources, Inc.
SQL Server MVP
kgboles a earthlink dt net
"Chris Wood" <anonymous@.microsoft.com> wrote in message
news:e6$B%23Y9UIHA.4448@.TK2MSFTNGP03.phx.gbl...
> kevin,
> What can we use to see how many file fragments there are? Running W2K3
> SP2.
> Thanks
> Chris
> "TheSQLGuru" <kgboles@.earthlink.net> wrote in message
> news:13od5m2iv7ec365@.corp.supernews.com...
>>I had a client with 300K+ file fragments when I arrived. 18% throughput
>>improvement from OS file defrag operation. It was on a small RAID10 set
>>(6 drives IIRC).
>> --
>> Kevin G. Boles
>> Indicium Resources, Inc.
>> SQL Server MVP
>> kgboles a earthlink dt net
>>
>> "Chris Wood" <anonymous@.microsoft.com> wrote in message
>> news:u0Spi6uUIHA.4768@.TK2MSFTNGP02.phx.gbl...
>> Kevin,
>> We also try and size our data and log files with limited growth. I have
>> seen problems with an unlimited log and percent full log alerts.
>> How much improvement would a disk defrag give you on todays raided
>> disks?
>> Thanks
>> Chris
>> "TheSQLGuru" <kgboles@.earthlink.net> wrote in message
>> news:13o7ttr3dli55fd@.corp.supernews.com...
>> Good point. I haven't seen tlogs set with no autogrow that I recall.
>> Almost every client I have been at still has the defaults for data/log
>> size and growths (2MB and 1MB growth for data and 1MB and 10% growth
>> for tlog, IIRC). Makes me look good when I have them defrag the hard
>> drive and pick up a big perf gain. :-)
>> --
>> Kevin G. Boles
>> Indicium Resources, Inc.
>> SQL Server MVP
>> kgboles a earthlink dt net
>>
>> "Kalen Delaney" <replies@.public_newsgroups.com> wrote in message
>> news:u3AgCjgUIHA.4584@.TK2MSFTNGP03.phx.gbl...
>> But we still don't know how big the log is. I've seen logs that are
>> set at the default 1 MB with no autogrow.
>> --
>> HTH
>> Kalen Delaney, SQL Server MVP
>> www.InsideSQLServer.com
>> http://blog.kalendelaney.com
>>
>> "TheSQLGuru" <kgboles@.earthlink.net> wrote in message
>> news:13o71gecmi9nmfb@.corp.supernews.com...
>> Modify your delete to do it in batches. Pick date ranges that will
>> only delete 1-5% of the table at once max for each range and then you
>> will probably be ok.
>> --
>> Kevin G. Boles
>> Indicium Resources, Inc.
>> SQL Server MVP
>> kgboles a earthlink dt net
>>
>> "fiaola" <fiaola@.mail.com> wrote in message
>> news:uLj2q0WUIHA.4768@.TK2MSFTNGP02.phx.gbl...
>>> I'm trying to clear some data from a SQL DB table, but i'm getting
>>> this error:
>>> I'm just running a Delete Query using Date Diff function. I read in
>>> some web site that this maybe a problem with SQL Server Management
>>> Tools. I appreciate any help to get around this and any suggestions
>>> would be great.
>>> Msg 9002, Level 17, State 4, Line 2
>>>
>>> The transaction log for database 'EventSentry' is full. To find out
>>> why space in the log cannot be reused, see the log_reuse_wait_desc
>>> column in sys.databases
>>>
>>> Thanks for answering.
>>>
>>>
>>
>>
>>
>>
>>
>|||Last question on this.
Can these products run in a scan mode when SQL is running so we have a
picture of the fragmentation? I am the DBA, the Infrastructure guys do the
Windows maintenance.
Thanks
Chris
"TheSQLGuru" <kgboles@.earthlink.net> wrote in message
news:13odvkmn08vcfa0@.corp.supernews.com...
>I would recommend diskkeeper. There are many others from symantec,
>perfectdisk (raxco maybe?), mcaffee probably has one, one built into
>windows (downgraded version of diskkeeper IIRC).
> --
> Kevin G. Boles
> Indicium Resources, Inc.
> SQL Server MVP
> kgboles a earthlink dt net
>
> "Chris Wood" <anonymous@.microsoft.com> wrote in message
> news:e6$B%23Y9UIHA.4448@.TK2MSFTNGP03.phx.gbl...
>> kevin,
>> What can we use to see how many file fragments there are? Running W2K3
>> SP2.
>> Thanks
>> Chris
>> "TheSQLGuru" <kgboles@.earthlink.net> wrote in message
>> news:13od5m2iv7ec365@.corp.supernews.com...
>>I had a client with 300K+ file fragments when I arrived. 18% throughput
>>improvement from OS file defrag operation. It was on a small RAID10 set
>>(6 drives IIRC).
>> --
>> Kevin G. Boles
>> Indicium Resources, Inc.
>> SQL Server MVP
>> kgboles a earthlink dt net
>>
>> "Chris Wood" <anonymous@.microsoft.com> wrote in message
>> news:u0Spi6uUIHA.4768@.TK2MSFTNGP02.phx.gbl...
>> Kevin,
>> We also try and size our data and log files with limited growth. I have
>> seen problems with an unlimited log and percent full log alerts.
>> How much improvement would a disk defrag give you on todays raided
>> disks?
>> Thanks
>> Chris
>> "TheSQLGuru" <kgboles@.earthlink.net> wrote in message
>> news:13o7ttr3dli55fd@.corp.supernews.com...
>> Good point. I haven't seen tlogs set with no autogrow that I recall.
>> Almost every client I have been at still has the defaults for data/log
>> size and growths (2MB and 1MB growth for data and 1MB and 10% growth
>> for tlog, IIRC). Makes me look good when I have them defrag the hard
>> drive and pick up a big perf gain. :-)
>> --
>> Kevin G. Boles
>> Indicium Resources, Inc.
>> SQL Server MVP
>> kgboles a earthlink dt net
>>
>> "Kalen Delaney" <replies@.public_newsgroups.com> wrote in message
>> news:u3AgCjgUIHA.4584@.TK2MSFTNGP03.phx.gbl...
>> But we still don't know how big the log is. I've seen logs that are
>> set at the default 1 MB with no autogrow.
>> --
>> HTH
>> Kalen Delaney, SQL Server MVP
>> www.InsideSQLServer.com
>> http://blog.kalendelaney.com
>>
>> "TheSQLGuru" <kgboles@.earthlink.net> wrote in message
>> news:13o71gecmi9nmfb@.corp.supernews.com...
>>> Modify your delete to do it in batches. Pick date ranges that will
>>> only delete 1-5% of the table at once max for each range and then
>>> you will probably be ok.
>>>
>>> --
>>> Kevin G. Boles
>>> Indicium Resources, Inc.
>>> SQL Server MVP
>>> kgboles a earthlink dt net
>>>
>>>
>>> "fiaola" <fiaola@.mail.com> wrote in message
>>> news:uLj2q0WUIHA.4768@.TK2MSFTNGP02.phx.gbl...
>>> I'm trying to clear some data from a SQL DB table, but i'm getting
>>> this error:
>>> I'm just running a Delete Query using Date Diff function. I read
>>> in some web site that this maybe a problem with SQL Server
>>> Management Tools. I appreciate any help to get around this and any
>>> suggestions would be great.
>>> Msg 9002, Level 17, State 4, Line 2
>>>
>>> The transaction log for database 'EventSentry' is full. To find out
>>> why space in the log cannot be reused, see the log_reuse_wait_desc
>>> column in sys.databases
>>>
>>> Thanks for answering.
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>>
>|||I know for a fact that several of them can. I don't know about all of them.
BTW, It is recommended that you shut sql server down during a defrag
operation, but I have at least 2 clients using diskkeeper that do not do
this. Do so at your own risk though.
--
Kevin G. Boles
Indicium Resources, Inc.
SQL Server MVP
kgboles a earthlink dt net
"Chris Wood" <anonymous@.microsoft.com> wrote in message
news:uoeWXFHVIHA.5360@.TK2MSFTNGP03.phx.gbl...
> Last question on this.
> Can these products run in a scan mode when SQL is running so we have a
> picture of the fragmentation? I am the DBA, the Infrastructure guys do the
> Windows maintenance.
> Thanks
> Chris
> "TheSQLGuru" <kgboles@.earthlink.net> wrote in message
> news:13odvkmn08vcfa0@.corp.supernews.com...
>>I would recommend diskkeeper. There are many others from symantec,
>>perfectdisk (raxco maybe?), mcaffee probably has one, one built into
>>windows (downgraded version of diskkeeper IIRC).
>> --
>> Kevin G. Boles
>> Indicium Resources, Inc.
>> SQL Server MVP
>> kgboles a earthlink dt net
>>
>> "Chris Wood" <anonymous@.microsoft.com> wrote in message
>> news:e6$B%23Y9UIHA.4448@.TK2MSFTNGP03.phx.gbl...
>> kevin,
>> What can we use to see how many file fragments there are? Running W2K3
>> SP2.
>> Thanks
>> Chris
>> "TheSQLGuru" <kgboles@.earthlink.net> wrote in message
>> news:13od5m2iv7ec365@.corp.supernews.com...
>>I had a client with 300K+ file fragments when I arrived. 18% throughput
>>improvement from OS file defrag operation. It was on a small RAID10 set
>>(6 drives IIRC).
>> --
>> Kevin G. Boles
>> Indicium Resources, Inc.
>> SQL Server MVP
>> kgboles a earthlink dt net
>>
>> "Chris Wood" <anonymous@.microsoft.com> wrote in message
>> news:u0Spi6uUIHA.4768@.TK2MSFTNGP02.phx.gbl...
>> Kevin,
>> We also try and size our data and log files with limited growth. I
>> have seen problems with an unlimited log and percent full log alerts.
>> How much improvement would a disk defrag give you on todays raided
>> disks?
>> Thanks
>> Chris
>> "TheSQLGuru" <kgboles@.earthlink.net> wrote in message
>> news:13o7ttr3dli55fd@.corp.supernews.com...
>> Good point. I haven't seen tlogs set with no autogrow that I recall.
>> Almost every client I have been at still has the defaults for
>> data/log size and growths (2MB and 1MB growth for data and 1MB and
>> 10% growth for tlog, IIRC). Makes me look good when I have them
>> defrag the hard drive and pick up a big perf gain. :-)
>> --
>> Kevin G. Boles
>> Indicium Resources, Inc.
>> SQL Server MVP
>> kgboles a earthlink dt net
>>
>> "Kalen Delaney" <replies@.public_newsgroups.com> wrote in message
>> news:u3AgCjgUIHA.4584@.TK2MSFTNGP03.phx.gbl...
>>> But we still don't know how big the log is. I've seen logs that are
>>> set at the default 1 MB with no autogrow.
>>>
>>> --
>>> HTH
>>> Kalen Delaney, SQL Server MVP
>>> www.InsideSQLServer.com
>>> http://blog.kalendelaney.com
>>>
>>>
>>> "TheSQLGuru" <kgboles@.earthlink.net> wrote in message
>>> news:13o71gecmi9nmfb@.corp.supernews.com...
>>> Modify your delete to do it in batches. Pick date ranges that will
>>> only delete 1-5% of the table at once max for each range and then
>>> you will probably be ok.
>>>
>>> --
>>> Kevin G. Boles
>>> Indicium Resources, Inc.
>>> SQL Server MVP
>>> kgboles a earthlink dt net
>>>
>>>
>>> "fiaola" <fiaola@.mail.com> wrote in message
>>> news:uLj2q0WUIHA.4768@.TK2MSFTNGP02.phx.gbl...
>>> I'm trying to clear some data from a SQL DB table, but i'm getting
>>> this error:
>>> I'm just running a Delete Query using Date Diff function. I read
>>> in some web site that this maybe a problem with SQL Server
>>> Management Tools. I appreciate any help to get around this and
>>> any suggestions would be great.
>>> Msg 9002, Level 17, State 4, Line 2
>>>
>>> The transaction log for database 'EventSentry' is full. To find
>>> out why space in the log cannot be reused, see the
>>> log_reuse_wait_desc column in sys.databases
>>>
>>> Thanks for answering.
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>>
>