are backups not successful?

Hello:
A client of mine is using SQL Server 2000 and has constructed a database
maintenance job to do "Complete Backup" and "Transaction Log Backup".
In another thread, I had asked why the job was not deleting its own backups
files as the job is configured to delete backups after one day.
Someone had replied and said that the deletions will not take effect until
the backup job completes successfully.
Since the backup files are not deleting, does that mean that the backup job
is not being successful?
If that's the case, then, I don't know what the client is doing wrong. It's
not hard to set up a backup job in the database maintenance plan.
I mean, does the SQL Server Service need to be stopped in order for these
backups to take place successfully?
Thanks!
childofthe1980s
Hi,
Before i suggest u any thing just check the maintinance plan log file.
It is not true that backup will not delete till the next backup is
successful.
Check maintinance plan again and make sure that u had selected one
day(delete old files)
check the path on the backup.
hope this helps
from
Killer

are backups not successful?

Hello:
A client of mine is using SQL Server 2000 and has constructed a database
maintenance job to do "Complete Backup" and "Transaction Log Backup".
In another thread, I had asked why the job was not deleting its own backups
files as the job is configured to delete backups after one day.
Someone had replied and said that the deletions will not take effect until
the backup job completes successfully.
Since the backup files are not deleting, does that mean that the backup job
is not being successful?
If that's the case, then, I don't know what the client is doing wrong. It's
not hard to set up a backup job in the database maintenance plan.
I mean, does the SQL Server Service need to be stopped in order for these
backups to take place successfully?
Thanks!
childofthe1980sHi,
Before i suggest u any thing just check the maintinance plan log file.
It is not true that backup will not delete till the next backup is
successful.
Check maintinance plan again and make sure that u had selected one
day(delete old files)
check the path on the backup.
hope this helps
from
Killersql

are backups not successful?

Hello:
A client of mine is using SQL Server 2000 and has constructed a database
maintenance job to do "Complete Backup" and "Transaction Log Backup".
In another thread, I had asked why the job was not deleting its own backups
files as the job is configured to delete backups after one day.
Someone had replied and said that the deletions will not take effect until
the backup job completes successfully.
Since the backup files are not deleting, does that mean that the backup job
is not being successful?
If that's the case, then, I don't know what the client is doing wrong. It's
not hard to set up a backup job in the database maintenance plan.
I mean, does the SQL Server Service need to be stopped in order for these
backups to take place successfully?
Thanks!
childofthe1980sHi,
Before i suggest u any thing just check the maintinance plan log file.
--
It is not true that backup will not delete till the next backup is
successful.
Check maintinance plan again and make sure that u had selected one
day(delete old files)
check the path on the backup.
hope this helps
from
Killer

Archive SQL Server Logs..?

Hi Folks
is anyone knows that how can i archive(delete) log file for current date or
specific date'?
Thanx in advance
regards
--
Message posted via http://www.sqlmonster.comHi,
Did you mean SQL Server error logs or Tranasction log backups?
If it is Error log, sql server by itself keep only 6+1 (current) copies by
default. The old files will be deleted automatically.
If it is Transaction log backup files, then use database maintenance plan to
fix a archival day. So as old file(s) will be deleted automatically.
Thanks
Hari
SQL Server MVP
"sonny singh via SQLMonster.com" <forum@.nospam.SQLMonster.com> wrote in
message news:fa2cf9e684d741419c1094db51a9fea5@.SQLMonster.com...
> Hi Folks
> is anyone knows that how can i archive(delete) log file for current date
> or
> specific date'?
> Thanx in advance
> regards
> --
> Message posted via http://www.sqlmonster.com|||Hi Hari
You can change the number of error logs maintained by editing the Registry
for any instance. For the default instance, find the key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer and edit it by
adding a new value. Define the value with the name NumErrorLogs, and the
type REG_DWORD. Supply any initial value desired, but keep in mind that the
value you enter when editing the Registry will be in hexadecimal format.
For a named instance, you need to find the key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\<SQL Server
Instance Name>\MSSQLServer. Again, use the Edit feature of the Registry to
add a new value with the name NumErrorLogs of type REG_DWORD, and supply an
initial value in hexadecimal format.
--
HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:Os1pMt2bFHA.3712@.TK2MSFTNGP09.phx.gbl...
> Hi,
> Did you mean SQL Server error logs or Tranasction log backups?
> If it is Error log, sql server by itself keep only 6+1 (current) copies by
> default. The old files will be deleted automatically.
> If it is Transaction log backup files, then use database maintenance plan
> to fix a archival day. So as old file(s) will be deleted automatically.
> Thanks
> Hari
> SQL Server MVP
> "sonny singh via SQLMonster.com" <forum@.nospam.SQLMonster.com> wrote in
> message news:fa2cf9e684d741419c1094db51a9fea5@.SQLMonster.com...
>> Hi Folks
>> is anyone knows that how can i archive(delete) log file for current date
>> or
>> specific date'?
>> Thanx in advance
>> regards
>> --
>> Message posted via http://www.sqlmonster.com
>

Archive SQL Server Logs..?

Hi Folks
is anyone knows that how can i archive(delete) log file for current date or
specific date??
Thanx in advance
regards
Message posted via http://www.droptable.com
Hi,
Did you mean SQL Server error logs or Tranasction log backups?
If it is Error log, sql server by itself keep only 6+1 (current) copies by
default. The old files will be deleted automatically.
If it is Transaction log backup files, then use database maintenance plan to
fix a archival day. So as old file(s) will be deleted automatically.
Thanks
Hari
SQL Server MVP
"sonny singh via droptable.com" <forum@.nospam.droptable.com> wrote in
message news:fa2cf9e684d741419c1094db51a9fea5@.droptable.co m...
> Hi Folks
> is anyone knows that how can i archive(delete) log file for current date
> or
> specific date??
> Thanx in advance
> regards
> --
> Message posted via http://www.droptable.com
|||Hi Hari
You can change the number of error logs maintained by editing the Registry
for any instance. For the default instance, find the key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\ MSSQLServer and edit it by
adding a new value. Define the value with the name NumErrorLogs, and the
type REG_DWORD. Supply any initial value desired, but keep in mind that the
value you enter when editing the Registry will be in hexadecimal format.
For a named instance, you need to find the key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\<SQL Server
Instance Name>\MSSQLServer. Again, use the Edit feature of the Registry to
add a new value with the name NumErrorLogs of type REG_DWORD, and supply an
initial value in hexadecimal format.
HTH
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:Os1pMt2bFHA.3712@.TK2MSFTNGP09.phx.gbl...
> Hi,
> Did you mean SQL Server error logs or Tranasction log backups?
> If it is Error log, sql server by itself keep only 6+1 (current) copies by
> default. The old files will be deleted automatically.
> If it is Transaction log backup files, then use database maintenance plan
> to fix a archival day. So as old file(s) will be deleted automatically.
> Thanks
> Hari
> SQL Server MVP
> "sonny singh via droptable.com" <forum@.nospam.droptable.com> wrote in
> message news:fa2cf9e684d741419c1094db51a9fea5@.droptable.co m...
>

Archive SQL Server Logs..?

Hi Folks
is anyone knows that how can i archive(delete) log file for current date or
specific date'?
Thanx in advance
regards
Message posted via http://www.droptable.comHi,
Did you mean SQL Server error logs or Tranasction log backups?
If it is Error log, sql server by itself keep only 6+1 (current) copies by
default. The old files will be deleted automatically.
If it is Transaction log backup files, then use database maintenance plan to
fix a archival day. So as old file(s) will be deleted automatically.
Thanks
Hari
SQL Server MVP
"sonny singh via droptable.com" <forum@.nospam.droptable.com> wrote in
message news:fa2cf9e684d741419c1094db51a9fea5@.SQ
droptable.com...
> Hi Folks
> is anyone knows that how can i archive(delete) log file for current date
> or
> specific date'?
> Thanx in advance
> regards
> --
> Message posted via http://www.droptable.com|||Hi Hari
You can change the number of error logs maintained by editing the Registry
for any instance. For the default instance, find the key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MS
SQLServer\MSSQLServer and edit it by
adding a new value. Define the value with the name NumErrorLogs, and the
type REG_DWORD. Supply any initial value desired, but keep in mind that the
value you enter when editing the Registry will be in hexadecimal format.
For a named instance, you need to find the key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Mi
crosoft SQL Server\<SQL Server
Instance Name>\MSSQLServer. Again, use the Edit feature of the Registry to
add a new value with the name NumErrorLogs of type REG_DWORD, and supply an
initial value in hexadecimal format.
HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:Os1pMt2bFHA.3712@.TK2MSFTNGP09.phx.gbl...
> Hi,
> Did you mean SQL Server error logs or Tranasction log backups?
> If it is Error log, sql server by itself keep only 6+1 (current) copies by
> default. The old files will be deleted automatically.
> If it is Transaction log backup files, then use database maintenance plan
> to fix a archival day. So as old file(s) will be deleted automatically.
> Thanks
> Hari
> SQL Server MVP
> "sonny singh via droptable.com" <forum@.nospam.droptable.com> wrote in
> message news:fa2cf9e684d741419c1094db51a9fea5@.SQ
droptable.com...
>

archive logging the log file

I am new to SQL Server, but I cannot seem to find any way that SQL Server
will automatically move a log file (when it isn't needed anymore) off to
archive. Is the only way I can do this by setting up a batch process and
doing it myself?
Help?I believe you are referring to transaction logs. The proper way to manage
transaction logs for databases in the FULL or BULK_LOGGED recovery model is
to backup the transaction log periodically. This will remove committed data
from the log (keeping the size reasonable) and allow you to use the log
backups in conjunction with database backups as part of your recovery plan.
A common practice is to backup to disk and then archive those backups to
tape. You can setup database maintenance plans to perform both database and
transaction log backups or create and schedule your own backup scripts. See
the Books Online for more information.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"learningdba" <learningdba@.discussions.microsoft.com> wrote in message
news:6BAE1103-01FC-45A4-B57E-B8FCD9AA86E3@.microsoft.com...
>I am new to SQL Server, but I cannot seem to find any way that SQL Server
> will automatically move a log file (when it isn't needed anymore) off to
> archive. Is the only way I can do this by setting up a batch process and
> doing it myself?
> Help?|||Transaction logs are circular files, the same space is reused over and over
again, so there is never a need to "remove the files"... As Dan says, the
way to remove transactions and make space available for re-use is to back up
the log , or use SQL Simple recovery mode.
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"learningdba" <learningdba@.discussions.microsoft.com> wrote in message
news:6BAE1103-01FC-45A4-B57E-B8FCD9AA86E3@.microsoft.com...
> I am new to SQL Server, but I cannot seem to find any way that SQL Server
> will automatically move a log file (when it isn't needed anymore) off to
> archive. Is the only way I can do this by setting up a batch process and
> doing it myself?
> Help?|||"learningdba" <learningdba@.discussions.microsoft.com> wrote in message
news:6BAE1103-01FC-45A4-B57E-B8FCD9AA86E3@.microsoft.com...
> I am new to SQL Server, but I cannot seem to find any way that SQL Server
> will automatically move a log file (when it isn't needed anymore) off to
> archive. Is the only way I can do this by setting up a batch process and
> doing it myself?
>
Just to add to what others have said, it sounds like you're coming from an
Oracle background?
In that case, basically it comes down to, SQL Server reuses the same file
and can do on-line backups of it which will "clear it out".
> Help?sql

archive logging the log file

I am new to SQL Server, but I cannot seem to find any way that SQL Server
will automatically move a log file (when it isn't needed anymore) off to
archive. Is the only way I can do this by setting up a batch process and
doing it myself?
Help?
I believe you are referring to transaction logs. The proper way to manage
transaction logs for databases in the FULL or BULK_LOGGED recovery model is
to backup the transaction log periodically. This will remove committed data
from the log (keeping the size reasonable) and allow you to use the log
backups in conjunction with database backups as part of your recovery plan.
A common practice is to backup to disk and then archive those backups to
tape. You can setup database maintenance plans to perform both database and
transaction log backups or create and schedule your own backup scripts. See
the Books Online for more information.
Hope this helps.
Dan Guzman
SQL Server MVP
"learningdba" <learningdba@.discussions.microsoft.com> wrote in message
news:6BAE1103-01FC-45A4-B57E-B8FCD9AA86E3@.microsoft.com...
>I am new to SQL Server, but I cannot seem to find any way that SQL Server
> will automatically move a log file (when it isn't needed anymore) off to
> archive. Is the only way I can do this by setting up a batch process and
> doing it myself?
> Help?
|||Transaction logs are circular files, the same space is reused over and over
again, so there is never a need to "remove the files"... As Dan says, the
way to remove transactions and make space available for re-use is to back up
the log , or use SQL Simple recovery mode.
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"learningdba" <learningdba@.discussions.microsoft.com> wrote in message
news:6BAE1103-01FC-45A4-B57E-B8FCD9AA86E3@.microsoft.com...
> I am new to SQL Server, but I cannot seem to find any way that SQL Server
> will automatically move a log file (when it isn't needed anymore) off to
> archive. Is the only way I can do this by setting up a batch process and
> doing it myself?
> Help?
|||"learningdba" <learningdba@.discussions.microsoft.com> wrote in message
news:6BAE1103-01FC-45A4-B57E-B8FCD9AA86E3@.microsoft.com...
> I am new to SQL Server, but I cannot seem to find any way that SQL Server
> will automatically move a log file (when it isn't needed anymore) off to
> archive. Is the only way I can do this by setting up a batch process and
> doing it myself?
>
Just to add to what others have said, it sounds like you're coming from an
Oracle background?
In that case, basically it comes down to, SQL Server reuses the same file
and can do on-line backups of it which will "clear it out".

> Help?

archive logging the log file

I am new to SQL Server, but I cannot seem to find any way that SQL Server
will automatically move a log file (when it isn't needed anymore) off to
archive. Is the only way I can do this by setting up a batch process and
doing it myself?
Help?I believe you are referring to transaction logs. The proper way to manage
transaction logs for databases in the FULL or BULK_LOGGED recovery model is
to backup the transaction log periodically. This will remove committed data
from the log (keeping the size reasonable) and allow you to use the log
backups in conjunction with database backups as part of your recovery plan.
A common practice is to backup to disk and then archive those backups to
tape. You can setup database maintenance plans to perform both database and
transaction log backups or create and schedule your own backup scripts. See
the Books Online for more information.
Hope this helps.
Dan Guzman
SQL Server MVP
"learningdba" <learningdba@.discussions.microsoft.com> wrote in message
news:6BAE1103-01FC-45A4-B57E-B8FCD9AA86E3@.microsoft.com...
>I am new to SQL Server, but I cannot seem to find any way that SQL Server
> will automatically move a log file (when it isn't needed anymore) off to
> archive. Is the only way I can do this by setting up a batch process and
> doing it myself?
> Help?|||Transaction logs are circular files, the same space is reused over and over
again, so there is never a need to "remove the files"... As Dan says, the
way to remove transactions and make space available for re-use is to back up
the log , or use SQL Simple recovery mode.
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"learningdba" <learningdba@.discussions.microsoft.com> wrote in message
news:6BAE1103-01FC-45A4-B57E-B8FCD9AA86E3@.microsoft.com...
> I am new to SQL Server, but I cannot seem to find any way that SQL Server
> will automatically move a log file (when it isn't needed anymore) off to
> archive. Is the only way I can do this by setting up a batch process and
> doing it myself?
> Help?|||"learningdba" <learningdba@.discussions.microsoft.com> wrote in message
news:6BAE1103-01FC-45A4-B57E-B8FCD9AA86E3@.microsoft.com...
> I am new to SQL Server, but I cannot seem to find any way that SQL Server
> will automatically move a log file (when it isn't needed anymore) off to
> archive. Is the only way I can do this by setting up a batch process and
> doing it myself?
>
Just to add to what others have said, it sounds like you're coming from an
Oracle background?
In that case, basically it comes down to, SQL Server reuses the same file
and can do on-line backups of it which will "clear it out".

> Help?

Architecture

Hello,
I want to kow if the following architecture is good :
Disque 1&2 ( Raid 1)
c: OS
d: sqlserver + system tables + log files
Disque 3&4&5 (Raid 5)
e: dataIf you don't plan on having any volume it would be fine. Otherwise, it would suck. A 3 disk RAID array is the slowest RAID 5 configuration possible. In addition, if you want high performance you should have the tempdb and/or the log files on seperate disks.

If you only have five disks though, this should work.

Apply Log File Transactions

I lost my mdf because of a failure on the RAID. The log
file was on another disk and it is apparently good thru
this morning. My last complete backup was last Friday
morning. I made two copies of the good log file and
restored the database using the option to restore more
log files. I would like to apply the log file I saved to
this database but the restore process needs a file
created by backup. I cannot figure out how to back up the
saved log file using a file name. How can I do this?
BACKUP LOG XXX FILE = ? TO DISK
= 'D:\MSSQL\BACKUP\SAFE.BKP'
Hi
Perform BACKUP LOG databasename WITH NO_TRUNCATE (For more details please
refer to BOL)
"pbrattin" <pbrattin@.removethis-bigfoot.com> wrote in message
news:181501c426d5$a693f360$a101280a@.phx.gbl...
> I lost my mdf because of a failure on the RAID. The log
> file was on another disk and it is apparently good thru
> this morning. My last complete backup was last Friday
> morning. I made two copies of the good log file and
> restored the database using the option to restore more
> log files. I would like to apply the log file I saved to
> this database but the restore process needs a file
> created by backup. I cannot figure out how to back up the
> saved log file using a file name. How can I do this?
> BACKUP LOG XXX FILE = ? TO DISK
> = 'D:\MSSQL\BACKUP\SAFE.BKP'
>
>

Apply Log File Transactions

I lost my mdf because of a failure on the RAID. The log
file was on another disk and it is apparently good thru
this morning. My last complete backup was last Friday
morning. I made two copies of the good log file and
restored the database using the option to restore more
log files. I would like to apply the log file I saved to
this database but the restore process needs a file
created by backup. I cannot figure out how to back up the
saved log file using a file name. How can I do this?
BACKUP LOG XXX FILE = ' TO DISK
= 'D:\MSSQL\BACKUP\SAFE.BKP'Hi
Perform BACKUP LOG databasename WITH NO_TRUNCATE (For more details please
refer to BOL)
"pbrattin" <pbrattin@.removethis-bigfoot.com> wrote in message
news:181501c426d5$a693f360$a101280a@.phx.gbl...
> I lost my mdf because of a failure on the RAID. The log
> file was on another disk and it is apparently good thru
> this morning. My last complete backup was last Friday
> morning. I made two copies of the good log file and
> restored the database using the option to restore more
> log files. I would like to apply the log file I saved to
> this database but the restore process needs a file
> created by backup. I cannot figure out how to back up the
> saved log file using a file name. How can I do this?
> BACKUP LOG XXX FILE = ' TO DISK
> = 'D:\MSSQL\BACKUP\SAFE.BKP'
>
>

Apply Log File Transactions

I lost my mdf because of a failure on the RAID. The log
file was on another disk and it is apparently good thru
this morning. My last complete backup was last Friday
morning. I made two copies of the good log file and
restored the database using the option to restore more
log files. I would like to apply the log file I saved to
this database but the restore process needs a file
created by backup. I cannot figure out how to back up the
saved log file using a file name. How can I do this?
BACKUP LOG XXX FILE = ' TO DISK
= 'D:\MSSQL\BACKUP\SAFE.BKP'Hi
Perform BACKUP LOG databasename WITH NO_TRUNCATE (For more details please
refer to BOL)
"pbrattin" <pbrattin@.removethis-bigfoot.com> wrote in message
news:181501c426d5$a693f360$a101280a@.phx.gbl...
> I lost my mdf because of a failure on the RAID. The log
> file was on another disk and it is apparently good thru
> this morning. My last complete backup was last Friday
> morning. I made two copies of the good log file and
> restored the database using the option to restore more
> log files. I would like to apply the log file I saved to
> this database but the restore process needs a file
> created by backup. I cannot figure out how to back up the
> saved log file using a file name. How can I do this?
> BACKUP LOG XXX FILE = ' TO DISK
> = 'D:\MSSQL\BACKUP\SAFE.BKP'
>
>

Apply filter on dbcc log query

Hi,
I am reading online transaction log using dbcc log command.
But I don't want to read the whole online transaction log, because it will t
ake too long time. Is there any way through which I can filter the record an
d get lesser no. of records.
Is there any way through which I can use dbcc command directly in a query.
Or is there any undocumennted parameter that might passed to dcc log command
through which we can specify filter.
Thanks in advance
PushkarHi
dbcc log is undocumented, so all of it is unsupported.
AFAIK, the commands listed here are the only ones:
http://www.mssqlcity.com/Articles/U...CC.htm#part_2_8
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Pushkar" wrote:

> Hi,
> I am reading online transaction log using dbcc log command.
> But I don't want to read the whole online transaction log, because it will
take too long time. Is there any way through which I can filter the record
and get lesser no. of records.
> Is there any way through which I can use dbcc command directly in a query.
> Or is there any undocumennted parameter that might passed to dcc log comma
nd through which we can specify filter.
> Thanks in advance
> Pushkar
>|||> But I don't want to read the whole online transaction log, because it will
> take too long time.
Once again, I suggest a 3rd party tool. This operation is meant for
disaster recovery and occasional usage, not for every day activities where
performance is a concern. http://www.aspfaq.com/2449
It seems you've already spent enough time on this that you would have paid
for the license, if your opportunity cost is more than minimum wage...

Application v. Error log. Will I miss anything important?

Hi,
Will I miss anything important in MS SQL Server 2000 if I monitor only MS
Windows 2000 application event log and don't monitor SQL Server error log?
What exactly will I miss?
-- Many thanks, Oskar
A comment to my previous post.
I suppose errors with severity 19 an higher ar logged into Windows
Application log, so I shouldn't miss any of them when they happen. Is that
true? Also if in SQL Server Enterprise Manager I configure a particular
message so that it is logged, I should see it in Application event log too,
right?
-- Thanks again, Oskar.
"Oskar" wrote:

> Hi,
> Will I miss anything important in MS SQL Server 2000 if I monitor only MS
> Windows 2000 application event log and don't monitor SQL Server error log?
> What exactly will I miss?
> -- Many thanks, Oskar
>

Application v. Error log. Will I miss anything important?

Hi,
Will I miss anything important in MS SQL Server 2000 if I monitor only MS
Windows 2000 application event log and don't monitor SQL Server error log?
What exactly will I miss?
-- Many thanks, OskarA comment to my previous post.
I suppose errors with severity 19 an higher ar logged into Windows
Application log, so I shouldn't miss any of them when they happen. Is that
true? Also if in SQL Server Enterprise Manager I configure a particular
message so that it is logged, I should see it in Application event log too,
right?
-- Thanks again, Oskar.
"Oskar" wrote:
> Hi,
> Will I miss anything important in MS SQL Server 2000 if I monitor only MS
> Windows 2000 application event log and don't monitor SQL Server error log?
> What exactly will I miss?
> -- Many thanks, Oskar
>

Application v. Error log. Will I miss anything important?

Hi,
Will I miss anything important in MS SQL Server 2000 if I monitor only MS
Windows 2000 application event log and don't monitor SQL Server error log?
What exactly will I miss?
-- Many thanks, OskarA comment to my previous post.
I suppose errors with severity 19 an higher ar logged into Windows
Application log, so I shouldn't miss any of them when they happen. Is that
true? Also if in SQL Server Enterprise Manager I configure a particular
message so that it is logged, I should see it in Application event log too,
right?
-- Thanks again, Oskar.
"Oskar" wrote:

> Hi,
> Will I miss anything important in MS SQL Server 2000 if I monitor only MS
> Windows 2000 application event log and don't monitor SQL Server error log?
> What exactly will I miss?
> -- Many thanks, Oskar
>

Application log and backuo operations

I'm using Log Shipping in order to update a backup database on SQL Server
2000. I scheduled the transaction log backup every 5 minutes. The problem is
that SQL Server logs an event into the Application Log every time backup is
completed so the Application Log becomes full very quickly.
Is there any way to disable this behaviour ?
Thank you for any suggestions.
Luigi
Hi,
In Enterprise manager -- SQL Server Agent -- Jobs -- Select the Logshipping
task. Double click above that and
select "Notifications"
In that screen "UNCHECK" the Write to windows Application log and clieck
Apply and OK.
Thanks
Hari
MCDBA
"Luigi" <Luigi@.discussions.microsoft.com> wrote in message
news:3ACE4093-DD77-454C-B59C-A0369417D49D@.microsoft.com...
> I'm using Log Shipping in order to update a backup database on SQL Server
> 2000. I scheduled the transaction log backup every 5 minutes. The problem
is
> that SQL Server logs an event into the Application Log every time backup
is
> completed so the Application Log becomes full very quickly.
> Is there any way to disable this behaviour ?
> Thank you for any suggestions.
> Luigi
|||Thank you Hari for your suggestion.
I tried it but it doesn't solve my problem. The problem isn't about the
job's result : the job is set up in order to write to tha application log in
case of error only. It seems instead that it is the BACKUP command that logs
the event: when I launch my job, I find in the application log the same log
that I find when I backup database by Enterprise Maganer's facilities.
Bye
Luigi
"Hari Prasad" wrote:

> Hi,
> In Enterprise manager -- SQL Server Agent -- Jobs -- Select the Logshipping
> task. Double click above that and
> select "Notifications"
> In that screen "UNCHECK" the Write to windows Application log and clieck
> Apply and OK.
> Thanks
> Hari
> MCDBA
>
> "Luigi" <Luigi@.discussions.microsoft.com> wrote in message
> news:3ACE4093-DD77-454C-B59C-A0369417D49D@.microsoft.com...
> is
> is
>
>
|||SQL Server always write these messages to your logs. Even if you define in sysmessages that they shouldn't be
written. I have suggested to MS that SQL Server honors the setting in sysmessages, we'll see if any such
change appears in the future. If you want to communicate such a wish, you can use sqlwish@.microsoft.com.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Luigi" <Luigi@.discussions.microsoft.com> wrote in message
news:07C296BE-FD47-46D1-94A6-669FD6FB9C67@.microsoft.com...[vbcol=seagreen]
> Thank you Hari for your suggestion.
> I tried it but it doesn't solve my problem. The problem isn't about the
> job's result : the job is set up in order to write to tha application log in
> case of error only. It seems instead that it is the BACKUP command that logs
> the event: when I launch my job, I find in the application log the same log
> that I find when I backup database by Enterprise Maganer's facilities.
> Bye
> Luigi
>
> "Hari Prasad" wrote:

Application log and backuo operations

I'm using Log Shipping in order to update a backup database on SQL Server
2000. I scheduled the transaction log backup every 5 minutes. The problem is
that SQL Server logs an event into the Application Log every time backup is
completed so the Application Log becomes full very quickly.
Is there any way to disable this behaviour '
Thank you for any suggestions.
LuigiHi,
In Enterprise manager -- SQL Server Agent -- Jobs -- Select the Logshipping
task. Double click above that and
select "Notifications"
In that screen "UNCHECK" the Write to windows Application log and clieck
Apply and OK.
Thanks
Hari
MCDBA
"Luigi" <Luigi@.discussions.microsoft.com> wrote in message
news:3ACE4093-DD77-454C-B59C-A0369417D49D@.microsoft.com...
> I'm using Log Shipping in order to update a backup database on SQL Server
> 2000. I scheduled the transaction log backup every 5 minutes. The problem
is
> that SQL Server logs an event into the Application Log every time backup
is
> completed so the Application Log becomes full very quickly.
> Is there any way to disable this behaviour '
> Thank you for any suggestions.
> Luigi|||SQL Server always write these messages to your logs. Even if you define in sysmessages that they shouldn't be
written. I have suggested to MS that SQL Server honors the setting in sysmessages, we'll see if any such
change appears in the future. If you want to communicate such a wish, you can use sqlwish@.microsoft.com.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Luigi" <Luigi@.discussions.microsoft.com> wrote in message
news:07C296BE-FD47-46D1-94A6-669FD6FB9C67@.microsoft.com...
> Thank you Hari for your suggestion.
> I tried it but it doesn't solve my problem. The problem isn't about the
> job's result : the job is set up in order to write to tha application log in
> case of error only. It seems instead that it is the BACKUP command that logs
> the event: when I launch my job, I find in the application log the same log
> that I find when I backup database by Enterprise Maganer's facilities.
> Bye
> Luigi
>
> "Hari Prasad" wrote:
> > Hi,
> >
> > In Enterprise manager -- SQL Server Agent -- Jobs -- Select the Logshipping
> > task. Double click above that and
> > select "Notifications"
> >
> > In that screen "UNCHECK" the Write to windows Application log and clieck
> > Apply and OK.
> >
> > Thanks
> > Hari
> > MCDBA
> >
> >
> >
> > "Luigi" <Luigi@.discussions.microsoft.com> wrote in message
> > news:3ACE4093-DD77-454C-B59C-A0369417D49D@.microsoft.com...
> > > I'm using Log Shipping in order to update a backup database on SQL Server
> > > 2000. I scheduled the transaction log backup every 5 minutes. The problem
> > is
> > > that SQL Server logs an event into the Application Log every time backup
> > is
> > > completed so the Application Log becomes full very quickly.
> > >
> > > Is there any way to disable this behaviour '
> > >
> > > Thank you for any suggestions.
> > >
> > > Luigi
> >
> >
> >

Application log and backuo operations

I'm using Log Shipping in order to update a backup database on SQL Server
2000. I scheduled the transaction log backup every 5 minutes. The problem is
that SQL Server logs an event into the Application Log every time backup is
completed so the Application Log becomes full very quickly.
Is there any way to disable this behaviour '
Thank you for any suggestions.
LuigiHi,
In Enterprise manager -- SQL Server Agent -- Jobs -- Select the Logshipping
task. Double click above that and
select "Notifications"
In that screen "UNCHECK" the Write to windows Application log and clieck
Apply and OK.
Thanks
Hari
MCDBA
"Luigi" <Luigi@.discussions.microsoft.com> wrote in message
news:3ACE4093-DD77-454C-B59C-A0369417D49D@.microsoft.com...
> I'm using Log Shipping in order to update a backup database on SQL Server
> 2000. I scheduled the transaction log backup every 5 minutes. The problem
is
> that SQL Server logs an event into the Application Log every time backup
is
> completed so the Application Log becomes full very quickly.
> Is there any way to disable this behaviour '
> Thank you for any suggestions.
> Luigi|||Thank you Hari for your suggestion.
I tried it but it doesn't solve my problem. The problem isn't about the
job's result : the job is set up in order to write to tha application log in
case of error only. It seems instead that it is the BACKUP command that logs
the event: when I launch my job, I find in the application log the same log
that I find when I backup database by Enterprise Maganer's facilities.
Bye
Luigi
"Hari Prasad" wrote:

> Hi,
> In Enterprise manager -- SQL Server Agent -- Jobs -- Select the Logshippin
g
> task. Double click above that and
> select "Notifications"
> In that screen "UNCHECK" the Write to windows Application log and clieck
> Apply and OK.
> Thanks
> Hari
> MCDBA
>
> "Luigi" <Luigi@.discussions.microsoft.com> wrote in message
> news:3ACE4093-DD77-454C-B59C-A0369417D49D@.microsoft.com...
> is
> is
>
>|||SQL Server always write these messages to your logs. Even if you define in s
ysmessages that they shouldn't be
written. I have suggested to MS that SQL Server honors the setting in sysmes
sages, we'll see if any such
change appears in the future. If you want to communicate such a wish, you ca
n use sqlwish@.microsoft.com.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Luigi" <Luigi@.discussions.microsoft.com> wrote in message
news:07C296BE-FD47-46D1-94A6-669FD6FB9C67@.microsoft.com...[vbcol=seagreen]
> Thank you Hari for your suggestion.
> I tried it but it doesn't solve my problem. The problem isn't about the
> job's result : the job is set up in order to write to tha application log
in
> case of error only. It seems instead that it is the BACKUP command that lo
gs
> the event: when I launch my job, I find in the application log the same lo
g
> that I find when I backup database by Enterprise Maganer's facilities.
> Bye
> Luigi
>
> "Hari Prasad" wrote:
>