db log Timeout errors

Hi,
we've got a situation as below:
Error: database log truncated, db1
Error 9002 : The database log file for "temdb" is full. Backup the
transaction log for the database to free up some space
Any thoughts on these errors?
On db1, tempdb is 1314Mb with a log size of 28Mb. Both are set to grow by
10% unrestricted. Our Apps developers were getting some timeouts running
queries on DB1. It's possible they may be running some large queries that
cause these errors (or at least the second error). Any ideas on this?
What would be a probable solution?
Or they are harmless and can be ignored?
Many thanks,
SQL NewbieFor some operations, autogrow doesn't grow the file fast enough to keep up with the space usage
requirements. Hence a "full" error message. Reading your error message, this is in the tempdb
database. I suggest you pre-allocate space for tempdb. Use the ALTER DATABASE command for that.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Hugh" <Hugh@.discussions.microsoft.com> wrote in message
news:80BF48AB-2D21-4DA4-9E47-B860F0859FA6@.microsoft.com...
> Some guru please help...pretty congeated.
> "Hugh" wrote:
>> Hi,
>> we've got a situation as below:
>> Error: database log truncated, db1
>> Error 9002 : The database log file for "temdb" is full. Backup the
>> transaction log for the database to free up some space
>> Any thoughts on these errors?
>> On db1, tempdb is 1314Mb with a log size of 28Mb. Both are set to grow by
>> 10% unrestricted. Our Apps developers were getting some timeouts running
>> queries on DB1. It's possible they may be running some large queries that
>> cause these errors (or at least the second error). Any ideas on this?
>> What would be a probable solution?
>> Or they are harmless and can be ignored?
>> Many thanks,
>> SQL Newbie|||thanx mate.
can recommend some good materials on the concepts of how SQL server works?
Any samples of what the statement will be like?
Also how to know how much more space is required? Will it require restart?
Is anything loss due this error?
Any means to analyse and prevent similar occurences?
thanx,
An SQL newbie
"Tibor Karaszi" wrote:
> For some operations, autogrow doesn't grow the file fast enough to keep up with the space usage
> requirements. Hence a "full" error message. Reading your error message, this is in the tempdb
> database. I suggest you pre-allocate space for tempdb. Use the ALTER DATABASE command for that.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Hugh" <Hugh@.discussions.microsoft.com> wrote in message
> news:80BF48AB-2D21-4DA4-9E47-B860F0859FA6@.microsoft.com...
> > Some guru please help...pretty congeated.
> >
> > "Hugh" wrote:
> >
> >> Hi,
> >>
> >> we've got a situation as below:
> >>
> >> Error: database log truncated, db1
> >>
> >> Error 9002 : The database log file for "temdb" is full. Backup the
> >> transaction log for the database to free up some space
> >>
> >> Any thoughts on these errors?
> >>
> >> On db1, tempdb is 1314Mb with a log size of 28Mb. Both are set to grow by
> >> 10% unrestricted. Our Apps developers were getting some timeouts running
> >> queries on DB1. It's possible they may be running some large queries that
> >> cause these errors (or at least the second error). Any ideas on this?
> >>
> >> What would be a probable solution?
> >> Or they are harmless and can be ignored?
> >>
> >> Many thanks,
> >> SQL Newbie
>
>|||You might want to get a hold of "Inside SQL Server 2000" by Kalen Delaney.
It is a big book but if you want to know how sql server works that is the
book.
--
Andrew J. Kelly SQL MVP
"Hugh" <Hugh@.discussions.microsoft.com> wrote in message
news:8B067416-65CF-45A6-B899-636CE6AF4CE1@.microsoft.com...
> thanx mate.
> can recommend some good materials on the concepts of how SQL server works?
> Any samples of what the statement will be like?
> Also how to know how much more space is required? Will it require
restart?
> Is anything loss due this error?
> Any means to analyse and prevent similar occurences?
> thanx,
> An SQL newbie
> "Tibor Karaszi" wrote:
> > For some operations, autogrow doesn't grow the file fast enough to keep
up with the space usage
> > requirements. Hence a "full" error message. Reading your error message,
this is in the tempdb
> > database. I suggest you pre-allocate space for tempdb. Use the ALTER
DATABASE command for that.
> >
> > --
> > Tibor Karaszi, SQL Server MVP
> > http://www.karaszi.com/sqlserver/default.asp
> > http://www.solidqualitylearning.com/
> >
> >
> > "Hugh" <Hugh@.discussions.microsoft.com> wrote in message
> > news:80BF48AB-2D21-4DA4-9E47-B860F0859FA6@.microsoft.com...
> > > Some guru please help...pretty congeated.
> > >
> > > "Hugh" wrote:
> > >
> > >> Hi,
> > >>
> > >> we've got a situation as below:
> > >>
> > >> Error: database log truncated, db1
> > >>
> > >> Error 9002 : The database log file for "temdb" is full. Backup the
> > >> transaction log for the database to free up some space
> > >>
> > >> Any thoughts on these errors?
> > >>
> > >> On db1, tempdb is 1314Mb with a log size of 28Mb. Both are set to
grow by
> > >> 10% unrestricted. Our Apps developers were getting some timeouts
running
> > >> queries on DB1. It's possible they may be running some large queries
that
> > >> cause these errors (or at least the second error). Any ideas on this?
> > >>
> > >> What would be a probable solution?
> > >> Or they are harmless and can be ignored?
> > >>
> > >> Many thanks,
> > >> SQL Newbie
> >
> >
> >|||thanx Andrew,
Pertaining to my problem. can any1 provide some samples of what the
statement will be like?
Also how to know how much more space is required? Will it require restart?
Is anything loss due this error?
Any means to analyse and prevent similar occurences?
thanx,
An SQL newbie
"Andrew J. Kelly" wrote:
> You might want to get a hold of "Inside SQL Server 2000" by Kalen Delaney.
> It is a big book but if you want to know how sql server works that is the
> book.
> --
> Andrew J. Kelly SQL MVP
>
> "Hugh" <Hugh@.discussions.microsoft.com> wrote in message
> news:8B067416-65CF-45A6-B899-636CE6AF4CE1@.microsoft.com...
> > thanx mate.
> >
> > can recommend some good materials on the concepts of how SQL server works?
> >
> > Any samples of what the statement will be like?
> > Also how to know how much more space is required? Will it require
> restart?
> > Is anything loss due this error?
> >
> > Any means to analyse and prevent similar occurences?
> >
> > thanx,
> > An SQL newbie
> >
> > "Tibor Karaszi" wrote:
> >
> > > For some operations, autogrow doesn't grow the file fast enough to keep
> up with the space usage
> > > requirements. Hence a "full" error message. Reading your error message,
> this is in the tempdb
> > > database. I suggest you pre-allocate space for tempdb. Use the ALTER
> DATABASE command for that.
> > >
> > > --
> > > Tibor Karaszi, SQL Server MVP
> > > http://www.karaszi.com/sqlserver/default.asp
> > > http://www.solidqualitylearning.com/
> > >
> > >
> > > "Hugh" <Hugh@.discussions.microsoft.com> wrote in message
> > > news:80BF48AB-2D21-4DA4-9E47-B860F0859FA6@.microsoft.com...
> > > > Some guru please help...pretty congeated.
> > > >
> > > > "Hugh" wrote:
> > > >
> > > >> Hi,
> > > >>
> > > >> we've got a situation as below:
> > > >>
> > > >> Error: database log truncated, db1
> > > >>
> > > >> Error 9002 : The database log file for "temdb" is full. Backup the
> > > >> transaction log for the database to free up some space
> > > >>
> > > >> Any thoughts on these errors?
> > > >>
> > > >> On db1, tempdb is 1314Mb with a log size of 28Mb. Both are set to
> grow by
> > > >> 10% unrestricted. Our Apps developers were getting some timeouts
> running
> > > >> queries on DB1. It's possible they may be running some large queries
> that
> > > >> cause these errors (or at least the second error). Any ideas on this?
> > > >>
> > > >> What would be a probable solution?
> > > >> Or they are harmless and can be ignored?
> > > >>
> > > >> Many thanks,
> > > >> SQL Newbie
> > >
> > >
> > >
>
>|||> Pertaining to my problem. can any1 provide some samples of what the
> statement will be like?
There's an example in Books Online, I believe (I'm in a hurry right now).
> Also how to know how much more space is required?
Monitor tempdb size over time to get an idea of the space it needs for your particular applications,
schema, indexes, queries and workload.
> Will it require restart?
Tempdb is re-created every time SQL Server restarts. Applying the "template" size which you set
using ALTER DATABASE requires a re-start. You can also use ALTER DATABASE to change the size of your
running tempdb, but again, it is re-created at restart.
> Is anything loss due this error?
The statements that failed has ... failed.
> Any means to analyze and prevent similar occurences?
Monitor size, and your errorlogs/eventlogs.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Hugh" <Hugh@.discussions.microsoft.com> wrote in message
news:06CD159E-9ED4-4F20-9788-A40560615699@.microsoft.com...
> thanx Andrew,
> Pertaining to my problem. can any1 provide some samples of what the
> statement will be like?
> Also how to know how much more space is required? Will it require restart?
> Is anything loss due this error?
> Any means to analyse and prevent similar occurences?
> thanx,
> An SQL newbie
>
>
> "Andrew J. Kelly" wrote:
>> You might want to get a hold of "Inside SQL Server 2000" by Kalen Delaney.
>> It is a big book but if you want to know how sql server works that is the
>> book.
>> --
>> Andrew J. Kelly SQL MVP
>>
>> "Hugh" <Hugh@.discussions.microsoft.com> wrote in message
>> news:8B067416-65CF-45A6-B899-636CE6AF4CE1@.microsoft.com...
>> > thanx mate.
>> >
>> > can recommend some good materials on the concepts of how SQL server works?
>> >
>> > Any samples of what the statement will be like?
>> > Also how to know how much more space is required? Will it require
>> restart?
>> > Is anything loss due this error?
>> >
>> > Any means to analyse and prevent similar occurences?
>> >
>> > thanx,
>> > An SQL newbie
>> >
>> > "Tibor Karaszi" wrote:
>> >
>> > > For some operations, autogrow doesn't grow the file fast enough to keep
>> up with the space usage
>> > > requirements. Hence a "full" error message. Reading your error message,
>> this is in the tempdb
>> > > database. I suggest you pre-allocate space for tempdb. Use the ALTER
>> DATABASE command for that.
>> > >
>> > > --
>> > > Tibor Karaszi, SQL Server MVP
>> > > http://www.karaszi.com/sqlserver/default.asp
>> > > http://www.solidqualitylearning.com/
>> > >
>> > >
>> > > "Hugh" <Hugh@.discussions.microsoft.com> wrote in message
>> > > news:80BF48AB-2D21-4DA4-9E47-B860F0859FA6@.microsoft.com...
>> > > > Some guru please help...pretty congeated.
>> > > >
>> > > > "Hugh" wrote:
>> > > >
>> > > >> Hi,
>> > > >>
>> > > >> we've got a situation as below:
>> > > >>
>> > > >> Error: database log truncated, db1
>> > > >>
>> > > >> Error 9002 : The database log file for "temdb" is full. Backup the
>> > > >> transaction log for the database to free up some space
>> > > >>
>> > > >> Any thoughts on these errors?
>> > > >>
>> > > >> On db1, tempdb is 1314Mb with a log size of 28Mb. Both are set to
>> grow by
>> > > >> 10% unrestricted. Our Apps developers were getting some timeouts
>> running
>> > > >> queries on DB1. It's possible they may be running some large queries
>> that
>> > > >> cause these errors (or at least the second error). Any ideas on this?
>> > > >>
>> > > >> What would be a probable solution?
>> > > >> Or they are harmless and can be ignored?
>> > > >>
>> > > >> Many thanks,
>> > > >> SQL Newbie
>> > >
>> > >
>> > >
>>|||Some guru please help...pretty congeated.
"Hugh" wrote:
> Hi,
> we've got a situation as below:
> Error: database log truncated, db1
> Error 9002 : The database log file for "temdb" is full. Backup the
> transaction log for the database to free up some space
> Any thoughts on these errors?
> On db1, tempdb is 1314Mb with a log size of 28Mb. Both are set to grow by
> 10% unrestricted. Our Apps developers were getting some timeouts running
> queries on DB1. It's possible they may be running some large queries that
> cause these errors (or at least the second error). Any ideas on this?
> What would be a probable solution?
> Or they are harmless and can be ignored?
> Many thanks,
> SQL Newbie