Hi:
We configured a backup job in the database maintenance plan for a database
for both "Complete Backup" and the "Transaction Log". We told the job to
delete files after one day. It has not been deleting these files, though.
Why is that?
John
Hi
Files are deleted after the next backup completes successfully.
If you se a backup to delete after 1 day, and you don't run the actual
backup job for 2 days, the backup will remain on disk for 2 days, until
after the backup is successful.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"childofthe1980s" <childofthe1980s@.discussions.microsoft.com> wrote in
message news:6E533D8D-A308-47F9-AC62-282987DBF849@.microsoft.com...
> Hi:
> We configured a backup job in the database maintenance plan for a database
> for both "Complete Backup" and the "Transaction Log". We told the job to
> delete files after one day. It has not been deleting these files, though.
> Why is that?
> John
|||So, does that mean that the backups have not been successful?
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> Files are deleted after the next backup completes successfully.
> If you se a backup to delete after 1 day, and you don't run the actual
> backup job for 2 days, the backup will remain on disk for 2 days, until
> after the backup is successful.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "childofthe1980s" <childofthe1980s@.discussions.microsoft.com> wrote in
> message news:6E533D8D-A308-47F9-AC62-282987DBF849@.microsoft.com...
>
>
|||See this old post:-
http://groups.google.co.in/group/mic...141cc02159d2bc
Thanks
Hari
SQL Server MVP
"childofthe1980s" <childofthe1980s@.discussions.microsoft.com> wrote in
message news:262CAB61-803A-46BF-AA4A-CF5EC4AF8672@.microsoft.com...[vbcol=seagreen]
> So, does that mean that the backups have not been successful?
> "Mike Epprecht (SQL MVP)" wrote:
|||Hi
No. Look at the backup job logs to see what is going on.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"childofthe1980s" <childofthe1980s@.discussions.microsoft.com> wrote in
message news:262CAB61-803A-46BF-AA4A-CF5EC4AF8672@.microsoft.com...[vbcol=seagreen]
> So, does that mean that the backups have not been successful?
> "Mike Epprecht (SQL MVP)" wrote:
Showing posts with label transaction. Show all posts
Showing posts with label transaction. Show all posts
Thursday, March 29, 2012
Backup File Deletions not Working
Hi:
We configured a backup job in the database maintenance plan for a database
for both "Complete Backup" and the "Transaction Log". We told the job to
delete files after one day. It has not been deleting these files, though.
Why is that?
JohnHi
Files are deleted after the next backup completes successfully.
If you se a backup to delete after 1 day, and you don't run the actual
backup job for 2 days, the backup will remain on disk for 2 days, until
after the backup is successful.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"childofthe1980s" <childofthe1980s@.discussions.microsoft.com> wrote in
message news:6E533D8D-A308-47F9-AC62-282987DBF849@.microsoft.com...
> Hi:
> We configured a backup job in the database maintenance plan for a database
> for both "Complete Backup" and the "Transaction Log". We told the job to
> delete files after one day. It has not been deleting these files, though.
> Why is that?
> John|||So, does that mean that the backups have not been successful?
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> Files are deleted after the next backup completes successfully.
> If you se a backup to delete after 1 day, and you don't run the actual
> backup job for 2 days, the backup will remain on disk for 2 days, until
> after the backup is successful.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "childofthe1980s" <childofthe1980s@.discussions.microsoft.com> wrote in
> message news:6E533D8D-A308-47F9-AC62-282987DBF849@.microsoft.com...
>
>|||See this old post:-
http://groups.google.co.in/group/mi...4141cc02159d2bc
Thanks
Hari
SQL Server MVP
"childofthe1980s" <childofthe1980s@.discussions.microsoft.com> wrote in
message news:262CAB61-803A-46BF-AA4A-CF5EC4AF8672@.microsoft.com...[vbcol=seagreen]
> So, does that mean that the backups have not been successful?
> "Mike Epprecht (SQL MVP)" wrote:
>|||Hi
No. Look at the backup job logs to see what is going on.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"childofthe1980s" <childofthe1980s@.discussions.microsoft.com> wrote in
message news:262CAB61-803A-46BF-AA4A-CF5EC4AF8672@.microsoft.com...[vbcol=seagreen]
> So, does that mean that the backups have not been successful?
> "Mike Epprecht (SQL MVP)" wrote:
>
We configured a backup job in the database maintenance plan for a database
for both "Complete Backup" and the "Transaction Log". We told the job to
delete files after one day. It has not been deleting these files, though.
Why is that?
JohnHi
Files are deleted after the next backup completes successfully.
If you se a backup to delete after 1 day, and you don't run the actual
backup job for 2 days, the backup will remain on disk for 2 days, until
after the backup is successful.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"childofthe1980s" <childofthe1980s@.discussions.microsoft.com> wrote in
message news:6E533D8D-A308-47F9-AC62-282987DBF849@.microsoft.com...
> Hi:
> We configured a backup job in the database maintenance plan for a database
> for both "Complete Backup" and the "Transaction Log". We told the job to
> delete files after one day. It has not been deleting these files, though.
> Why is that?
> John|||So, does that mean that the backups have not been successful?
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> Files are deleted after the next backup completes successfully.
> If you se a backup to delete after 1 day, and you don't run the actual
> backup job for 2 days, the backup will remain on disk for 2 days, until
> after the backup is successful.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "childofthe1980s" <childofthe1980s@.discussions.microsoft.com> wrote in
> message news:6E533D8D-A308-47F9-AC62-282987DBF849@.microsoft.com...
>
>|||See this old post:-
http://groups.google.co.in/group/mi...4141cc02159d2bc
Thanks
Hari
SQL Server MVP
"childofthe1980s" <childofthe1980s@.discussions.microsoft.com> wrote in
message news:262CAB61-803A-46BF-AA4A-CF5EC4AF8672@.microsoft.com...[vbcol=seagreen]
> So, does that mean that the backups have not been successful?
> "Mike Epprecht (SQL MVP)" wrote:
>|||Hi
No. Look at the backup job logs to see what is going on.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"childofthe1980s" <childofthe1980s@.discussions.microsoft.com> wrote in
message news:262CAB61-803A-46BF-AA4A-CF5EC4AF8672@.microsoft.com...[vbcol=seagreen]
> So, does that mean that the backups have not been successful?
> "Mike Epprecht (SQL MVP)" wrote:
>
Backup File Deletions not Working
Hi:
We configured a backup job in the database maintenance plan for a database
for both "Complete Backup" and the "Transaction Log". We told the job to
delete files after one day. It has not been deleting these files, though.
Why is that?
JohnHi
Files are deleted after the next backup completes successfully.
If you se a backup to delete after 1 day, and you don't run the actual
backup job for 2 days, the backup will remain on disk for 2 days, until
after the backup is successful.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"childofthe1980s" <childofthe1980s@.discussions.microsoft.com> wrote in
message news:6E533D8D-A308-47F9-AC62-282987DBF849@.microsoft.com...
> Hi:
> We configured a backup job in the database maintenance plan for a database
> for both "Complete Backup" and the "Transaction Log". We told the job to
> delete files after one day. It has not been deleting these files, though.
> Why is that?
> John|||So, does that mean that the backups have not been successful?
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> Files are deleted after the next backup completes successfully.
> If you se a backup to delete after 1 day, and you don't run the actual
> backup job for 2 days, the backup will remain on disk for 2 days, until
> after the backup is successful.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "childofthe1980s" <childofthe1980s@.discussions.microsoft.com> wrote in
> message news:6E533D8D-A308-47F9-AC62-282987DBF849@.microsoft.com...
> > Hi:
> >
> > We configured a backup job in the database maintenance plan for a database
> > for both "Complete Backup" and the "Transaction Log". We told the job to
> > delete files after one day. It has not been deleting these files, though.
> >
> > Why is that?
> >
> > John
>
>|||See this old post:-
http://groups.google.co.in/group/microsoft.public.sqlserver.server/browse_thread/thread/f24fa621edb472b/04141cc02159d2bc?lnk=st&q=maintenance+plan+not+deleting+old+files&rnum=4&hl=en#04141cc02159d2bc
Thanks
Hari
SQL Server MVP
"childofthe1980s" <childofthe1980s@.discussions.microsoft.com> wrote in
message news:262CAB61-803A-46BF-AA4A-CF5EC4AF8672@.microsoft.com...
> So, does that mean that the backups have not been successful?
> "Mike Epprecht (SQL MVP)" wrote:
>> Hi
>> Files are deleted after the next backup completes successfully.
>> If you se a backup to delete after 1 day, and you don't run the actual
>> backup job for 2 days, the backup will remain on disk for 2 days, until
>> after the backup is successful.
>> Regards
>> --
>> Mike Epprecht, Microsoft SQL Server MVP
>> Zurich, Switzerland
>> IM: mike@.epprecht.net
>> MVP Program: http://www.microsoft.com/mvp
>> Blog: http://www.msmvps.com/epprecht/
>> "childofthe1980s" <childofthe1980s@.discussions.microsoft.com> wrote in
>> message news:6E533D8D-A308-47F9-AC62-282987DBF849@.microsoft.com...
>> > Hi:
>> >
>> > We configured a backup job in the database maintenance plan for a
>> > database
>> > for both "Complete Backup" and the "Transaction Log". We told the job
>> > to
>> > delete files after one day. It has not been deleting these files,
>> > though.
>> >
>> > Why is that?
>> >
>> > John
>>|||Hi
No. Look at the backup job logs to see what is going on.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"childofthe1980s" <childofthe1980s@.discussions.microsoft.com> wrote in
message news:262CAB61-803A-46BF-AA4A-CF5EC4AF8672@.microsoft.com...
> So, does that mean that the backups have not been successful?
> "Mike Epprecht (SQL MVP)" wrote:
>> Hi
>> Files are deleted after the next backup completes successfully.
>> If you se a backup to delete after 1 day, and you don't run the actual
>> backup job for 2 days, the backup will remain on disk for 2 days, until
>> after the backup is successful.
>> Regards
>> --
>> Mike Epprecht, Microsoft SQL Server MVP
>> Zurich, Switzerland
>> IM: mike@.epprecht.net
>> MVP Program: http://www.microsoft.com/mvp
>> Blog: http://www.msmvps.com/epprecht/
>> "childofthe1980s" <childofthe1980s@.discussions.microsoft.com> wrote in
>> message news:6E533D8D-A308-47F9-AC62-282987DBF849@.microsoft.com...
>> > Hi:
>> >
>> > We configured a backup job in the database maintenance plan for a
>> > database
>> > for both "Complete Backup" and the "Transaction Log". We told the job
>> > to
>> > delete files after one day. It has not been deleting these files,
>> > though.
>> >
>> > Why is that?
>> >
>> > John
>>
We configured a backup job in the database maintenance plan for a database
for both "Complete Backup" and the "Transaction Log". We told the job to
delete files after one day. It has not been deleting these files, though.
Why is that?
JohnHi
Files are deleted after the next backup completes successfully.
If you se a backup to delete after 1 day, and you don't run the actual
backup job for 2 days, the backup will remain on disk for 2 days, until
after the backup is successful.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"childofthe1980s" <childofthe1980s@.discussions.microsoft.com> wrote in
message news:6E533D8D-A308-47F9-AC62-282987DBF849@.microsoft.com...
> Hi:
> We configured a backup job in the database maintenance plan for a database
> for both "Complete Backup" and the "Transaction Log". We told the job to
> delete files after one day. It has not been deleting these files, though.
> Why is that?
> John|||So, does that mean that the backups have not been successful?
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> Files are deleted after the next backup completes successfully.
> If you se a backup to delete after 1 day, and you don't run the actual
> backup job for 2 days, the backup will remain on disk for 2 days, until
> after the backup is successful.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "childofthe1980s" <childofthe1980s@.discussions.microsoft.com> wrote in
> message news:6E533D8D-A308-47F9-AC62-282987DBF849@.microsoft.com...
> > Hi:
> >
> > We configured a backup job in the database maintenance plan for a database
> > for both "Complete Backup" and the "Transaction Log". We told the job to
> > delete files after one day. It has not been deleting these files, though.
> >
> > Why is that?
> >
> > John
>
>|||See this old post:-
http://groups.google.co.in/group/microsoft.public.sqlserver.server/browse_thread/thread/f24fa621edb472b/04141cc02159d2bc?lnk=st&q=maintenance+plan+not+deleting+old+files&rnum=4&hl=en#04141cc02159d2bc
Thanks
Hari
SQL Server MVP
"childofthe1980s" <childofthe1980s@.discussions.microsoft.com> wrote in
message news:262CAB61-803A-46BF-AA4A-CF5EC4AF8672@.microsoft.com...
> So, does that mean that the backups have not been successful?
> "Mike Epprecht (SQL MVP)" wrote:
>> Hi
>> Files are deleted after the next backup completes successfully.
>> If you se a backup to delete after 1 day, and you don't run the actual
>> backup job for 2 days, the backup will remain on disk for 2 days, until
>> after the backup is successful.
>> Regards
>> --
>> Mike Epprecht, Microsoft SQL Server MVP
>> Zurich, Switzerland
>> IM: mike@.epprecht.net
>> MVP Program: http://www.microsoft.com/mvp
>> Blog: http://www.msmvps.com/epprecht/
>> "childofthe1980s" <childofthe1980s@.discussions.microsoft.com> wrote in
>> message news:6E533D8D-A308-47F9-AC62-282987DBF849@.microsoft.com...
>> > Hi:
>> >
>> > We configured a backup job in the database maintenance plan for a
>> > database
>> > for both "Complete Backup" and the "Transaction Log". We told the job
>> > to
>> > delete files after one day. It has not been deleting these files,
>> > though.
>> >
>> > Why is that?
>> >
>> > John
>>|||Hi
No. Look at the backup job logs to see what is going on.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"childofthe1980s" <childofthe1980s@.discussions.microsoft.com> wrote in
message news:262CAB61-803A-46BF-AA4A-CF5EC4AF8672@.microsoft.com...
> So, does that mean that the backups have not been successful?
> "Mike Epprecht (SQL MVP)" wrote:
>> Hi
>> Files are deleted after the next backup completes successfully.
>> If you se a backup to delete after 1 day, and you don't run the actual
>> backup job for 2 days, the backup will remain on disk for 2 days, until
>> after the backup is successful.
>> Regards
>> --
>> Mike Epprecht, Microsoft SQL Server MVP
>> Zurich, Switzerland
>> IM: mike@.epprecht.net
>> MVP Program: http://www.microsoft.com/mvp
>> Blog: http://www.msmvps.com/epprecht/
>> "childofthe1980s" <childofthe1980s@.discussions.microsoft.com> wrote in
>> message news:6E533D8D-A308-47F9-AC62-282987DBF849@.microsoft.com...
>> > Hi:
>> >
>> > We configured a backup job in the database maintenance plan for a
>> > database
>> > for both "Complete Backup" and the "Transaction Log". We told the job
>> > to
>> > delete files after one day. It has not been deleting these files,
>> > though.
>> >
>> > Why is that?
>> >
>> > John
>>
backup failure
Hi
My DB backup and transaction backup of a database keep on failing with
the following error:
Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3202: [Microsoft][ODBC
SQL Server Driver][SQL Server]Write on
'E:\SqlServer\testdb_db_200604221313.BAK' failed, status = 112. See the
SQL Server error log for more details.
[Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP DATABASE is
terminating abnormally.
Any idea what it really means ?
Thanks
DavidYou can get the description of Win32 error codes with NET HELPMSG from a
command prompt:
My DB backup and transaction backup of a database keep on failing with
the following error:
Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3202: [Microsoft][ODBC
SQL Server Driver][SQL Server]Write on
'E:\SqlServer\testdb_db_200604221313.BAK' failed, status = 112. See the
SQL Server error log for more details.
[Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP DATABASE is
terminating abnormally.
Any idea what it really means ?
Thanks
DavidYou can get the description of Win32 error codes with NET HELPMSG from a
command prompt:
NET HELPMSG 112
Yields:
There is not enough space on the disk.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"David Greenberg" <davidgr@.iba.org.il> wrote in message
news:444B9239.2010804@.iba.org.il...
> Hi
> My DB backup and transaction backup of a database keep on failing with the
> following error:
> Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3202: [Microsoft][ODBC SQL
> Server Driver][SQL Server]Write on
> 'E:\SqlServer\testdb_db_200604221313.BAK' failed, status = 112. See the
> SQL Server error log for more details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP DATABASE is
> terminating abnormally.
> Any idea what it really means ?
> Thanks
> David
Monday, March 19, 2012
Backup Database remove inactive/replication
Does doing a transaction log backup with 'Remove inactive entries from
transaction log' option selected and shrinking database to free up space
affect replication in anyway?
Thanks
Gav
Gav,
merge is monitored using triggers so this isn't affected. Transactional will
remove only those commands read by the log reader agent (log is marked using
sp_repldone), otherwise it'll not truncate those commands. It might be that
the log reader agent will function faster having less records to filter by -
I have no way of knowing this without knowing the structure of the
transaction log and the query used. Certainly empirically I haven't noticed
a significant difference.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||Gav wrote:
> Does doing a transaction log backup with 'Remove inactive entries from
> transaction log' option selected and shrinking database to free up space
> affect replication in anyway?
> Thanks
> Gav
>
No, but the converse is true. Transactions cannot be flushed from the
log if they are waiting to be replicated, i.e. read by the LogReader agent.
Tracy McKibben
MCDBA
http://www.realsqlguy.com
|||Thanks for the fast reply
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:45A508CA.8060104@.realsqlguy.com...
> Gav wrote:
> No, but the converse is true. Transactions cannot be flushed from the log
> if they are waiting to be replicated, i.e. read by the LogReader agent.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
transaction log' option selected and shrinking database to free up space
affect replication in anyway?
Thanks
Gav
Gav,
merge is monitored using triggers so this isn't affected. Transactional will
remove only those commands read by the log reader agent (log is marked using
sp_repldone), otherwise it'll not truncate those commands. It might be that
the log reader agent will function faster having less records to filter by -
I have no way of knowing this without knowing the structure of the
transaction log and the query used. Certainly empirically I haven't noticed
a significant difference.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||Gav wrote:
> Does doing a transaction log backup with 'Remove inactive entries from
> transaction log' option selected and shrinking database to free up space
> affect replication in anyway?
> Thanks
> Gav
>
No, but the converse is true. Transactions cannot be flushed from the
log if they are waiting to be replicated, i.e. read by the LogReader agent.
Tracy McKibben
MCDBA
http://www.realsqlguy.com
|||Thanks for the fast reply
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:45A508CA.8060104@.realsqlguy.com...
> Gav wrote:
> No, but the converse is true. Transactions cannot be flushed from the log
> if they are waiting to be replicated, i.e. read by the LogReader agent.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
Backup Database remove inactive/replication
Does doing a transaction log backup with 'Remove inactive entries from
transaction log' option selected and shrinking database to free up space
affect replication in anyway?
Thanks
GavGav,
merge is monitored using triggers so this isn't affected. Transactional will
remove only those commands read by the log reader agent (log is marked using
sp_repldone), otherwise it'll not truncate those commands. It might be that
the log reader agent will function faster having less records to filter by -
I have no way of knowing this without knowing the structure of the
transaction log and the query used. Certainly empirically I haven't noticed
a significant difference.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .|||Gav wrote:
> Does doing a transaction log backup with 'Remove inactive entries from
> transaction log' option selected and shrinking database to free up space
> affect replication in anyway?
> Thanks
> Gav
>
No, but the converse is true. Transactions cannot be flushed from the
log if they are waiting to be replicated, i.e. read by the LogReader agent.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Thanks for the fast reply
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:45A508CA.8060104@.realsqlguy.com...
> Gav wrote:
>> Does doing a transaction log backup with 'Remove inactive entries from
>> transaction log' option selected and shrinking database to free up space
>> affect replication in anyway?
>> Thanks
>> Gav
> No, but the converse is true. Transactions cannot be flushed from the log
> if they are waiting to be replicated, i.e. read by the LogReader agent.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
transaction log' option selected and shrinking database to free up space
affect replication in anyway?
Thanks
GavGav,
merge is monitored using triggers so this isn't affected. Transactional will
remove only those commands read by the log reader agent (log is marked using
sp_repldone), otherwise it'll not truncate those commands. It might be that
the log reader agent will function faster having less records to filter by -
I have no way of knowing this without knowing the structure of the
transaction log and the query used. Certainly empirically I haven't noticed
a significant difference.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .|||Gav wrote:
> Does doing a transaction log backup with 'Remove inactive entries from
> transaction log' option selected and shrinking database to free up space
> affect replication in anyway?
> Thanks
> Gav
>
No, but the converse is true. Transactions cannot be flushed from the
log if they are waiting to be replicated, i.e. read by the LogReader agent.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Thanks for the fast reply
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:45A508CA.8060104@.realsqlguy.com...
> Gav wrote:
>> Does doing a transaction log backup with 'Remove inactive entries from
>> transaction log' option selected and shrinking database to free up space
>> affect replication in anyway?
>> Thanks
>> Gav
> No, but the converse is true. Transactions cannot be flushed from the log
> if they are waiting to be replicated, i.e. read by the LogReader agent.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
Backup Database remove inactive/replication
Does doing a transaction log backup with 'Remove inactive entries from
transaction log' option selected and shrinking database to free up space
affect replication in anyway?
Thanks
GavGav,
merge is monitored using triggers so this isn't affected. Transactional will
remove only those commands read by the log reader agent (log is marked using
sp_repldone), otherwise it'll not truncate those commands. It might be that
the log reader agent will function faster having less records to filter by -
I have no way of knowing this without knowing the structure of the
transaction log and the query used. Certainly empirically I haven't noticed
a significant difference.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .|||Gav wrote:
> Does doing a transaction log backup with 'Remove inactive entries from
> transaction log' option selected and shrinking database to free up space
> affect replication in anyway?
> Thanks
> Gav
>
No, but the converse is true. Transactions cannot be flushed from the
log if they are waiting to be replicated, i.e. read by the LogReader agent.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Thanks for the fast reply
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:45A508CA.8060104@.realsqlguy.com...
> Gav wrote:
> No, but the converse is true. Transactions cannot be flushed from the log
> if they are waiting to be replicated, i.e. read by the LogReader agent.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
transaction log' option selected and shrinking database to free up space
affect replication in anyway?
Thanks
GavGav,
merge is monitored using triggers so this isn't affected. Transactional will
remove only those commands read by the log reader agent (log is marked using
sp_repldone), otherwise it'll not truncate those commands. It might be that
the log reader agent will function faster having less records to filter by -
I have no way of knowing this without knowing the structure of the
transaction log and the query used. Certainly empirically I haven't noticed
a significant difference.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .|||Gav wrote:
> Does doing a transaction log backup with 'Remove inactive entries from
> transaction log' option selected and shrinking database to free up space
> affect replication in anyway?
> Thanks
> Gav
>
No, but the converse is true. Transactions cannot be flushed from the
log if they are waiting to be replicated, i.e. read by the LogReader agent.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Thanks for the fast reply
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:45A508CA.8060104@.realsqlguy.com...
> Gav wrote:
> No, but the converse is true. Transactions cannot be flushed from the log
> if they are waiting to be replicated, i.e. read by the LogReader agent.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
Sunday, March 11, 2012
Backup Database ?
Does the backup database command truncate the transaction log to the point
of the backup?
nivek
No
You must backup the log separately.
If you're using Simple Recovery model, use the backup log... with
truncate_only and then dbcc shrinkfile
to release disk back to the OS.
"nivek" <eckart_612@.hotmail.com> wrote in message
news:rI2dnf7GAuFAeqPfRVn-rQ@.centurytel.net...
> Does the backup database command truncate the transaction log to the point
> of the backup?
> --
> nivek
>
>
>
of the backup?
nivek
No
You must backup the log separately.
If you're using Simple Recovery model, use the backup log... with
truncate_only and then dbcc shrinkfile
to release disk back to the OS.
"nivek" <eckart_612@.hotmail.com> wrote in message
news:rI2dnf7GAuFAeqPfRVn-rQ@.centurytel.net...
> Does the backup database command truncate the transaction log to the point
> of the backup?
> --
> nivek
>
>
>
Backup Database ?
Does the backup database command truncate the transaction log to the point
of the backup?
--
nivekNo
You must backup the log separately.
If you're using Simple Recovery model, use the backup log... with
truncate_only and then dbcc shrinkfile
to release disk back to the OS.
"nivek" <eckart_612@.hotmail.com> wrote in message
news:rI2dnf7GAuFAeqPfRVn-rQ@.centurytel.net...
> Does the backup database command truncate the transaction log to the point
> of the backup?
> --
> nivek
>
>
>
of the backup?
--
nivekNo
You must backup the log separately.
If you're using Simple Recovery model, use the backup log... with
truncate_only and then dbcc shrinkfile
to release disk back to the OS.
"nivek" <eckart_612@.hotmail.com> wrote in message
news:rI2dnf7GAuFAeqPfRVn-rQ@.centurytel.net...
> Does the backup database command truncate the transaction log to the point
> of the backup?
> --
> nivek
>
>
>
Backup Database ?
Does the backup database command truncate the transaction log to the point
of the backup?
nivekNo
You must backup the log separately.
If you're using Simple Recovery model, use the backup log... with
truncate_only and then dbcc shrinkfile
to release disk back to the OS.
"nivek" <eckart_612@.hotmail.com> wrote in message
news:rI2dnf7GAuFAeqPfRVn-rQ@.centurytel.net...
> Does the backup database command truncate the transaction log to the point
> of the backup?
> --
> nivek
>
>
>
of the backup?
nivekNo
You must backup the log separately.
If you're using Simple Recovery model, use the backup log... with
truncate_only and then dbcc shrinkfile
to release disk back to the OS.
"nivek" <eckart_612@.hotmail.com> wrote in message
news:rI2dnf7GAuFAeqPfRVn-rQ@.centurytel.net...
> Does the backup database command truncate the transaction log to the point
> of the backup?
> --
> nivek
>
>
>
Thursday, March 8, 2012
Backup claims to have run, but there's no file
I have been trying to figure out why my transaction log backup task doesn't
seem to do anything. I changed the user account to SA, and now I see in the
logs that the task did run (no more account errors).
When I View Job History on the task, I see that it ran last night at 5AM as
I expected, and there's no errors. But there's no file!
Any ideas?
Maury
That's not much to go on but is there any chance the db is in Simple
Recovery mode?
Andrew J. Kelly SQL MVP
"Maury Markowitz" <MauryMarkowitz@.discussions.microsoft.com> wrote in
message news:4E2A71B7-814A-4DC8-98B3-0974F1778827@.microsoft.com...
>I have been trying to figure out why my transaction log backup task doesn't
> seem to do anything. I changed the user account to SA, and now I see in
> the
> logs that the task did run (no more account errors).
> When I View Job History on the task, I see that it ran last night at 5AM
> as
> I expected, and there's no errors. But there's no file!
> Any ideas?
> Maury
|||"Andrew J. Kelly" wrote:
> That's not much to go on but is there any chance the db is in Simple
> Recovery mode?
I can't tell you, I'm running '97 and Enterprise Manager doesn't say. Was
this even an option in earlier versions?
It would certainly make sense that this could cause the problem, I never
thought of it likely because I never saw the option while poking about!
After a little googling I note that the SQL Server Agent appearently resets
the server to Simple (assuming my server has this). This might be the problem
right there.
Maury
|||That's SQL Server 7.0 of course, not '97
|||In 7.0 it would not be called Simple mode. It would have Truncate Log on
ChkPoint I believe.
Andrew J. Kelly SQL MVP
"Maury Markowitz" <MauryMarkowitz@.discussions.microsoft.com> wrote in
message news:5BF9ADF5-4465-43C6-B090-36BDF0322629@.microsoft.com...
> That's SQL Server 7.0 of course, not '97
|||"Andrew J. Kelly" wrote:
> In 7.0 it would not be called Simple mode. It would have Truncate Log on
> ChkPoint I believe.
That option I do see. So I will turn this off and keep my fingers crossed.
BTW, what is a checkpoint, and when does it occur?
Maury
|||Look up CHECKPOINT in BooksOnLine for details.
Andrew J. Kelly SQL MVP
"Maury Markowitz" <MauryMarkowitz@.discussions.microsoft.com> wrote in
message news:14EEF517-A29E-40FA-983C-476E721FCD46@.microsoft.com...
> "Andrew J. Kelly" wrote:
> That option I do see. So I will turn this off and keep my fingers crossed.
> BTW, what is a checkpoint, and when does it occur?
> Maury
|||No luck so far...
I checked all of the log and error files (in /LOG), and don't see any
mention of a backup even running. I do, however, see an empty file for the
16th, the last time it ran.
I went into Enterprise Manager and after some poking about managed to find
the internal logs, the ones stored in the table. This did have an entry (so
why didn't the log file?!) for the 16th, which stated that "Backup can not be
performed on this database. This sub task is ignored", and said it
_succeeded_.
Either way, still no backup file!
This shouldn't be this confusing.
Maury
|||"Maury Markowitz" <MauryMarkowitz@.discussions.microsoft.com> wrote in
message news:28194502-6F72-4448-935B-E8DAE25CBCEA@.microsoft.com...
> No luck so far...
> I checked all of the log and error files (in /LOG), and don't see any
> mention of a backup even running. I do, however, see an empty file for the
> 16th, the last time it ran.
> I went into Enterprise Manager and after some poking about managed to find
> the internal logs, the ones stored in the table. This did have an entry
(so
> why didn't the log file?!) for the 16th, which stated that "Backup can not
be
> performed on this database. This sub task is ignored", and said it
> _succeeded_.
> Either way, still no backup file!
I missed it, is this a full or transaction log backup?
If it's a transaction log backup either your database may be in SIMPLE
recovery mode or a bulk insert has been done since the last full backup.
> This shouldn't be this confusing.
> Maury
|||"Greg D. Moore (Strider)" wrote:
> I missed it, is this a full or transaction log backup?
Transaction log.
> If it's a transaction log backup either your database may be in SIMPLE
> recovery mode or a bulk insert has been done since the last full backup.
There is no "simple" in 7.0, but I have turned off the confusingly-named
options that seem to imply transaction logs should now work.
The only bulk work we do is SELECT INTO on #temp tables. If THAT is the
cause of the problem, I can't imagine why -- bulks into temp tables should be
ignored for the purpose of transaction logging.
And if that is the cause, what is the solution? Diff backups prior to trans
backups?
Maury
seem to do anything. I changed the user account to SA, and now I see in the
logs that the task did run (no more account errors).
When I View Job History on the task, I see that it ran last night at 5AM as
I expected, and there's no errors. But there's no file!
Any ideas?
Maury
That's not much to go on but is there any chance the db is in Simple
Recovery mode?
Andrew J. Kelly SQL MVP
"Maury Markowitz" <MauryMarkowitz@.discussions.microsoft.com> wrote in
message news:4E2A71B7-814A-4DC8-98B3-0974F1778827@.microsoft.com...
>I have been trying to figure out why my transaction log backup task doesn't
> seem to do anything. I changed the user account to SA, and now I see in
> the
> logs that the task did run (no more account errors).
> When I View Job History on the task, I see that it ran last night at 5AM
> as
> I expected, and there's no errors. But there's no file!
> Any ideas?
> Maury
|||"Andrew J. Kelly" wrote:
> That's not much to go on but is there any chance the db is in Simple
> Recovery mode?
I can't tell you, I'm running '97 and Enterprise Manager doesn't say. Was
this even an option in earlier versions?
It would certainly make sense that this could cause the problem, I never
thought of it likely because I never saw the option while poking about!
After a little googling I note that the SQL Server Agent appearently resets
the server to Simple (assuming my server has this). This might be the problem
right there.
Maury
|||That's SQL Server 7.0 of course, not '97
|||In 7.0 it would not be called Simple mode. It would have Truncate Log on
ChkPoint I believe.
Andrew J. Kelly SQL MVP
"Maury Markowitz" <MauryMarkowitz@.discussions.microsoft.com> wrote in
message news:5BF9ADF5-4465-43C6-B090-36BDF0322629@.microsoft.com...
> That's SQL Server 7.0 of course, not '97
|||"Andrew J. Kelly" wrote:
> In 7.0 it would not be called Simple mode. It would have Truncate Log on
> ChkPoint I believe.
That option I do see. So I will turn this off and keep my fingers crossed.
BTW, what is a checkpoint, and when does it occur?
Maury
|||Look up CHECKPOINT in BooksOnLine for details.
Andrew J. Kelly SQL MVP
"Maury Markowitz" <MauryMarkowitz@.discussions.microsoft.com> wrote in
message news:14EEF517-A29E-40FA-983C-476E721FCD46@.microsoft.com...
> "Andrew J. Kelly" wrote:
> That option I do see. So I will turn this off and keep my fingers crossed.
> BTW, what is a checkpoint, and when does it occur?
> Maury
|||No luck so far...
I checked all of the log and error files (in /LOG), and don't see any
mention of a backup even running. I do, however, see an empty file for the
16th, the last time it ran.
I went into Enterprise Manager and after some poking about managed to find
the internal logs, the ones stored in the table. This did have an entry (so
why didn't the log file?!) for the 16th, which stated that "Backup can not be
performed on this database. This sub task is ignored", and said it
_succeeded_.
Either way, still no backup file!
This shouldn't be this confusing.
Maury
|||"Maury Markowitz" <MauryMarkowitz@.discussions.microsoft.com> wrote in
message news:28194502-6F72-4448-935B-E8DAE25CBCEA@.microsoft.com...
> No luck so far...
> I checked all of the log and error files (in /LOG), and don't see any
> mention of a backup even running. I do, however, see an empty file for the
> 16th, the last time it ran.
> I went into Enterprise Manager and after some poking about managed to find
> the internal logs, the ones stored in the table. This did have an entry
(so
> why didn't the log file?!) for the 16th, which stated that "Backup can not
be
> performed on this database. This sub task is ignored", and said it
> _succeeded_.
> Either way, still no backup file!
I missed it, is this a full or transaction log backup?
If it's a transaction log backup either your database may be in SIMPLE
recovery mode or a bulk insert has been done since the last full backup.
> This shouldn't be this confusing.
> Maury
|||"Greg D. Moore (Strider)" wrote:
> I missed it, is this a full or transaction log backup?
Transaction log.
> If it's a transaction log backup either your database may be in SIMPLE
> recovery mode or a bulk insert has been done since the last full backup.
There is no "simple" in 7.0, but I have turned off the confusingly-named
options that seem to imply transaction logs should now work.
The only bulk work we do is SELECT INTO on #temp tables. If THAT is the
cause of the problem, I can't imagine why -- bulks into temp tables should be
ignored for the purpose of transaction logging.
And if that is the cause, what is the solution? Diff backups prior to trans
backups?
Maury
Backup claims to have run, but there's no file
I have been trying to figure out why my transaction log backup task doesn't
seem to do anything. I changed the user account to SA, and now I see in the
logs that the task did run (no more account errors).
When I View Job History on the task, I see that it ran last night at 5AM as
I expected, and there's no errors. But there's no file!
Any ideas?
MauryThat's not much to go on but is there any chance the db is in Simple
Recovery mode?
--
Andrew J. Kelly SQL MVP
"Maury Markowitz" <MauryMarkowitz@.discussions.microsoft.com> wrote in
message news:4E2A71B7-814A-4DC8-98B3-0974F1778827@.microsoft.com...
>I have been trying to figure out why my transaction log backup task doesn't
> seem to do anything. I changed the user account to SA, and now I see in
> the
> logs that the task did run (no more account errors).
> When I View Job History on the task, I see that it ran last night at 5AM
> as
> I expected, and there's no errors. But there's no file!
> Any ideas?
> Maury|||"Andrew J. Kelly" wrote:
> That's not much to go on but is there any chance the db is in Simple
> Recovery mode?
I can't tell you, I'm running '97 and Enterprise Manager doesn't say. Was
this even an option in earlier versions?
It would certainly make sense that this could cause the problem, I never
thought of it likely because I never saw the option while poking about!
After a little googling I note that the SQL Server Agent appearently resets
the server to Simple (assuming my server has this). This might be the problem
right there.
Maury|||That's SQL Server 7.0 of course, not '97|||In 7.0 it would not be called Simple mode. It would have Truncate Log on
ChkPoint I believe.
--
Andrew J. Kelly SQL MVP
"Maury Markowitz" <MauryMarkowitz@.discussions.microsoft.com> wrote in
message news:5BF9ADF5-4465-43C6-B090-36BDF0322629@.microsoft.com...
> That's SQL Server 7.0 of course, not '97|||"Andrew J. Kelly" wrote:
> In 7.0 it would not be called Simple mode. It would have Truncate Log on
> ChkPoint I believe.
That option I do see. So I will turn this off and keep my fingers crossed.
BTW, what is a checkpoint, and when does it occur?
Maury|||Look up CHECKPOINT in BooksOnLine for details.
--
Andrew J. Kelly SQL MVP
"Maury Markowitz" <MauryMarkowitz@.discussions.microsoft.com> wrote in
message news:14EEF517-A29E-40FA-983C-476E721FCD46@.microsoft.com...
> "Andrew J. Kelly" wrote:
>> In 7.0 it would not be called Simple mode. It would have Truncate Log on
>> ChkPoint I believe.
> That option I do see. So I will turn this off and keep my fingers crossed.
> BTW, what is a checkpoint, and when does it occur?
> Maury|||No luck so far...
I checked all of the log and error files (in /LOG), and don't see any
mention of a backup even running. I do, however, see an empty file for the
16th, the last time it ran.
I went into Enterprise Manager and after some poking about managed to find
the internal logs, the ones stored in the table. This did have an entry (so
why didn't the log file?!) for the 16th, which stated that "Backup can not be
performed on this database. This sub task is ignored", and said it
_succeeded_.
Either way, still no backup file!
This shouldn't be this confusing.
Maury|||"Maury Markowitz" <MauryMarkowitz@.discussions.microsoft.com> wrote in
message news:28194502-6F72-4448-935B-E8DAE25CBCEA@.microsoft.com...
> No luck so far...
> I checked all of the log and error files (in /LOG), and don't see any
> mention of a backup even running. I do, however, see an empty file for the
> 16th, the last time it ran.
> I went into Enterprise Manager and after some poking about managed to find
> the internal logs, the ones stored in the table. This did have an entry
(so
> why didn't the log file?!) for the 16th, which stated that "Backup can not
be
> performed on this database. This sub task is ignored", and said it
> _succeeded_.
> Either way, still no backup file!
I missed it, is this a full or transaction log backup?
If it's a transaction log backup either your database may be in SIMPLE
recovery mode or a bulk insert has been done since the last full backup.
> This shouldn't be this confusing.
> Maury|||"Greg D. Moore (Strider)" wrote:
> > Either way, still no backup file!
> I missed it, is this a full or transaction log backup?
Transaction log.
> If it's a transaction log backup either your database may be in SIMPLE
> recovery mode or a bulk insert has been done since the last full backup.
There is no "simple" in 7.0, but I have turned off the confusingly-named
options that seem to imply transaction logs should now work.
The only bulk work we do is SELECT INTO on #temp tables. If THAT is the
cause of the problem, I can't imagine why -- bulks into temp tables should be
ignored for the purpose of transaction logging.
And if that is the cause, what is the solution? Diff backups prior to trans
backups?
Maury|||What is the setting of "SELECT INTO / BULKCOPY"? Try turning it off. It doesn't have to be on for
SELECTINTO into temp tables...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Maury Markowitz" <MauryMarkowitz@.discussions.microsoft.com> wrote in message
news:856788B4-5904-4027-89AD-CAFC5275009C@.microsoft.com...
> "Greg D. Moore (Strider)" wrote:
>> > Either way, still no backup file!
>> I missed it, is this a full or transaction log backup?
> Transaction log.
>> If it's a transaction log backup either your database may be in SIMPLE
>> recovery mode or a bulk insert has been done since the last full backup.
> There is no "simple" in 7.0, but I have turned off the confusingly-named
> options that seem to imply transaction logs should now work.
> The only bulk work we do is SELECT INTO on #temp tables. If THAT is the
> cause of the problem, I can't imagine why -- bulks into temp tables should be
> ignored for the purpose of transaction logging.
> And if that is the cause, what is the solution? Diff backups prior to trans
> backups?
> Maury
seem to do anything. I changed the user account to SA, and now I see in the
logs that the task did run (no more account errors).
When I View Job History on the task, I see that it ran last night at 5AM as
I expected, and there's no errors. But there's no file!
Any ideas?
MauryThat's not much to go on but is there any chance the db is in Simple
Recovery mode?
--
Andrew J. Kelly SQL MVP
"Maury Markowitz" <MauryMarkowitz@.discussions.microsoft.com> wrote in
message news:4E2A71B7-814A-4DC8-98B3-0974F1778827@.microsoft.com...
>I have been trying to figure out why my transaction log backup task doesn't
> seem to do anything. I changed the user account to SA, and now I see in
> the
> logs that the task did run (no more account errors).
> When I View Job History on the task, I see that it ran last night at 5AM
> as
> I expected, and there's no errors. But there's no file!
> Any ideas?
> Maury|||"Andrew J. Kelly" wrote:
> That's not much to go on but is there any chance the db is in Simple
> Recovery mode?
I can't tell you, I'm running '97 and Enterprise Manager doesn't say. Was
this even an option in earlier versions?
It would certainly make sense that this could cause the problem, I never
thought of it likely because I never saw the option while poking about!
After a little googling I note that the SQL Server Agent appearently resets
the server to Simple (assuming my server has this). This might be the problem
right there.
Maury|||That's SQL Server 7.0 of course, not '97|||In 7.0 it would not be called Simple mode. It would have Truncate Log on
ChkPoint I believe.
--
Andrew J. Kelly SQL MVP
"Maury Markowitz" <MauryMarkowitz@.discussions.microsoft.com> wrote in
message news:5BF9ADF5-4465-43C6-B090-36BDF0322629@.microsoft.com...
> That's SQL Server 7.0 of course, not '97|||"Andrew J. Kelly" wrote:
> In 7.0 it would not be called Simple mode. It would have Truncate Log on
> ChkPoint I believe.
That option I do see. So I will turn this off and keep my fingers crossed.
BTW, what is a checkpoint, and when does it occur?
Maury|||Look up CHECKPOINT in BooksOnLine for details.
--
Andrew J. Kelly SQL MVP
"Maury Markowitz" <MauryMarkowitz@.discussions.microsoft.com> wrote in
message news:14EEF517-A29E-40FA-983C-476E721FCD46@.microsoft.com...
> "Andrew J. Kelly" wrote:
>> In 7.0 it would not be called Simple mode. It would have Truncate Log on
>> ChkPoint I believe.
> That option I do see. So I will turn this off and keep my fingers crossed.
> BTW, what is a checkpoint, and when does it occur?
> Maury|||No luck so far...
I checked all of the log and error files (in /LOG), and don't see any
mention of a backup even running. I do, however, see an empty file for the
16th, the last time it ran.
I went into Enterprise Manager and after some poking about managed to find
the internal logs, the ones stored in the table. This did have an entry (so
why didn't the log file?!) for the 16th, which stated that "Backup can not be
performed on this database. This sub task is ignored", and said it
_succeeded_.
Either way, still no backup file!
This shouldn't be this confusing.
Maury|||"Maury Markowitz" <MauryMarkowitz@.discussions.microsoft.com> wrote in
message news:28194502-6F72-4448-935B-E8DAE25CBCEA@.microsoft.com...
> No luck so far...
> I checked all of the log and error files (in /LOG), and don't see any
> mention of a backup even running. I do, however, see an empty file for the
> 16th, the last time it ran.
> I went into Enterprise Manager and after some poking about managed to find
> the internal logs, the ones stored in the table. This did have an entry
(so
> why didn't the log file?!) for the 16th, which stated that "Backup can not
be
> performed on this database. This sub task is ignored", and said it
> _succeeded_.
> Either way, still no backup file!
I missed it, is this a full or transaction log backup?
If it's a transaction log backup either your database may be in SIMPLE
recovery mode or a bulk insert has been done since the last full backup.
> This shouldn't be this confusing.
> Maury|||"Greg D. Moore (Strider)" wrote:
> > Either way, still no backup file!
> I missed it, is this a full or transaction log backup?
Transaction log.
> If it's a transaction log backup either your database may be in SIMPLE
> recovery mode or a bulk insert has been done since the last full backup.
There is no "simple" in 7.0, but I have turned off the confusingly-named
options that seem to imply transaction logs should now work.
The only bulk work we do is SELECT INTO on #temp tables. If THAT is the
cause of the problem, I can't imagine why -- bulks into temp tables should be
ignored for the purpose of transaction logging.
And if that is the cause, what is the solution? Diff backups prior to trans
backups?
Maury|||What is the setting of "SELECT INTO / BULKCOPY"? Try turning it off. It doesn't have to be on for
SELECTINTO into temp tables...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Maury Markowitz" <MauryMarkowitz@.discussions.microsoft.com> wrote in message
news:856788B4-5904-4027-89AD-CAFC5275009C@.microsoft.com...
> "Greg D. Moore (Strider)" wrote:
>> > Either way, still no backup file!
>> I missed it, is this a full or transaction log backup?
> Transaction log.
>> If it's a transaction log backup either your database may be in SIMPLE
>> recovery mode or a bulk insert has been done since the last full backup.
> There is no "simple" in 7.0, but I have turned off the confusingly-named
> options that seem to imply transaction logs should now work.
> The only bulk work we do is SELECT INTO on #temp tables. If THAT is the
> cause of the problem, I can't imagine why -- bulks into temp tables should be
> ignored for the purpose of transaction logging.
> And if that is the cause, what is the solution? Diff backups prior to trans
> backups?
> Maury
Backup claims to have run, but there's no file
I have been trying to figure out why my transaction log backup task doesn't
seem to do anything. I changed the user account to SA, and now I see in the
logs that the task did run (no more account errors).
When I View Job History on the task, I see that it ran last night at 5AM as
I expected, and there's no errors. But there's no file!
Any ideas?
MauryThat's not much to go on but is there any chance the db is in Simple
Recovery mode?
Andrew J. Kelly SQL MVP
"Maury Markowitz" <MauryMarkowitz@.discussions.microsoft.com> wrote in
message news:4E2A71B7-814A-4DC8-98B3-0974F1778827@.microsoft.com...
>I have been trying to figure out why my transaction log backup task doesn't
> seem to do anything. I changed the user account to SA, and now I see in
> the
> logs that the task did run (no more account errors).
> When I View Job History on the task, I see that it ran last night at 5AM
> as
> I expected, and there's no errors. But there's no file!
> Any ideas?
> Maury|||"Andrew J. Kelly" wrote:
> That's not much to go on but is there any chance the db is in Simple
> Recovery mode?
I can't tell you, I'm running '97 and Enterprise Manager doesn't say. Was
this even an option in earlier versions?
It would certainly make sense that this could cause the problem, I never
thought of it likely because I never saw the option while poking about!
After a little googling I note that the SQL Server Agent appearently resets
the server to Simple (assuming my server has this). This might be the proble
m
right there.
Maury|||That's SQL Server 7.0 of course, not '97|||In 7.0 it would not be called Simple mode. It would have Truncate Log on
ChkPoint I believe.
Andrew J. Kelly SQL MVP
"Maury Markowitz" <MauryMarkowitz@.discussions.microsoft.com> wrote in
message news:5BF9ADF5-4465-43C6-B090-36BDF0322629@.microsoft.com...
> That's SQL Server 7.0 of course, not '97|||"Andrew J. Kelly" wrote:
> In 7.0 it would not be called Simple mode. It would have Truncate Log on
> ChkPoint I believe.
That option I do see. So I will turn this off and keep my fingers crossed.
BTW, what is a checkpoint, and when does it occur?
Maury|||Look up CHECKPOINT in BooksOnLine for details.
Andrew J. Kelly SQL MVP
"Maury Markowitz" <MauryMarkowitz@.discussions.microsoft.com> wrote in
message news:14EEF517-A29E-40FA-983C-476E721FCD46@.microsoft.com...
> "Andrew J. Kelly" wrote:
> That option I do see. So I will turn this off and keep my fingers crossed.
> BTW, what is a checkpoint, and when does it occur?
> Maury|||No luck so far...
I checked all of the log and error files (in /LOG), and don't see any
mention of a backup even running. I do, however, see an empty file for the
16th, the last time it ran.
I went into Enterprise Manager and after some poking about managed to find
the internal logs, the ones stored in the table. This did have an entry (so
why didn't the log file?!) for the 16th, which stated that "Backup can not b
e
performed on this database. This sub task is ignored", and said it
_succeeded_.
Either way, still no backup file!
This shouldn't be this confusing.
Maury|||"Maury Markowitz" <MauryMarkowitz@.discussions.microsoft.com> wrote in
message news:28194502-6F72-4448-935B-E8DAE25CBCEA@.microsoft.com...
> No luck so far...
> I checked all of the log and error files (in /LOG), and don't see any
> mention of a backup even running. I do, however, see an empty file for the
> 16th, the last time it ran.
> I went into Enterprise Manager and after some poking about managed to find
> the internal logs, the ones stored in the table. This did have an entry
(so
> why didn't the log file?!) for the 16th, which stated that "Backup can not
be
> performed on this database. This sub task is ignored", and said it
> _succeeded_.
> Either way, still no backup file!
I missed it, is this a full or transaction log backup?
If it's a transaction log backup either your database may be in SIMPLE
recovery mode or a bulk insert has been done since the last full backup.
> This shouldn't be this confusing.
> Maury|||"Greg D. Moore (Strider)" wrote:
> I missed it, is this a full or transaction log backup?
Transaction log.
> If it's a transaction log backup either your database may be in SIMPLE
> recovery mode or a bulk insert has been done since the last full backup.
There is no "simple" in 7.0, but I have turned off the confusingly-named
options that seem to imply transaction logs should now work.
The only bulk work we do is SELECT INTO on #temp tables. If THAT is the
cause of the problem, I can't imagine why -- bulks into temp tables should b
e
ignored for the purpose of transaction logging.
And if that is the cause, what is the solution? Diff backups prior to trans
backups?
Maury
seem to do anything. I changed the user account to SA, and now I see in the
logs that the task did run (no more account errors).
When I View Job History on the task, I see that it ran last night at 5AM as
I expected, and there's no errors. But there's no file!
Any ideas?
MauryThat's not much to go on but is there any chance the db is in Simple
Recovery mode?
Andrew J. Kelly SQL MVP
"Maury Markowitz" <MauryMarkowitz@.discussions.microsoft.com> wrote in
message news:4E2A71B7-814A-4DC8-98B3-0974F1778827@.microsoft.com...
>I have been trying to figure out why my transaction log backup task doesn't
> seem to do anything. I changed the user account to SA, and now I see in
> the
> logs that the task did run (no more account errors).
> When I View Job History on the task, I see that it ran last night at 5AM
> as
> I expected, and there's no errors. But there's no file!
> Any ideas?
> Maury|||"Andrew J. Kelly" wrote:
> That's not much to go on but is there any chance the db is in Simple
> Recovery mode?
I can't tell you, I'm running '97 and Enterprise Manager doesn't say. Was
this even an option in earlier versions?
It would certainly make sense that this could cause the problem, I never
thought of it likely because I never saw the option while poking about!
After a little googling I note that the SQL Server Agent appearently resets
the server to Simple (assuming my server has this). This might be the proble
m
right there.
Maury|||That's SQL Server 7.0 of course, not '97|||In 7.0 it would not be called Simple mode. It would have Truncate Log on
ChkPoint I believe.
Andrew J. Kelly SQL MVP
"Maury Markowitz" <MauryMarkowitz@.discussions.microsoft.com> wrote in
message news:5BF9ADF5-4465-43C6-B090-36BDF0322629@.microsoft.com...
> That's SQL Server 7.0 of course, not '97|||"Andrew J. Kelly" wrote:
> In 7.0 it would not be called Simple mode. It would have Truncate Log on
> ChkPoint I believe.
That option I do see. So I will turn this off and keep my fingers crossed.
BTW, what is a checkpoint, and when does it occur?
Maury|||Look up CHECKPOINT in BooksOnLine for details.
Andrew J. Kelly SQL MVP
"Maury Markowitz" <MauryMarkowitz@.discussions.microsoft.com> wrote in
message news:14EEF517-A29E-40FA-983C-476E721FCD46@.microsoft.com...
> "Andrew J. Kelly" wrote:
> That option I do see. So I will turn this off and keep my fingers crossed.
> BTW, what is a checkpoint, and when does it occur?
> Maury|||No luck so far...
I checked all of the log and error files (in /LOG), and don't see any
mention of a backup even running. I do, however, see an empty file for the
16th, the last time it ran.
I went into Enterprise Manager and after some poking about managed to find
the internal logs, the ones stored in the table. This did have an entry (so
why didn't the log file?!) for the 16th, which stated that "Backup can not b
e
performed on this database. This sub task is ignored", and said it
_succeeded_.
Either way, still no backup file!
This shouldn't be this confusing.
Maury|||"Maury Markowitz" <MauryMarkowitz@.discussions.microsoft.com> wrote in
message news:28194502-6F72-4448-935B-E8DAE25CBCEA@.microsoft.com...
> No luck so far...
> I checked all of the log and error files (in /LOG), and don't see any
> mention of a backup even running. I do, however, see an empty file for the
> 16th, the last time it ran.
> I went into Enterprise Manager and after some poking about managed to find
> the internal logs, the ones stored in the table. This did have an entry
(so
> why didn't the log file?!) for the 16th, which stated that "Backup can not
be
> performed on this database. This sub task is ignored", and said it
> _succeeded_.
> Either way, still no backup file!
I missed it, is this a full or transaction log backup?
If it's a transaction log backup either your database may be in SIMPLE
recovery mode or a bulk insert has been done since the last full backup.
> This shouldn't be this confusing.
> Maury|||"Greg D. Moore (Strider)" wrote:
> I missed it, is this a full or transaction log backup?
Transaction log.
> If it's a transaction log backup either your database may be in SIMPLE
> recovery mode or a bulk insert has been done since the last full backup.
There is no "simple" in 7.0, but I have turned off the confusingly-named
options that seem to imply transaction logs should now work.
The only bulk work we do is SELECT INTO on #temp tables. If THAT is the
cause of the problem, I can't imagine why -- bulks into temp tables should b
e
ignored for the purpose of transaction logging.
And if that is the cause, what is the solution? Diff backups prior to trans
backups?
Maury
Backup and zip the Transaction log file
Once the procedure is executed the database transaction log would be backed up and zipped with a blank text file which has the
the current date DD/MM/yyyy as the text file name
the current date DD/MM/yyyy as the text file name
exec ('exec master..xp_cmdshell ''dtsrun /SItchy /Usa /PF!gl@.59b#fl@.#f!uxr /N'+@.defaultCSVFeed_DTS+''' ')
exec ('exec master..xp_cmdshell ''E:\Inetpub\wwwroot\BIASS\wzzip.exe E:\Inetpub\wwwroot\'+@.SiteFolder+'\Admin\BIA_DataF eed\'+@.FileName+'.zip E:\Inetpub\wwwroot\'+@.SiteFolder+'\Admin\BIA_DataF eed\'+@.FileName+'.'+@.defaultCSVFeed_FileType+''' ')
Pls let me know how can i zip the backup file with a blank text file with the date as the file name of the blank text file...hey... its URGENT.... pls can anybody help me on this...... :(
Backup and zip the Transaction log file
Once the procedure is executed the database transaction log would be backed up and zipped with a blank text file which has the
the current date DD/MM/yyyy as the text file name
the current date DD/MM/yyyy as the text file name
exec ('exec master..xp_cmdshell ''dtsrun /SItchy /Usa /PF!gl@.59b#fl@.#f!uxr /N'+@.defaultCSVFeed_DTS+''' ')
exec ('exec master..xp_cmdshell ''E:\Inetpub\wwwroot\BIASS\wzzip.exe E:\Inetpub\wwwroot\'+@.SiteFolder+'\Admin\BIA_DataF eed\'+@.FileName+'.zip E:\Inetpub\wwwroot\'+@.SiteFolder+'\Admin\BIA_DataF eed\'+@.FileName+'.'+@.defaultCSVFeed_FileType+''' ')
Pls let me know how can i zip the backup file with a blank text file with the date as the file name of the blank text file...As you have posted a question in the articles section it is being moved to SQL Server Forum.
MODERATOR.
Friday, February 24, 2012
Backup and notify operator
We are using SQL Server 2005.
We do transaction backup every 15 minutes and we notify the operator by
email every time after the backup. So, there is a lot of emails the whole
day.
I am wondering if there is a way to only notify the operator only when there
is a problem with the backup.
Thank you.On Job Pproperties, Notifications, E-mail there are three choices. Perhaps
you are using 'When the job completes'. Select 'When the job fails' instead.
Hope this helps,
Ben Nevarez
"fniles" wrote:
> We are using SQL Server 2005.
> We do transaction backup every 15 minutes and we notify the operator by
> email every time after the backup. So, there is a lot of emails the whole
> day.
> I am wondering if there is a way to only notify the operator only when there
> is a problem with the backup.
> Thank you.
>
>|||Thank you.
When I right click - Edit on the Notify Operator Task, I only see "operators
to notify" and "notification message to send:"
I do not see the 3 choices. Is this because I am using SQL Server 2005
Developer version ?
"Ben Nevarez" <BenNevarez@.discussions.microsoft.com> wrote in message
news:C8F93DF7-A7AD-422E-8C02-3A818F0270D9@.microsoft.com...
> On Job Pproperties, Notifications, E-mail there are three choices. Perhaps
> you are using 'When the job completes'. Select 'When the job fails'
> instead.
> Hope this helps,
> Ben Nevarez
>
>
> "fniles" wrote:
>> We are using SQL Server 2005.
>> We do transaction backup every 15 minutes and we notify the operator by
>> email every time after the backup. So, there is a lot of emails the whole
>> day.
>> I am wondering if there is a way to only notify the operator only when
>> there
>> is a problem with the backup.
>> Thank you.
>>|||Developer Edition is fine. Go to Jobs, double-click your job, Notifications,
E-mail must be checked, on the right there is a list. Select the list.
Perhaps you are using 'When the job completes'. Select 'When the job fails'
instead.
Hope this helps,
Ben Nevarez
"fniles" wrote:
> Thank you.
> When I right click - Edit on the Notify Operator Task, I only see "operators
> to notify" and "notification message to send:"
> I do not see the 3 choices. Is this because I am using SQL Server 2005
> Developer version ?
> "Ben Nevarez" <BenNevarez@.discussions.microsoft.com> wrote in message
> news:C8F93DF7-A7AD-422E-8C02-3A818F0270D9@.microsoft.com...
> >
> > On Job Pproperties, Notifications, E-mail there are three choices. Perhaps
> > you are using 'When the job completes'. Select 'When the job fails'
> > instead.
> >
> > Hope this helps,
> >
> > Ben Nevarez
> >
> >
> >
> >
> > "fniles" wrote:
> >
> >> We are using SQL Server 2005.
> >> We do transaction backup every 15 minutes and we notify the operator by
> >> email every time after the backup. So, there is a lot of emails the whole
> >> day.
> >> I am wondering if there is a way to only notify the operator only when
> >> there
> >> is a problem with the backup.
> >> Thank you.
> >>
> >>
> >>
>
>|||It looks like you were referring to SQL 2000. I do see what you are
referring to in SQL 2000. I am using SQL 2005. I do not see "Jobs" in SQL
2005.
Do you know how I can do this in SQL 2005 ?
Thank you.
"Ben Nevarez" <BenNevarez@.discussions.microsoft.com> wrote in message
news:BC2F9E23-D44D-40C3-BB49-55910DA35015@.microsoft.com...
> Developer Edition is fine. Go to Jobs, double-click your job,
> Notifications,
> E-mail must be checked, on the right there is a list. Select the list.
> Perhaps you are using 'When the job completes'. Select 'When the job
> fails'
> instead.
> Hope this helps,
> Ben Nevarez
>
>
> "fniles" wrote:
>> Thank you.
>> When I right click - Edit on the Notify Operator Task, I only see
>> "operators
>> to notify" and "notification message to send:"
>> I do not see the 3 choices. Is this because I am using SQL Server 2005
>> Developer version ?
>> "Ben Nevarez" <BenNevarez@.discussions.microsoft.com> wrote in message
>> news:C8F93DF7-A7AD-422E-8C02-3A818F0270D9@.microsoft.com...
>> >
>> > On Job Pproperties, Notifications, E-mail there are three choices.
>> > Perhaps
>> > you are using 'When the job completes'. Select 'When the job fails'
>> > instead.
>> >
>> > Hope this helps,
>> >
>> > Ben Nevarez
>> >
>> >
>> >
>> >
>> > "fniles" wrote:
>> >
>> >> We are using SQL Server 2005.
>> >> We do transaction backup every 15 minutes and we notify the operator
>> >> by
>> >> email every time after the backup. So, there is a lot of emails the
>> >> whole
>> >> day.
>> >> I am wondering if there is a way to only notify the operator only when
>> >> there
>> >> is a problem with the backup.
>> >> Thank you.
>> >>
>> >>
>> >>
>>|||If I am understanding correctly what you have done, you have created a
maintenance plan in SQL 2005. In that maintenance plan (actually that
sub-plan), you have two tasks. The backup task and a notify operator
task, connected by a precedence constraint (green line with an arrow
pointing to the notify operator task).
If so, just right click on the precedence constraint and change it from
success to failure. Then, the notify operator task will only run when
the preceding task fails.
HTH,
Jeff
fniles wrote:
> It looks like you were referring to SQL 2000. I do see what you are
> referring to in SQL 2000. I am using SQL 2005. I do not see "Jobs" in SQL
> 2005.
> Do you know how I can do this in SQL 2005 ?
> Thank you.
> "Ben Nevarez" <BenNevarez@.discussions.microsoft.com> wrote in message
> news:BC2F9E23-D44D-40C3-BB49-55910DA35015@.microsoft.com...
>> Developer Edition is fine. Go to Jobs, double-click your job,
>> Notifications,
>> E-mail must be checked, on the right there is a list. Select the list.
>> Perhaps you are using 'When the job completes'. Select 'When the job
>> fails'
>> instead.
>> Hope this helps,
>> Ben Nevarez
>>
>>
>> "fniles" wrote:
>>
>> Thank you.
>> When I right click - Edit on the Notify Operator Task, I only see
>> "operators
>> to notify" and "notification message to send:"
>> I do not see the 3 choices. Is this because I am using SQL Server 2005
>> Developer version ?
>> "Ben Nevarez" <BenNevarez@.discussions.microsoft.com> wrote in message
>> news:C8F93DF7-A7AD-422E-8C02-3A818F0270D9@.microsoft.com...
>> On Job Pproperties, Notifications, E-mail there are three choices.
>> Perhaps
>> you are using 'When the job completes'. Select 'When the job fails'
>> instead.
>> Hope this helps,
>> Ben Nevarez
>>
>>
>> "fniles" wrote:
>>
>> We are using SQL Server 2005.
>> We do transaction backup every 15 minutes and we notify the operator
>> by
>> email every time after the backup. So, there is a lot of emails the
>> whole
>> day.
>> I am wondering if there is a way to only notify the operator only when
>> there
>> is a problem with the backup.
>> Thank you.
>>
>>
>>
>
>|||Thank you.
If I change it to failure, if the process only fail partially, will it
report it to the operator ?
"Jeffrey Williams" <jeff.williams3188@.verizon.net> wrote in message
news:e7uo%23IXVIHA.2368@.TK2MSFTNGP05.phx.gbl...
> If I am understanding correctly what you have done, you have created a
> maintenance plan in SQL 2005. In that maintenance plan (actually that
> sub-plan), you have two tasks. The backup task and a notify operator
> task, connected by a precedence constraint (green line with an arrow
> pointing to the notify operator task).
> If so, just right click on the precedence constraint and change it from
> success to failure. Then, the notify operator task will only run when the
> preceding task fails.
> HTH,
> Jeff
> fniles wrote:
>> It looks like you were referring to SQL 2000. I do see what you are
>> referring to in SQL 2000. I am using SQL 2005. I do not see "Jobs" in SQL
>> 2005.
>> Do you know how I can do this in SQL 2005 ?
>> Thank you.
>> "Ben Nevarez" <BenNevarez@.discussions.microsoft.com> wrote in message
>> news:BC2F9E23-D44D-40C3-BB49-55910DA35015@.microsoft.com...
>> Developer Edition is fine. Go to Jobs, double-click your job,
>> Notifications,
>> E-mail must be checked, on the right there is a list. Select the list.
>> Perhaps you are using 'When the job completes'. Select 'When the job
>> fails'
>> instead.
>> Hope this helps,
>> Ben Nevarez
>>
>>
>> "fniles" wrote:
>>
>> Thank you.
>> When I right click - Edit on the Notify Operator Task, I only see
>> "operators
>> to notify" and "notification message to send:"
>> I do not see the 3 choices. Is this because I am using SQL Server 2005
>> Developer version ?
>> "Ben Nevarez" <BenNevarez@.discussions.microsoft.com> wrote in message
>> news:C8F93DF7-A7AD-422E-8C02-3A818F0270D9@.microsoft.com...
>> On Job Pproperties, Notifications, E-mail there are three choices.
>> Perhaps
>> you are using 'When the job completes'. Select 'When the job fails'
>> instead.
>> Hope this helps,
>> Ben Nevarez
>>
>>
>> "fniles" wrote:
>>
>> We are using SQL Server 2005.
>> We do transaction backup every 15 minutes and we notify the operator
>> by
>> email every time after the backup. So, there is a lot of emails the
>> whole
>> day.
>> I am wondering if there is a way to only notify the operator only
>> when
>> there
>> is a problem with the backup.
>> Thank you.
>>
>>
>>
>>|||What do you mean by fail partially? Either the task completes
successfully, or the task fails - there is no partial failure.
But, if you have multiple tasks in the sub-plan and a single notify
operator task - with all tasks connected to the notify operator task on
failure the notify operator task will only fire if all tasks fail. To
get the notify operator task to fire if any one task fails you need to
right-click on one of the failure (red arrow) constraints and change
from AND to OR condition.
Or, you can add a separate notify operator task for each individual task
in the sub-plan. For example, you would have a Check Database Integrity
Task, Rebuild Index Task, Update Statistics, Backup Task and Cleanup
Task (connected in order on success) with a notify operator task
connected to the Database Integrity Task, a separate notify operator
task connected to the Rebuild Index Task, etc...
fniles wrote:
> Thank you.
> If I change it to failure, if the process only fail partially, will it
> report it to the operator ?
> "Jeffrey Williams" <jeff.williams3188@.verizon.net> wrote in message
> news:e7uo%23IXVIHA.2368@.TK2MSFTNGP05.phx.gbl...
>> If I am understanding correctly what you have done, you have created a
>> maintenance plan in SQL 2005. In that maintenance plan (actually that
>> sub-plan), you have two tasks. The backup task and a notify operator
>> task, connected by a precedence constraint (green line with an arrow
>> pointing to the notify operator task).
>> If so, just right click on the precedence constraint and change it from
>> success to failure. Then, the notify operator task will only run when the
>> preceding task fails.
>> HTH,
>> Jeff
>> fniles wrote:
>> It looks like you were referring to SQL 2000. I do see what you are
>> referring to in SQL 2000. I am using SQL 2005. I do not see "Jobs" in SQL
>> 2005.
>> Do you know how I can do this in SQL 2005 ?
>> Thank you.
>> "Ben Nevarez" <BenNevarez@.discussions.microsoft.com> wrote in message
>> news:BC2F9E23-D44D-40C3-BB49-55910DA35015@.microsoft.com...
>>
>> Developer Edition is fine. Go to Jobs, double-click your job,
>> Notifications,
>> E-mail must be checked, on the right there is a list. Select the list.
>> Perhaps you are using 'When the job completes'. Select 'When the job
>> fails'
>> instead.
>> Hope this helps,
>> Ben Nevarez
>>
>>
>> "fniles" wrote:
>>
>> Thank you.
>> When I right click - Edit on the Notify Operator Task, I only see
>> "operators
>> to notify" and "notification message to send:"
>> I do not see the 3 choices. Is this because I am using SQL Server 2005
>> Developer version ?
>> "Ben Nevarez" <BenNevarez@.discussions.microsoft.com> wrote in message
>> news:C8F93DF7-A7AD-422E-8C02-3A818F0270D9@.microsoft.com...
>>
>> On Job Pproperties, Notifications, E-mail there are three choices.
>> Perhaps
>> you are using 'When the job completes'. Select 'When the job fails'
>> instead.
>> Hope this helps,
>> Ben Nevarez
>>
>>
>> "fniles" wrote:
>>
>>> We are using SQL Server 2005.
>>> We do transaction backup every 15 minutes and we notify the operator
>>> by
>>> email every time after the backup. So, there is a lot of emails the
>>> whole
>>> day.
>>> I am wondering if there is a way to only notify the operator only
>>> when
>>> there
>>> is a problem with the backup.
>>> Thank you.
>>>
>>>
>>>
>>>
>>>
>>
>
>
We do transaction backup every 15 minutes and we notify the operator by
email every time after the backup. So, there is a lot of emails the whole
day.
I am wondering if there is a way to only notify the operator only when there
is a problem with the backup.
Thank you.On Job Pproperties, Notifications, E-mail there are three choices. Perhaps
you are using 'When the job completes'. Select 'When the job fails' instead.
Hope this helps,
Ben Nevarez
"fniles" wrote:
> We are using SQL Server 2005.
> We do transaction backup every 15 minutes and we notify the operator by
> email every time after the backup. So, there is a lot of emails the whole
> day.
> I am wondering if there is a way to only notify the operator only when there
> is a problem with the backup.
> Thank you.
>
>|||Thank you.
When I right click - Edit on the Notify Operator Task, I only see "operators
to notify" and "notification message to send:"
I do not see the 3 choices. Is this because I am using SQL Server 2005
Developer version ?
"Ben Nevarez" <BenNevarez@.discussions.microsoft.com> wrote in message
news:C8F93DF7-A7AD-422E-8C02-3A818F0270D9@.microsoft.com...
> On Job Pproperties, Notifications, E-mail there are three choices. Perhaps
> you are using 'When the job completes'. Select 'When the job fails'
> instead.
> Hope this helps,
> Ben Nevarez
>
>
> "fniles" wrote:
>> We are using SQL Server 2005.
>> We do transaction backup every 15 minutes and we notify the operator by
>> email every time after the backup. So, there is a lot of emails the whole
>> day.
>> I am wondering if there is a way to only notify the operator only when
>> there
>> is a problem with the backup.
>> Thank you.
>>|||Developer Edition is fine. Go to Jobs, double-click your job, Notifications,
E-mail must be checked, on the right there is a list. Select the list.
Perhaps you are using 'When the job completes'. Select 'When the job fails'
instead.
Hope this helps,
Ben Nevarez
"fniles" wrote:
> Thank you.
> When I right click - Edit on the Notify Operator Task, I only see "operators
> to notify" and "notification message to send:"
> I do not see the 3 choices. Is this because I am using SQL Server 2005
> Developer version ?
> "Ben Nevarez" <BenNevarez@.discussions.microsoft.com> wrote in message
> news:C8F93DF7-A7AD-422E-8C02-3A818F0270D9@.microsoft.com...
> >
> > On Job Pproperties, Notifications, E-mail there are three choices. Perhaps
> > you are using 'When the job completes'. Select 'When the job fails'
> > instead.
> >
> > Hope this helps,
> >
> > Ben Nevarez
> >
> >
> >
> >
> > "fniles" wrote:
> >
> >> We are using SQL Server 2005.
> >> We do transaction backup every 15 minutes and we notify the operator by
> >> email every time after the backup. So, there is a lot of emails the whole
> >> day.
> >> I am wondering if there is a way to only notify the operator only when
> >> there
> >> is a problem with the backup.
> >> Thank you.
> >>
> >>
> >>
>
>|||It looks like you were referring to SQL 2000. I do see what you are
referring to in SQL 2000. I am using SQL 2005. I do not see "Jobs" in SQL
2005.
Do you know how I can do this in SQL 2005 ?
Thank you.
"Ben Nevarez" <BenNevarez@.discussions.microsoft.com> wrote in message
news:BC2F9E23-D44D-40C3-BB49-55910DA35015@.microsoft.com...
> Developer Edition is fine. Go to Jobs, double-click your job,
> Notifications,
> E-mail must be checked, on the right there is a list. Select the list.
> Perhaps you are using 'When the job completes'. Select 'When the job
> fails'
> instead.
> Hope this helps,
> Ben Nevarez
>
>
> "fniles" wrote:
>> Thank you.
>> When I right click - Edit on the Notify Operator Task, I only see
>> "operators
>> to notify" and "notification message to send:"
>> I do not see the 3 choices. Is this because I am using SQL Server 2005
>> Developer version ?
>> "Ben Nevarez" <BenNevarez@.discussions.microsoft.com> wrote in message
>> news:C8F93DF7-A7AD-422E-8C02-3A818F0270D9@.microsoft.com...
>> >
>> > On Job Pproperties, Notifications, E-mail there are three choices.
>> > Perhaps
>> > you are using 'When the job completes'. Select 'When the job fails'
>> > instead.
>> >
>> > Hope this helps,
>> >
>> > Ben Nevarez
>> >
>> >
>> >
>> >
>> > "fniles" wrote:
>> >
>> >> We are using SQL Server 2005.
>> >> We do transaction backup every 15 minutes and we notify the operator
>> >> by
>> >> email every time after the backup. So, there is a lot of emails the
>> >> whole
>> >> day.
>> >> I am wondering if there is a way to only notify the operator only when
>> >> there
>> >> is a problem with the backup.
>> >> Thank you.
>> >>
>> >>
>> >>
>>|||If I am understanding correctly what you have done, you have created a
maintenance plan in SQL 2005. In that maintenance plan (actually that
sub-plan), you have two tasks. The backup task and a notify operator
task, connected by a precedence constraint (green line with an arrow
pointing to the notify operator task).
If so, just right click on the precedence constraint and change it from
success to failure. Then, the notify operator task will only run when
the preceding task fails.
HTH,
Jeff
fniles wrote:
> It looks like you were referring to SQL 2000. I do see what you are
> referring to in SQL 2000. I am using SQL 2005. I do not see "Jobs" in SQL
> 2005.
> Do you know how I can do this in SQL 2005 ?
> Thank you.
> "Ben Nevarez" <BenNevarez@.discussions.microsoft.com> wrote in message
> news:BC2F9E23-D44D-40C3-BB49-55910DA35015@.microsoft.com...
>> Developer Edition is fine. Go to Jobs, double-click your job,
>> Notifications,
>> E-mail must be checked, on the right there is a list. Select the list.
>> Perhaps you are using 'When the job completes'. Select 'When the job
>> fails'
>> instead.
>> Hope this helps,
>> Ben Nevarez
>>
>>
>> "fniles" wrote:
>>
>> Thank you.
>> When I right click - Edit on the Notify Operator Task, I only see
>> "operators
>> to notify" and "notification message to send:"
>> I do not see the 3 choices. Is this because I am using SQL Server 2005
>> Developer version ?
>> "Ben Nevarez" <BenNevarez@.discussions.microsoft.com> wrote in message
>> news:C8F93DF7-A7AD-422E-8C02-3A818F0270D9@.microsoft.com...
>> On Job Pproperties, Notifications, E-mail there are three choices.
>> Perhaps
>> you are using 'When the job completes'. Select 'When the job fails'
>> instead.
>> Hope this helps,
>> Ben Nevarez
>>
>>
>> "fniles" wrote:
>>
>> We are using SQL Server 2005.
>> We do transaction backup every 15 minutes and we notify the operator
>> by
>> email every time after the backup. So, there is a lot of emails the
>> whole
>> day.
>> I am wondering if there is a way to only notify the operator only when
>> there
>> is a problem with the backup.
>> Thank you.
>>
>>
>>
>
>|||Thank you.
If I change it to failure, if the process only fail partially, will it
report it to the operator ?
"Jeffrey Williams" <jeff.williams3188@.verizon.net> wrote in message
news:e7uo%23IXVIHA.2368@.TK2MSFTNGP05.phx.gbl...
> If I am understanding correctly what you have done, you have created a
> maintenance plan in SQL 2005. In that maintenance plan (actually that
> sub-plan), you have two tasks. The backup task and a notify operator
> task, connected by a precedence constraint (green line with an arrow
> pointing to the notify operator task).
> If so, just right click on the precedence constraint and change it from
> success to failure. Then, the notify operator task will only run when the
> preceding task fails.
> HTH,
> Jeff
> fniles wrote:
>> It looks like you were referring to SQL 2000. I do see what you are
>> referring to in SQL 2000. I am using SQL 2005. I do not see "Jobs" in SQL
>> 2005.
>> Do you know how I can do this in SQL 2005 ?
>> Thank you.
>> "Ben Nevarez" <BenNevarez@.discussions.microsoft.com> wrote in message
>> news:BC2F9E23-D44D-40C3-BB49-55910DA35015@.microsoft.com...
>> Developer Edition is fine. Go to Jobs, double-click your job,
>> Notifications,
>> E-mail must be checked, on the right there is a list. Select the list.
>> Perhaps you are using 'When the job completes'. Select 'When the job
>> fails'
>> instead.
>> Hope this helps,
>> Ben Nevarez
>>
>>
>> "fniles" wrote:
>>
>> Thank you.
>> When I right click - Edit on the Notify Operator Task, I only see
>> "operators
>> to notify" and "notification message to send:"
>> I do not see the 3 choices. Is this because I am using SQL Server 2005
>> Developer version ?
>> "Ben Nevarez" <BenNevarez@.discussions.microsoft.com> wrote in message
>> news:C8F93DF7-A7AD-422E-8C02-3A818F0270D9@.microsoft.com...
>> On Job Pproperties, Notifications, E-mail there are three choices.
>> Perhaps
>> you are using 'When the job completes'. Select 'When the job fails'
>> instead.
>> Hope this helps,
>> Ben Nevarez
>>
>>
>> "fniles" wrote:
>>
>> We are using SQL Server 2005.
>> We do transaction backup every 15 minutes and we notify the operator
>> by
>> email every time after the backup. So, there is a lot of emails the
>> whole
>> day.
>> I am wondering if there is a way to only notify the operator only
>> when
>> there
>> is a problem with the backup.
>> Thank you.
>>
>>
>>
>>|||What do you mean by fail partially? Either the task completes
successfully, or the task fails - there is no partial failure.
But, if you have multiple tasks in the sub-plan and a single notify
operator task - with all tasks connected to the notify operator task on
failure the notify operator task will only fire if all tasks fail. To
get the notify operator task to fire if any one task fails you need to
right-click on one of the failure (red arrow) constraints and change
from AND to OR condition.
Or, you can add a separate notify operator task for each individual task
in the sub-plan. For example, you would have a Check Database Integrity
Task, Rebuild Index Task, Update Statistics, Backup Task and Cleanup
Task (connected in order on success) with a notify operator task
connected to the Database Integrity Task, a separate notify operator
task connected to the Rebuild Index Task, etc...
fniles wrote:
> Thank you.
> If I change it to failure, if the process only fail partially, will it
> report it to the operator ?
> "Jeffrey Williams" <jeff.williams3188@.verizon.net> wrote in message
> news:e7uo%23IXVIHA.2368@.TK2MSFTNGP05.phx.gbl...
>> If I am understanding correctly what you have done, you have created a
>> maintenance plan in SQL 2005. In that maintenance plan (actually that
>> sub-plan), you have two tasks. The backup task and a notify operator
>> task, connected by a precedence constraint (green line with an arrow
>> pointing to the notify operator task).
>> If so, just right click on the precedence constraint and change it from
>> success to failure. Then, the notify operator task will only run when the
>> preceding task fails.
>> HTH,
>> Jeff
>> fniles wrote:
>> It looks like you were referring to SQL 2000. I do see what you are
>> referring to in SQL 2000. I am using SQL 2005. I do not see "Jobs" in SQL
>> 2005.
>> Do you know how I can do this in SQL 2005 ?
>> Thank you.
>> "Ben Nevarez" <BenNevarez@.discussions.microsoft.com> wrote in message
>> news:BC2F9E23-D44D-40C3-BB49-55910DA35015@.microsoft.com...
>>
>> Developer Edition is fine. Go to Jobs, double-click your job,
>> Notifications,
>> E-mail must be checked, on the right there is a list. Select the list.
>> Perhaps you are using 'When the job completes'. Select 'When the job
>> fails'
>> instead.
>> Hope this helps,
>> Ben Nevarez
>>
>>
>> "fniles" wrote:
>>
>> Thank you.
>> When I right click - Edit on the Notify Operator Task, I only see
>> "operators
>> to notify" and "notification message to send:"
>> I do not see the 3 choices. Is this because I am using SQL Server 2005
>> Developer version ?
>> "Ben Nevarez" <BenNevarez@.discussions.microsoft.com> wrote in message
>> news:C8F93DF7-A7AD-422E-8C02-3A818F0270D9@.microsoft.com...
>>
>> On Job Pproperties, Notifications, E-mail there are three choices.
>> Perhaps
>> you are using 'When the job completes'. Select 'When the job fails'
>> instead.
>> Hope this helps,
>> Ben Nevarez
>>
>>
>> "fniles" wrote:
>>
>>> We are using SQL Server 2005.
>>> We do transaction backup every 15 minutes and we notify the operator
>>> by
>>> email every time after the backup. So, there is a lot of emails the
>>> whole
>>> day.
>>> I am wondering if there is a way to only notify the operator only
>>> when
>>> there
>>> is a problem with the backup.
>>> Thank you.
>>>
>>>
>>>
>>>
>>>
>>
>
>
Backup and notify operator
We are using SQL Server 2005.
We do transaction backup every 15 minutes and we notify the operator by
email every time after the backup. So, there is a lot of emails the whole
day.
I am wondering if there is a way to only notify the operator only when there
is a problem with the backup.
Thank you.
On Job Pproperties, Notifications, E-mail there are three choices. Perhaps
you are using 'When the job completes'. Select 'When the job fails' instead.
Hope this helps,
Ben Nevarez
"fniles" wrote:
> We are using SQL Server 2005.
> We do transaction backup every 15 minutes and we notify the operator by
> email every time after the backup. So, there is a lot of emails the whole
> day.
> I am wondering if there is a way to only notify the operator only when there
> is a problem with the backup.
> Thank you.
>
>
|||Thank you.
When I right click - Edit on the Notify Operator Task, I only see "operators
to notify" and "notification message to send:"
I do not see the 3 choices. Is this because I am using SQL Server 2005
Developer version ?
"Ben Nevarez" <BenNevarez@.discussions.microsoft.com> wrote in message
news:C8F93DF7-A7AD-422E-8C02-3A818F0270D9@.microsoft.com...[vbcol=seagreen]
> On Job Pproperties, Notifications, E-mail there are three choices. Perhaps
> you are using 'When the job completes'. Select 'When the job fails'
> instead.
> Hope this helps,
> Ben Nevarez
>
>
> "fniles" wrote:
|||Developer Edition is fine. Go to Jobs, double-click your job, Notifications,
E-mail must be checked, on the right there is a list. Select the list.
Perhaps you are using 'When the job completes'. Select 'When the job fails'
instead.
Hope this helps,
Ben Nevarez
"fniles" wrote:
> Thank you.
> When I right click - Edit on the Notify Operator Task, I only see "operators
> to notify" and "notification message to send:"
> I do not see the 3 choices. Is this because I am using SQL Server 2005
> Developer version ?
> "Ben Nevarez" <BenNevarez@.discussions.microsoft.com> wrote in message
> news:C8F93DF7-A7AD-422E-8C02-3A818F0270D9@.microsoft.com...
>
>
|||It looks like you were referring to SQL 2000. I do see what you are
referring to in SQL 2000. I am using SQL 2005. I do not see "Jobs" in SQL
2005.
Do you know how I can do this in SQL 2005 ?
Thank you.
"Ben Nevarez" <BenNevarez@.discussions.microsoft.com> wrote in message
news:BC2F9E23-D44D-40C3-BB49-55910DA35015@.microsoft.com...[vbcol=seagreen]
> Developer Edition is fine. Go to Jobs, double-click your job,
> Notifications,
> E-mail must be checked, on the right there is a list. Select the list.
> Perhaps you are using 'When the job completes'. Select 'When the job
> fails'
> instead.
> Hope this helps,
> Ben Nevarez
>
>
> "fniles" wrote:
|||If I am understanding correctly what you have done, you have created a
maintenance plan in SQL 2005. In that maintenance plan (actually that
sub-plan), you have two tasks. The backup task and a notify operator
task, connected by a precedence constraint (green line with an arrow
pointing to the notify operator task).
If so, just right click on the precedence constraint and change it from
success to failure. Then, the notify operator task will only run when
the preceding task fails.
HTH,
Jeff
fniles wrote:
> It looks like you were referring to SQL 2000. I do see what you are
> referring to in SQL 2000. I am using SQL 2005. I do not see "Jobs" in SQL
> 2005.
> Do you know how I can do this in SQL 2005 ?
> Thank you.
> "Ben Nevarez" <BenNevarez@.discussions.microsoft.com> wrote in message
> news:BC2F9E23-D44D-40C3-BB49-55910DA35015@.microsoft.com...
>
>
|||Thank you.
If I change it to failure, if the process only fail partially, will it
report it to the operator ?
"Jeffrey Williams" <jeff.williams3188@.verizon.net> wrote in message
news:e7uo%23IXVIHA.2368@.TK2MSFTNGP05.phx.gbl...[vbcol=seagreen]
> If I am understanding correctly what you have done, you have created a
> maintenance plan in SQL 2005. In that maintenance plan (actually that
> sub-plan), you have two tasks. The backup task and a notify operator
> task, connected by a precedence constraint (green line with an arrow
> pointing to the notify operator task).
> If so, just right click on the precedence constraint and change it from
> success to failure. Then, the notify operator task will only run when the
> preceding task fails.
> HTH,
> Jeff
> fniles wrote:
|||What do you mean by fail partially? Either the task completes
successfully, or the task fails - there is no partial failure.
But, if you have multiple tasks in the sub-plan and a single notify
operator task - with all tasks connected to the notify operator task on
failure the notify operator task will only fire if all tasks fail. To
get the notify operator task to fire if any one task fails you need to
right-click on one of the failure (red arrow) constraints and change
from AND to OR condition.
Or, you can add a separate notify operator task for each individual task
in the sub-plan. For example, you would have a Check Database Integrity
Task, Rebuild Index Task, Update Statistics, Backup Task and Cleanup
Task (connected in order on success) with a notify operator task
connected to the Database Integrity Task, a separate notify operator
task connected to the Rebuild Index Task, etc...
fniles wrote:
> Thank you.
> If I change it to failure, if the process only fail partially, will it
> report it to the operator ?
> "Jeffrey Williams" <jeff.williams3188@.verizon.net> wrote in message
> news:e7uo%23IXVIHA.2368@.TK2MSFTNGP05.phx.gbl...
>
>
We do transaction backup every 15 minutes and we notify the operator by
email every time after the backup. So, there is a lot of emails the whole
day.
I am wondering if there is a way to only notify the operator only when there
is a problem with the backup.
Thank you.
On Job Pproperties, Notifications, E-mail there are three choices. Perhaps
you are using 'When the job completes'. Select 'When the job fails' instead.
Hope this helps,
Ben Nevarez
"fniles" wrote:
> We are using SQL Server 2005.
> We do transaction backup every 15 minutes and we notify the operator by
> email every time after the backup. So, there is a lot of emails the whole
> day.
> I am wondering if there is a way to only notify the operator only when there
> is a problem with the backup.
> Thank you.
>
>
|||Thank you.
When I right click - Edit on the Notify Operator Task, I only see "operators
to notify" and "notification message to send:"
I do not see the 3 choices. Is this because I am using SQL Server 2005
Developer version ?
"Ben Nevarez" <BenNevarez@.discussions.microsoft.com> wrote in message
news:C8F93DF7-A7AD-422E-8C02-3A818F0270D9@.microsoft.com...[vbcol=seagreen]
> On Job Pproperties, Notifications, E-mail there are three choices. Perhaps
> you are using 'When the job completes'. Select 'When the job fails'
> instead.
> Hope this helps,
> Ben Nevarez
>
>
> "fniles" wrote:
|||Developer Edition is fine. Go to Jobs, double-click your job, Notifications,
E-mail must be checked, on the right there is a list. Select the list.
Perhaps you are using 'When the job completes'. Select 'When the job fails'
instead.
Hope this helps,
Ben Nevarez
"fniles" wrote:
> Thank you.
> When I right click - Edit on the Notify Operator Task, I only see "operators
> to notify" and "notification message to send:"
> I do not see the 3 choices. Is this because I am using SQL Server 2005
> Developer version ?
> "Ben Nevarez" <BenNevarez@.discussions.microsoft.com> wrote in message
> news:C8F93DF7-A7AD-422E-8C02-3A818F0270D9@.microsoft.com...
>
>
|||It looks like you were referring to SQL 2000. I do see what you are
referring to in SQL 2000. I am using SQL 2005. I do not see "Jobs" in SQL
2005.
Do you know how I can do this in SQL 2005 ?
Thank you.
"Ben Nevarez" <BenNevarez@.discussions.microsoft.com> wrote in message
news:BC2F9E23-D44D-40C3-BB49-55910DA35015@.microsoft.com...[vbcol=seagreen]
> Developer Edition is fine. Go to Jobs, double-click your job,
> Notifications,
> E-mail must be checked, on the right there is a list. Select the list.
> Perhaps you are using 'When the job completes'. Select 'When the job
> fails'
> instead.
> Hope this helps,
> Ben Nevarez
>
>
> "fniles" wrote:
|||If I am understanding correctly what you have done, you have created a
maintenance plan in SQL 2005. In that maintenance plan (actually that
sub-plan), you have two tasks. The backup task and a notify operator
task, connected by a precedence constraint (green line with an arrow
pointing to the notify operator task).
If so, just right click on the precedence constraint and change it from
success to failure. Then, the notify operator task will only run when
the preceding task fails.
HTH,
Jeff
fniles wrote:
> It looks like you were referring to SQL 2000. I do see what you are
> referring to in SQL 2000. I am using SQL 2005. I do not see "Jobs" in SQL
> 2005.
> Do you know how I can do this in SQL 2005 ?
> Thank you.
> "Ben Nevarez" <BenNevarez@.discussions.microsoft.com> wrote in message
> news:BC2F9E23-D44D-40C3-BB49-55910DA35015@.microsoft.com...
>
>
|||Thank you.
If I change it to failure, if the process only fail partially, will it
report it to the operator ?
"Jeffrey Williams" <jeff.williams3188@.verizon.net> wrote in message
news:e7uo%23IXVIHA.2368@.TK2MSFTNGP05.phx.gbl...[vbcol=seagreen]
> If I am understanding correctly what you have done, you have created a
> maintenance plan in SQL 2005. In that maintenance plan (actually that
> sub-plan), you have two tasks. The backup task and a notify operator
> task, connected by a precedence constraint (green line with an arrow
> pointing to the notify operator task).
> If so, just right click on the precedence constraint and change it from
> success to failure. Then, the notify operator task will only run when the
> preceding task fails.
> HTH,
> Jeff
> fniles wrote:
|||What do you mean by fail partially? Either the task completes
successfully, or the task fails - there is no partial failure.
But, if you have multiple tasks in the sub-plan and a single notify
operator task - with all tasks connected to the notify operator task on
failure the notify operator task will only fire if all tasks fail. To
get the notify operator task to fire if any one task fails you need to
right-click on one of the failure (red arrow) constraints and change
from AND to OR condition.
Or, you can add a separate notify operator task for each individual task
in the sub-plan. For example, you would have a Check Database Integrity
Task, Rebuild Index Task, Update Statistics, Backup Task and Cleanup
Task (connected in order on success) with a notify operator task
connected to the Database Integrity Task, a separate notify operator
task connected to the Rebuild Index Task, etc...
fniles wrote:
> Thank you.
> If I change it to failure, if the process only fail partially, will it
> report it to the operator ?
> "Jeffrey Williams" <jeff.williams3188@.verizon.net> wrote in message
> news:e7uo%23IXVIHA.2368@.TK2MSFTNGP05.phx.gbl...
>
>
Tuesday, February 14, 2012
Backup
I am in the process of setting up my backup schedule. Is it good practice to
include the transaction logs in the same backup file as my full or
differential backup?
Thank you"Curtis" <Curtis@.discussions.microsoft.com> wrote in message
news:8E90BB0D-F1B9-47C9-9EFD-B8EB41C5061F@.microsoft.com...
> I am in the process of setting up my backup schedule. Is it good practice
to
> include the transaction logs in the same backup file as my full or
> differential backup?
I tend not to. Mostly personal preference.
> Thank you
include the transaction logs in the same backup file as my full or
differential backup?
Thank you"Curtis" <Curtis@.discussions.microsoft.com> wrote in message
news:8E90BB0D-F1B9-47C9-9EFD-B8EB41C5061F@.microsoft.com...
> I am in the process of setting up my backup schedule. Is it good practice
to
> include the transaction logs in the same backup file as my full or
> differential backup?
I tend not to. Mostly personal preference.
> Thank you
Backup
I am in the process of setting up my backup schedule. Is it good practice to
include the transaction logs in the same backup file as my full or
differential backup?
Thank you"Curtis" <Curtis@.discussions.microsoft.com> wrote in message
news:8E90BB0D-F1B9-47C9-9EFD-B8EB41C5061F@.microsoft.com...
> I am in the process of setting up my backup schedule. Is it good practice
to
> include the transaction logs in the same backup file as my full or
> differential backup?
I tend not to. Mostly personal preference.
> Thank you
include the transaction logs in the same backup file as my full or
differential backup?
Thank you"Curtis" <Curtis@.discussions.microsoft.com> wrote in message
news:8E90BB0D-F1B9-47C9-9EFD-B8EB41C5061F@.microsoft.com...
> I am in the process of setting up my backup schedule. Is it good practice
to
> include the transaction logs in the same backup file as my full or
> differential backup?
I tend not to. Mostly personal preference.
> Thank you
Sunday, February 12, 2012
Backing up transaction logs using two DB Maintainance Plan
If I am doing two different maintainance plan for backing up the transaction logs of the same database of sql server. Will the transactions logs being backed up on plan 2 will be independent of plan 1, or will it be backup of the transactions done after backup done by maintainance plan of
Please reply soon
Thank
Saroshthey'll be independent as long as they aren't scheduled for the exact same time. each backup file's name contains the date and time (only to hour and minute) that the backup started so that you could have problems if both backups began running at the same time.
Sarosh wrote:
> If I am doing two different maintainance plan for backing up the transaction logs of the same database of sql server. Will the transactions logs being backed up on plan 2 will be independent of plan 1, or will it be backup of the transactions done after backup done by maintainance plan of 1
> Please reply soon.
> Thanks
> Sarosh
Please reply soon
Thank
Saroshthey'll be independent as long as they aren't scheduled for the exact same time. each backup file's name contains the date and time (only to hour and minute) that the backup started so that you could have problems if both backups began running at the same time.
Sarosh wrote:
> If I am doing two different maintainance plan for backing up the transaction logs of the same database of sql server. Will the transactions logs being backed up on plan 2 will be independent of plan 1, or will it be backup of the transactions done after backup done by maintainance plan of 1
> Please reply soon.
> Thanks
> Sarosh
Subscribe to:
Posts (Atom)