Backups

I guess I'm not understander your responce. Do I need a
specific job to "Update statistics used by the query
optimizer"?Are you asking a question or responding to the question already asked in this thread?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Lee" <anonymous@.discussions.microsoft.com> wrote in message
news:2479d01c45f79$e19f6de0$a501280a@.phx.gbl...
> I guess I'm not understander your responce. Do I need a
> specific job to "Update statistics used by the query
> optimizer"?

Backup Transaction Log - Event ID 17055

I recently changed the recovery model from simple to full on a specific SQL
Server 2000 database. I am backing up the transaction log every two hours
via a maintenance plan. I have other SQL Server 2000 DB's defined with the
full recovery model and do not receive these messages. The following error,
not a warning, appears in the application event log when the log backup
completes also in the database log. Are these backups valid? Found KB
818202 on this, but I cannot determine what action needs to be taken, if any.
Thoughts'?
Source: MSSQLSERVER
Category: (6)
Event ID: 17055
Description: 18278 Database log truncated: Database: dbname.Hi,
Can you perform a full database backup and then follow the transaction log
backup.
This is required when you change the recovery model from SIMPLE to FULL
Thanks
Hari
MCDBA
"paldba" wrote:
> I recently changed the recovery model from simple to full on a specific SQL
> Server 2000 database. I am backing up the transaction log every two hours
> via a maintenance plan. I have other SQL Server 2000 DB's defined with the
> full recovery model and do not receive these messages. The following error,
> not a warning, appears in the application event log when the log backup
> completes also in the database log. Are these backups valid? Found KB
> 818202 on this, but I cannot determine what action needs to be taken, if any.
> Thoughts'?
> Source: MSSQLSERVER
> Category: (6)
> Event ID: 17055
> Description: 18278 Database log truncated: Database: dbname.|||Yes, that has been completed.
"Hari Prasad" wrote:
> Hi,
> Can you perform a full database backup and then follow the transaction log
> backup.
> This is required when you change the recovery model from SIMPLE to FULL
> Thanks
> Hari
> MCDBA
> "paldba" wrote:
> > I recently changed the recovery model from simple to full on a specific SQL
> > Server 2000 database. I am backing up the transaction log every two hours
> > via a maintenance plan. I have other SQL Server 2000 DB's defined with the
> > full recovery model and do not receive these messages. The following error,
> > not a warning, appears in the application event log when the log backup
> > completes also in the database log. Are these backups valid? Found KB
> > 818202 on this, but I cannot determine what action needs to be taken, if any.
> > Thoughts'?
> >
> > Source: MSSQLSERVER
> > Category: (6)
> > Event ID: 17055
> > Description: 18278 Database log truncated: Database: dbname.|||It looks like someone is running a Backup LOG command with
NO_LOG or TRUNCATE_ONLY option. Investigate if anyone or
any job is scheduled to run this command. Also, check your
own backup log command to see if it includes this option.
Lll the Log backups after a truncate will be invalid till
you take a FULL backup.
>--Original Message--
>I recently changed the recovery model from simple to full
on a specific SQL
>Server 2000 database. I am backing up the transaction
log every two hours
>via a maintenance plan. I have other SQL Server 2000 DB's
defined with the
>full recovery model and do not receive these messages.
The following error,
>not a warning, appears in the application event log when
the log backup
>completes also in the database log. Are these backups
valid? Found KB
>818202 on this, but I cannot determine what action needs
to be taken, if any.
> Thoughts'?
>Source: MSSQLSERVER
>Category: (6)
>Event ID: 17055
>Description: 18278 Database log truncated: Database:
dbname.
>.
>

Backup Transaction Log - Event ID 17055

I recently changed the recovery model from simple to full on a specific SQL
Server 2000 database. I am backing up the transaction log every two hours
via a maintenance plan. I have other SQL Server 2000 DB's defined with the
full recovery model and do not receive these messages. The following error,
not a warning, appears in the application event log when the log backup
completes also in the database log. Are these backups valid? Found KB
818202 on this, but I cannot determine what action needs to be taken, if any.
Thoughts??
Source: MSSQLSERVER
Category: (6)
Event ID: 17055
Description: 18278 Database log truncated: Database: dbname.
Hi,
Can you perform a full database backup and then follow the transaction log
backup.
This is required when you change the recovery model from SIMPLE to FULL
Thanks
Hari
MCDBA
"paldba" wrote:

> I recently changed the recovery model from simple to full on a specific SQL
> Server 2000 database. I am backing up the transaction log every two hours
> via a maintenance plan. I have other SQL Server 2000 DB's defined with the
> full recovery model and do not receive these messages. The following error,
> not a warning, appears in the application event log when the log backup
> completes also in the database log. Are these backups valid? Found KB
> 818202 on this, but I cannot determine what action needs to be taken, if any.
> Thoughts??
> Source: MSSQLSERVER
> Category: (6)
> Event ID: 17055
> Description: 18278 Database log truncated: Database: dbname.
|||Yes, that has been completed.
"Hari Prasad" wrote:
[vbcol=seagreen]
> Hi,
> Can you perform a full database backup and then follow the transaction log
> backup.
> This is required when you change the recovery model from SIMPLE to FULL
> Thanks
> Hari
> MCDBA
> "paldba" wrote: