Hello all.
Does log shipping use the tables in msdb normally used by backup, e.g.
backupset, backupfile?
Thanks.
Log shipping creates its set of tables in the msdb database of the monitor
server.
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
|||Yes, but then there are also specialized objects for the log shipping
information in addition to the normal ones.
Either use SQL EM or the Object Browser in QA to browse through the msdb
objects.
Sincerely,
Anthony Thomas
"David Pendleton" <qnircra@.gpd.arg> wrote in message
news:upK2NYL2EHA.3640@.tk2msftngp13.phx.gbl...
Hello all.
Does log shipping use the tables in msdb normally used by backup, e.g.
backupset, backupfile?
Thanks.
Showing posts with label msdb. Show all posts
Showing posts with label msdb. Show all posts
Wednesday, March 28, 2012
Log Shipping Tables
Hello all.
Does log shipping use the tables in msdb normally used by backup, e.g.
backupset, backupfile?
Thanks.Log shipping creates its set of tables in the msdb database of the monitor
server.
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.|||Yes, but then there are also specialized objects for the log shipping
information in addition to the normal ones.
Either use SQL EM or the Object Browser in QA to browse through the msdb
objects.
Sincerely,
Anthony Thomas
"David Pendleton" <qnircra@.gpd.arg> wrote in message
news:upK2NYL2EHA.3640@.tk2msftngp13.phx.gbl...
Hello all.
Does log shipping use the tables in msdb normally used by backup, e.g.
backupset, backupfile?
Thanks.
Does log shipping use the tables in msdb normally used by backup, e.g.
backupset, backupfile?
Thanks.Log shipping creates its set of tables in the msdb database of the monitor
server.
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.|||Yes, but then there are also specialized objects for the log shipping
information in addition to the normal ones.
Either use SQL EM or the Object Browser in QA to browse through the msdb
objects.
Sincerely,
Anthony Thomas
"David Pendleton" <qnircra@.gpd.arg> wrote in message
news:upK2NYL2EHA.3640@.tk2msftngp13.phx.gbl...
Hello all.
Does log shipping use the tables in msdb normally used by backup, e.g.
backupset, backupfile?
Thanks.
Log Shipping Tables
Hello all.
Does log shipping use the tables in msdb normally used by backup, e.g.
backupset, backupfile?
Thanks.Log shipping creates its set of tables in the msdb database of the monitor
server.
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.|||Yes, but then there are also specialized objects for the log shipping
information in addition to the normal ones.
Either use SQL EM or the Object Browser in QA to browse through the msdb
objects.
Sincerely,
Anthony Thomas
"David Pendleton" <qnircra@.gpd.arg> wrote in message
news:upK2NYL2EHA.3640@.tk2msftngp13.phx.gbl...
Hello all.
Does log shipping use the tables in msdb normally used by backup, e.g.
backupset, backupfile?
Thanks.sql
Does log shipping use the tables in msdb normally used by backup, e.g.
backupset, backupfile?
Thanks.Log shipping creates its set of tables in the msdb database of the monitor
server.
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.|||Yes, but then there are also specialized objects for the log shipping
information in addition to the normal ones.
Either use SQL EM or the Object Browser in QA to browse through the msdb
objects.
Sincerely,
Anthony Thomas
"David Pendleton" <qnircra@.gpd.arg> wrote in message
news:upK2NYL2EHA.3640@.tk2msftngp13.phx.gbl...
Hello all.
Does log shipping use the tables in msdb normally used by backup, e.g.
backupset, backupfile?
Thanks.sql
Friday, March 23, 2012
log shipping problem
So...
I *accidentally* deleted some of the msdb.dbo log shipping tables, could
anyone out there help me out with the table generation scripts so that I
don't have to re-install SQL 2000?
Willie
All the MSDB stuff is in the instmsdb.sql script which I think should be in
the INSTALL directory for your instance. It's unlikely that you understand
log shipping well enough to get everything back to a useable state if only
some of the tables were dropped so your number one option is to restore an
old backup and number to is to ask customer support for help.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Willie Bodger" <williebnospam@.lap_ink.c_m> wrote in message
news:OTOVdZHeHHA.1216@.TK2MSFTNGP03.phx.gbl...
> So...
> I *accidentally* deleted some of the msdb.dbo log shipping tables, could
> anyone out there help me out with the table generation scripts so that I
> don't have to re-install SQL 2000?
> Willie
>
|||Actually, this got me on the right path, but it was the instls.sql file in
the /install directory that creates the log shipping pieces.
"Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
news:910467DF-E344-4246-96E0-EF31FF583BEA@.microsoft.com...
> All the MSDB stuff is in the instmsdb.sql script which I think should be
> in the INSTALL directory for your instance. It's unlikely that you
> understand log shipping well enough to get everything back to a useable
> state if only some of the tables were dropped so your number one option is
> to restore an old backup and number to is to ask customer support for
> help.
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "Willie Bodger" <williebnospam@.lap_ink.c_m> wrote in message
> news:OTOVdZHeHHA.1216@.TK2MSFTNGP03.phx.gbl...
>
|||Sorry, I just have SQL 2005 on my box. That's why I was a little vague
about locations.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Willie Bodger" <williebnospam@.lap_ink.c_m> wrote in message
news:OrDV8XJeHHA.2188@.TK2MSFTNGP04.phx.gbl...
> Actually, this got me on the right path, but it was the instls.sql file in
> the /install directory that creates the log shipping pieces.
> "Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
> news:910467DF-E344-4246-96E0-EF31FF583BEA@.microsoft.com...
>
|||Once you recover your tables , make sure that you add MSDB and MASTER
databases in your regular backup procedure
Thanks
Hari
"Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
news:E0C391EC-AD75-48EC-A5B7-29DAF4D13510@.microsoft.com...
> Sorry, I just have SQL 2005 on my box. That's why I was a little vague
> about locations.
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "Willie Bodger" <williebnospam@.lap_ink.c_m> wrote in message
> news:OrDV8XJeHHA.2188@.TK2MSFTNGP04.phx.gbl...
>
|||Thank you for the help you have already given me, and now I have another
problem with the log shipping. I have 7 databases that I have setup Log
Shipping on and 6 of them work great. The one with issues is a much larger
database (exponentially larger). On the other 6 I have log shipping done at
longer intervals to spread the load out and because they don't see much
activity. On the main database, it seems to work along fine for a while and
then suddenly it can no longer restore the log files. What I have is the SQL
Server installed on the C drive (33.5 GB free), the data is on the D drive
(38.9 GB free) and the log files are on the F drive (262 GB free). The log
files are generally between 2 and 4 MB and the log file that it choked on
was 2,493 kb, with the last one before it being 2,237 kb. I have tried it
with 15 minute intervals between transaction log backups and an hour between
backups, both ending in the same thing: Everything works fine for a while
and then all of a sudden the restore fails and the database is left in the
loading state where it has been for 26 hours now. Does anybody out there
have any suggestions for me? Is there some limit on how many databases you
can setup log shipping on any one machine? Or perhaps any other suggestions
for where I could like for the cause of this problem? Thanks again for any
help you can give me.
Willie
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:%23tR%23c5LeHHA.928@.TK2MSFTNGP02.phx.gbl...
> Once you recover your tables , make sure that you add MSDB and MASTER
> databases in your regular backup procedure
> Thanks
> Hari
> "Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
> news:E0C391EC-AD75-48EC-A5B7-29DAF4D13510@.microsoft.com...
>
sql
I *accidentally* deleted some of the msdb.dbo log shipping tables, could
anyone out there help me out with the table generation scripts so that I
don't have to re-install SQL 2000?
Willie
All the MSDB stuff is in the instmsdb.sql script which I think should be in
the INSTALL directory for your instance. It's unlikely that you understand
log shipping well enough to get everything back to a useable state if only
some of the tables were dropped so your number one option is to restore an
old backup and number to is to ask customer support for help.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Willie Bodger" <williebnospam@.lap_ink.c_m> wrote in message
news:OTOVdZHeHHA.1216@.TK2MSFTNGP03.phx.gbl...
> So...
> I *accidentally* deleted some of the msdb.dbo log shipping tables, could
> anyone out there help me out with the table generation scripts so that I
> don't have to re-install SQL 2000?
> Willie
>
|||Actually, this got me on the right path, but it was the instls.sql file in
the /install directory that creates the log shipping pieces.
"Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
news:910467DF-E344-4246-96E0-EF31FF583BEA@.microsoft.com...
> All the MSDB stuff is in the instmsdb.sql script which I think should be
> in the INSTALL directory for your instance. It's unlikely that you
> understand log shipping well enough to get everything back to a useable
> state if only some of the tables were dropped so your number one option is
> to restore an old backup and number to is to ask customer support for
> help.
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "Willie Bodger" <williebnospam@.lap_ink.c_m> wrote in message
> news:OTOVdZHeHHA.1216@.TK2MSFTNGP03.phx.gbl...
>
|||Sorry, I just have SQL 2005 on my box. That's why I was a little vague
about locations.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Willie Bodger" <williebnospam@.lap_ink.c_m> wrote in message
news:OrDV8XJeHHA.2188@.TK2MSFTNGP04.phx.gbl...
> Actually, this got me on the right path, but it was the instls.sql file in
> the /install directory that creates the log shipping pieces.
> "Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
> news:910467DF-E344-4246-96E0-EF31FF583BEA@.microsoft.com...
>
|||Once you recover your tables , make sure that you add MSDB and MASTER
databases in your regular backup procedure
Thanks
Hari
"Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
news:E0C391EC-AD75-48EC-A5B7-29DAF4D13510@.microsoft.com...
> Sorry, I just have SQL 2005 on my box. That's why I was a little vague
> about locations.
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "Willie Bodger" <williebnospam@.lap_ink.c_m> wrote in message
> news:OrDV8XJeHHA.2188@.TK2MSFTNGP04.phx.gbl...
>
|||Thank you for the help you have already given me, and now I have another
problem with the log shipping. I have 7 databases that I have setup Log
Shipping on and 6 of them work great. The one with issues is a much larger
database (exponentially larger). On the other 6 I have log shipping done at
longer intervals to spread the load out and because they don't see much
activity. On the main database, it seems to work along fine for a while and
then suddenly it can no longer restore the log files. What I have is the SQL
Server installed on the C drive (33.5 GB free), the data is on the D drive
(38.9 GB free) and the log files are on the F drive (262 GB free). The log
files are generally between 2 and 4 MB and the log file that it choked on
was 2,493 kb, with the last one before it being 2,237 kb. I have tried it
with 15 minute intervals between transaction log backups and an hour between
backups, both ending in the same thing: Everything works fine for a while
and then all of a sudden the restore fails and the database is left in the
loading state where it has been for 26 hours now. Does anybody out there
have any suggestions for me? Is there some limit on how many databases you
can setup log shipping on any one machine? Or perhaps any other suggestions
for where I could like for the cause of this problem? Thanks again for any
help you can give me.
Willie
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:%23tR%23c5LeHHA.928@.TK2MSFTNGP02.phx.gbl...
> Once you recover your tables , make sure that you add MSDB and MASTER
> databases in your regular backup procedure
> Thanks
> Hari
> "Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
> news:E0C391EC-AD75-48EC-A5B7-29DAF4D13510@.microsoft.com...
>
sql
log shipping problem
So...
I *accidentally* deleted some of the msdb.dbo log shipping tables, could
anyone out there help me out with the table generation scripts so that I
don't have to re-install SQL 2000?
WillieAll the MSDB stuff is in the instmsdb.sql script which I think should be in
the INSTALL directory for your instance. It's unlikely that you understand
log shipping well enough to get everything back to a useable state if only
some of the tables were dropped so your number one option is to restore an
old backup and number to is to ask customer support for help.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Willie Bodger" <williebnospam@.lap_ink.c_m> wrote in message
news:OTOVdZHeHHA.1216@.TK2MSFTNGP03.phx.gbl...
> So...
> I *accidentally* deleted some of the msdb.dbo log shipping tables, could
> anyone out there help me out with the table generation scripts so that I
> don't have to re-install SQL 2000?
> Willie
>|||Actually, this got me on the right path, but it was the instls.sql file in
the /install directory that creates the log shipping pieces.
"Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
news:910467DF-E344-4246-96E0-EF31FF583BEA@.microsoft.com...
> All the MSDB stuff is in the instmsdb.sql script which I think should be
> in the INSTALL directory for your instance. It's unlikely that you
> understand log shipping well enough to get everything back to a useable
> state if only some of the tables were dropped so your number one option is
> to restore an old backup and number to is to ask customer support for
> help.
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "Willie Bodger" <williebnospam@.lap_ink.c_m> wrote in message
> news:OTOVdZHeHHA.1216@.TK2MSFTNGP03.phx.gbl...
>|||Sorry, I just have SQL 2005 on my box. That's why I was a little vague
about locations.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Willie Bodger" <williebnospam@.lap_ink.c_m> wrote in message
news:OrDV8XJeHHA.2188@.TK2MSFTNGP04.phx.gbl...
> Actually, this got me on the right path, but it was the instls.sql file in
> the /install directory that creates the log shipping pieces.
> "Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
> news:910467DF-E344-4246-96E0-EF31FF583BEA@.microsoft.com...
>|||Once you recover your tables , make sure that you add MSDB and MASTER
databases in your regular backup procedure
Thanks
Hari
"Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
news:E0C391EC-AD75-48EC-A5B7-29DAF4D13510@.microsoft.com...
> Sorry, I just have SQL 2005 on my box. That's why I was a little vague
> about locations.
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "Willie Bodger" <williebnospam@.lap_ink.c_m> wrote in message
> news:OrDV8XJeHHA.2188@.TK2MSFTNGP04.phx.gbl...
>|||Thank you for the help you have already given me, and now I have another
problem with the log shipping. I have 7 databases that I have setup Log
Shipping on and 6 of them work great. The one with issues is a much larger
database (exponentially larger). On the other 6 I have log shipping done at
longer intervals to spread the load out and because they don't see much
activity. On the main database, it seems to work along fine for a while and
then suddenly it can no longer restore the log files. What I have is the SQL
Server installed on the C drive (33.5 GB free), the data is on the D drive
(38.9 GB free) and the log files are on the F drive (262 GB free). The log
files are generally between 2 and 4 MB and the log file that it choked on
was 2,493 kb, with the last one before it being 2,237 kb. I have tried it
with 15 minute intervals between transaction log backups and an hour between
backups, both ending in the same thing: Everything works fine for a while
and then all of a sudden the restore fails and the database is left in the
loading state where it has been for 26 hours now. Does anybody out there
have any suggestions for me? Is there some limit on how many databases you
can setup log shipping on any one machine? Or perhaps any other suggestions
for where I could like for the cause of this problem? Thanks again for any
help you can give me.
Willie
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:%23tR%23c5LeHHA.928@.TK2MSFTNGP02.phx.gbl...
> Once you recover your tables , make sure that you add MSDB and MASTER
> databases in your regular backup procedure
> Thanks
> Hari
> "Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
> news:E0C391EC-AD75-48EC-A5B7-29DAF4D13510@.microsoft.com...
>
I *accidentally* deleted some of the msdb.dbo log shipping tables, could
anyone out there help me out with the table generation scripts so that I
don't have to re-install SQL 2000?
WillieAll the MSDB stuff is in the instmsdb.sql script which I think should be in
the INSTALL directory for your instance. It's unlikely that you understand
log shipping well enough to get everything back to a useable state if only
some of the tables were dropped so your number one option is to restore an
old backup and number to is to ask customer support for help.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Willie Bodger" <williebnospam@.lap_ink.c_m> wrote in message
news:OTOVdZHeHHA.1216@.TK2MSFTNGP03.phx.gbl...
> So...
> I *accidentally* deleted some of the msdb.dbo log shipping tables, could
> anyone out there help me out with the table generation scripts so that I
> don't have to re-install SQL 2000?
> Willie
>|||Actually, this got me on the right path, but it was the instls.sql file in
the /install directory that creates the log shipping pieces.
"Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
news:910467DF-E344-4246-96E0-EF31FF583BEA@.microsoft.com...
> All the MSDB stuff is in the instmsdb.sql script which I think should be
> in the INSTALL directory for your instance. It's unlikely that you
> understand log shipping well enough to get everything back to a useable
> state if only some of the tables were dropped so your number one option is
> to restore an old backup and number to is to ask customer support for
> help.
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "Willie Bodger" <williebnospam@.lap_ink.c_m> wrote in message
> news:OTOVdZHeHHA.1216@.TK2MSFTNGP03.phx.gbl...
>|||Sorry, I just have SQL 2005 on my box. That's why I was a little vague
about locations.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Willie Bodger" <williebnospam@.lap_ink.c_m> wrote in message
news:OrDV8XJeHHA.2188@.TK2MSFTNGP04.phx.gbl...
> Actually, this got me on the right path, but it was the instls.sql file in
> the /install directory that creates the log shipping pieces.
> "Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
> news:910467DF-E344-4246-96E0-EF31FF583BEA@.microsoft.com...
>|||Once you recover your tables , make sure that you add MSDB and MASTER
databases in your regular backup procedure
Thanks
Hari
"Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
news:E0C391EC-AD75-48EC-A5B7-29DAF4D13510@.microsoft.com...
> Sorry, I just have SQL 2005 on my box. That's why I was a little vague
> about locations.
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "Willie Bodger" <williebnospam@.lap_ink.c_m> wrote in message
> news:OrDV8XJeHHA.2188@.TK2MSFTNGP04.phx.gbl...
>|||Thank you for the help you have already given me, and now I have another
problem with the log shipping. I have 7 databases that I have setup Log
Shipping on and 6 of them work great. The one with issues is a much larger
database (exponentially larger). On the other 6 I have log shipping done at
longer intervals to spread the load out and because they don't see much
activity. On the main database, it seems to work along fine for a while and
then suddenly it can no longer restore the log files. What I have is the SQL
Server installed on the C drive (33.5 GB free), the data is on the D drive
(38.9 GB free) and the log files are on the F drive (262 GB free). The log
files are generally between 2 and 4 MB and the log file that it choked on
was 2,493 kb, with the last one before it being 2,237 kb. I have tried it
with 15 minute intervals between transaction log backups and an hour between
backups, both ending in the same thing: Everything works fine for a while
and then all of a sudden the restore fails and the database is left in the
loading state where it has been for 26 hours now. Does anybody out there
have any suggestions for me? Is there some limit on how many databases you
can setup log shipping on any one machine? Or perhaps any other suggestions
for where I could like for the cause of this problem? Thanks again for any
help you can give me.
Willie
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:%23tR%23c5LeHHA.928@.TK2MSFTNGP02.phx.gbl...
> Once you recover your tables , make sure that you add MSDB and MASTER
> databases in your regular backup procedure
> Thanks
> Hari
> "Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
> news:E0C391EC-AD75-48EC-A5B7-29DAF4D13510@.microsoft.com...
>
log shipping problem
So...
I *accidentally* deleted some of the msdb.dbo log shipping tables, could
anyone out there help me out with the table generation scripts so that I
don't have to re-install SQL 2000?
WillieAll the MSDB stuff is in the instmsdb.sql script which I think should be in
the INSTALL directory for your instance. It's unlikely that you understand
log shipping well enough to get everything back to a useable state if only
some of the tables were dropped so your number one option is to restore an
old backup and number to is to ask customer support for help.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Willie Bodger" <williebnospam@.lap_ink.c_m> wrote in message
news:OTOVdZHeHHA.1216@.TK2MSFTNGP03.phx.gbl...
> So...
> I *accidentally* deleted some of the msdb.dbo log shipping tables, could
> anyone out there help me out with the table generation scripts so that I
> don't have to re-install SQL 2000?
> Willie
>|||Actually, this got me on the right path, but it was the instls.sql file in
the /install directory that creates the log shipping pieces.
"Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
news:910467DF-E344-4246-96E0-EF31FF583BEA@.microsoft.com...
> All the MSDB stuff is in the instmsdb.sql script which I think should be
> in the INSTALL directory for your instance. It's unlikely that you
> understand log shipping well enough to get everything back to a useable
> state if only some of the tables were dropped so your number one option is
> to restore an old backup and number to is to ask customer support for
> help.
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "Willie Bodger" <williebnospam@.lap_ink.c_m> wrote in message
> news:OTOVdZHeHHA.1216@.TK2MSFTNGP03.phx.gbl...
>> So...
>> I *accidentally* deleted some of the msdb.dbo log shipping tables, could
>> anyone out there help me out with the table generation scripts so that I
>> don't have to re-install SQL 2000?
>> Willie
>|||Sorry, I just have SQL 2005 on my box. That's why I was a little vague
about locations.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Willie Bodger" <williebnospam@.lap_ink.c_m> wrote in message
news:OrDV8XJeHHA.2188@.TK2MSFTNGP04.phx.gbl...
> Actually, this got me on the right path, but it was the instls.sql file in
> the /install directory that creates the log shipping pieces.
> "Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
> news:910467DF-E344-4246-96E0-EF31FF583BEA@.microsoft.com...
>> All the MSDB stuff is in the instmsdb.sql script which I think should be
>> in the INSTALL directory for your instance. It's unlikely that you
>> understand log shipping well enough to get everything back to a useable
>> state if only some of the tables were dropped so your number one option
>> is to restore an old backup and number to is to ask customer support for
>> help.
>> --
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> Use of included script samples are subject to the terms specified at
>> http://www.microsoft.com/info/cpyright.htm
>> "Willie Bodger" <williebnospam@.lap_ink.c_m> wrote in message
>> news:OTOVdZHeHHA.1216@.TK2MSFTNGP03.phx.gbl...
>> So...
>> I *accidentally* deleted some of the msdb.dbo log shipping tables, could
>> anyone out there help me out with the table generation scripts so that I
>> don't have to re-install SQL 2000?
>> Willie
>>
>|||Once you recover your tables , make sure that you add MSDB and MASTER
databases in your regular backup procedure
Thanks
Hari
"Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
news:E0C391EC-AD75-48EC-A5B7-29DAF4D13510@.microsoft.com...
> Sorry, I just have SQL 2005 on my box. That's why I was a little vague
> about locations.
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "Willie Bodger" <williebnospam@.lap_ink.c_m> wrote in message
> news:OrDV8XJeHHA.2188@.TK2MSFTNGP04.phx.gbl...
>> Actually, this got me on the right path, but it was the instls.sql file
>> in the /install directory that creates the log shipping pieces.
>> "Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
>> news:910467DF-E344-4246-96E0-EF31FF583BEA@.microsoft.com...
>> All the MSDB stuff is in the instmsdb.sql script which I think should be
>> in the INSTALL directory for your instance. It's unlikely that you
>> understand log shipping well enough to get everything back to a useable
>> state if only some of the tables were dropped so your number one option
>> is to restore an old backup and number to is to ask customer support for
>> help.
>> --
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> Use of included script samples are subject to the terms specified at
>> http://www.microsoft.com/info/cpyright.htm
>> "Willie Bodger" <williebnospam@.lap_ink.c_m> wrote in message
>> news:OTOVdZHeHHA.1216@.TK2MSFTNGP03.phx.gbl...
>> So...
>> I *accidentally* deleted some of the msdb.dbo log shipping tables,
>> could anyone out there help me out with the table generation scripts so
>> that I don't have to re-install SQL 2000?
>> Willie
>>
>>
>|||Thank you for the help you have already given me, and now I have another
problem with the log shipping. I have 7 databases that I have setup Log
Shipping on and 6 of them work great. The one with issues is a much larger
database (exponentially larger). On the other 6 I have log shipping done at
longer intervals to spread the load out and because they don't see much
activity. On the main database, it seems to work along fine for a while and
then suddenly it can no longer restore the log files. What I have is the SQL
Server installed on the C drive (33.5 GB free), the data is on the D drive
(38.9 GB free) and the log files are on the F drive (262 GB free). The log
files are generally between 2 and 4 MB and the log file that it choked on
was 2,493 kb, with the last one before it being 2,237 kb. I have tried it
with 15 minute intervals between transaction log backups and an hour between
backups, both ending in the same thing: Everything works fine for a while
and then all of a sudden the restore fails and the database is left in the
loading state where it has been for 26 hours now. Does anybody out there
have any suggestions for me? Is there some limit on how many databases you
can setup log shipping on any one machine? Or perhaps any other suggestions
for where I could like for the cause of this problem? Thanks again for any
help you can give me.
Willie
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:%23tR%23c5LeHHA.928@.TK2MSFTNGP02.phx.gbl...
> Once you recover your tables , make sure that you add MSDB and MASTER
> databases in your regular backup procedure
> Thanks
> Hari
> "Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
> news:E0C391EC-AD75-48EC-A5B7-29DAF4D13510@.microsoft.com...
>> Sorry, I just have SQL 2005 on my box. That's why I was a little vague
>> about locations.
>> --
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> Use of included script samples are subject to the terms specified at
>> http://www.microsoft.com/info/cpyright.htm
>> "Willie Bodger" <williebnospam@.lap_ink.c_m> wrote in message
>> news:OrDV8XJeHHA.2188@.TK2MSFTNGP04.phx.gbl...
>> Actually, this got me on the right path, but it was the instls.sql file
>> in the /install directory that creates the log shipping pieces.
>> "Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
>> news:910467DF-E344-4246-96E0-EF31FF583BEA@.microsoft.com...
>> All the MSDB stuff is in the instmsdb.sql script which I think should
>> be in the INSTALL directory for your instance. It's unlikely that you
>> understand log shipping well enough to get everything back to a useable
>> state if only some of the tables were dropped so your number one option
>> is to restore an old backup and number to is to ask customer support
>> for help.
>> --
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> Use of included script samples are subject to the terms specified at
>> http://www.microsoft.com/info/cpyright.htm
>> "Willie Bodger" <williebnospam@.lap_ink.c_m> wrote in message
>> news:OTOVdZHeHHA.1216@.TK2MSFTNGP03.phx.gbl...
>> So...
>> I *accidentally* deleted some of the msdb.dbo log shipping tables,
>> could anyone out there help me out with the table generation scripts
>> so that I don't have to re-install SQL 2000?
>> Willie
>>
>>
>
I *accidentally* deleted some of the msdb.dbo log shipping tables, could
anyone out there help me out with the table generation scripts so that I
don't have to re-install SQL 2000?
WillieAll the MSDB stuff is in the instmsdb.sql script which I think should be in
the INSTALL directory for your instance. It's unlikely that you understand
log shipping well enough to get everything back to a useable state if only
some of the tables were dropped so your number one option is to restore an
old backup and number to is to ask customer support for help.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Willie Bodger" <williebnospam@.lap_ink.c_m> wrote in message
news:OTOVdZHeHHA.1216@.TK2MSFTNGP03.phx.gbl...
> So...
> I *accidentally* deleted some of the msdb.dbo log shipping tables, could
> anyone out there help me out with the table generation scripts so that I
> don't have to re-install SQL 2000?
> Willie
>|||Actually, this got me on the right path, but it was the instls.sql file in
the /install directory that creates the log shipping pieces.
"Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
news:910467DF-E344-4246-96E0-EF31FF583BEA@.microsoft.com...
> All the MSDB stuff is in the instmsdb.sql script which I think should be
> in the INSTALL directory for your instance. It's unlikely that you
> understand log shipping well enough to get everything back to a useable
> state if only some of the tables were dropped so your number one option is
> to restore an old backup and number to is to ask customer support for
> help.
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "Willie Bodger" <williebnospam@.lap_ink.c_m> wrote in message
> news:OTOVdZHeHHA.1216@.TK2MSFTNGP03.phx.gbl...
>> So...
>> I *accidentally* deleted some of the msdb.dbo log shipping tables, could
>> anyone out there help me out with the table generation scripts so that I
>> don't have to re-install SQL 2000?
>> Willie
>|||Sorry, I just have SQL 2005 on my box. That's why I was a little vague
about locations.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Willie Bodger" <williebnospam@.lap_ink.c_m> wrote in message
news:OrDV8XJeHHA.2188@.TK2MSFTNGP04.phx.gbl...
> Actually, this got me on the right path, but it was the instls.sql file in
> the /install directory that creates the log shipping pieces.
> "Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
> news:910467DF-E344-4246-96E0-EF31FF583BEA@.microsoft.com...
>> All the MSDB stuff is in the instmsdb.sql script which I think should be
>> in the INSTALL directory for your instance. It's unlikely that you
>> understand log shipping well enough to get everything back to a useable
>> state if only some of the tables were dropped so your number one option
>> is to restore an old backup and number to is to ask customer support for
>> help.
>> --
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> Use of included script samples are subject to the terms specified at
>> http://www.microsoft.com/info/cpyright.htm
>> "Willie Bodger" <williebnospam@.lap_ink.c_m> wrote in message
>> news:OTOVdZHeHHA.1216@.TK2MSFTNGP03.phx.gbl...
>> So...
>> I *accidentally* deleted some of the msdb.dbo log shipping tables, could
>> anyone out there help me out with the table generation scripts so that I
>> don't have to re-install SQL 2000?
>> Willie
>>
>|||Once you recover your tables , make sure that you add MSDB and MASTER
databases in your regular backup procedure
Thanks
Hari
"Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
news:E0C391EC-AD75-48EC-A5B7-29DAF4D13510@.microsoft.com...
> Sorry, I just have SQL 2005 on my box. That's why I was a little vague
> about locations.
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "Willie Bodger" <williebnospam@.lap_ink.c_m> wrote in message
> news:OrDV8XJeHHA.2188@.TK2MSFTNGP04.phx.gbl...
>> Actually, this got me on the right path, but it was the instls.sql file
>> in the /install directory that creates the log shipping pieces.
>> "Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
>> news:910467DF-E344-4246-96E0-EF31FF583BEA@.microsoft.com...
>> All the MSDB stuff is in the instmsdb.sql script which I think should be
>> in the INSTALL directory for your instance. It's unlikely that you
>> understand log shipping well enough to get everything back to a useable
>> state if only some of the tables were dropped so your number one option
>> is to restore an old backup and number to is to ask customer support for
>> help.
>> --
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> Use of included script samples are subject to the terms specified at
>> http://www.microsoft.com/info/cpyright.htm
>> "Willie Bodger" <williebnospam@.lap_ink.c_m> wrote in message
>> news:OTOVdZHeHHA.1216@.TK2MSFTNGP03.phx.gbl...
>> So...
>> I *accidentally* deleted some of the msdb.dbo log shipping tables,
>> could anyone out there help me out with the table generation scripts so
>> that I don't have to re-install SQL 2000?
>> Willie
>>
>>
>|||Thank you for the help you have already given me, and now I have another
problem with the log shipping. I have 7 databases that I have setup Log
Shipping on and 6 of them work great. The one with issues is a much larger
database (exponentially larger). On the other 6 I have log shipping done at
longer intervals to spread the load out and because they don't see much
activity. On the main database, it seems to work along fine for a while and
then suddenly it can no longer restore the log files. What I have is the SQL
Server installed on the C drive (33.5 GB free), the data is on the D drive
(38.9 GB free) and the log files are on the F drive (262 GB free). The log
files are generally between 2 and 4 MB and the log file that it choked on
was 2,493 kb, with the last one before it being 2,237 kb. I have tried it
with 15 minute intervals between transaction log backups and an hour between
backups, both ending in the same thing: Everything works fine for a while
and then all of a sudden the restore fails and the database is left in the
loading state where it has been for 26 hours now. Does anybody out there
have any suggestions for me? Is there some limit on how many databases you
can setup log shipping on any one machine? Or perhaps any other suggestions
for where I could like for the cause of this problem? Thanks again for any
help you can give me.
Willie
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:%23tR%23c5LeHHA.928@.TK2MSFTNGP02.phx.gbl...
> Once you recover your tables , make sure that you add MSDB and MASTER
> databases in your regular backup procedure
> Thanks
> Hari
> "Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
> news:E0C391EC-AD75-48EC-A5B7-29DAF4D13510@.microsoft.com...
>> Sorry, I just have SQL 2005 on my box. That's why I was a little vague
>> about locations.
>> --
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> Use of included script samples are subject to the terms specified at
>> http://www.microsoft.com/info/cpyright.htm
>> "Willie Bodger" <williebnospam@.lap_ink.c_m> wrote in message
>> news:OrDV8XJeHHA.2188@.TK2MSFTNGP04.phx.gbl...
>> Actually, this got me on the right path, but it was the instls.sql file
>> in the /install directory that creates the log shipping pieces.
>> "Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
>> news:910467DF-E344-4246-96E0-EF31FF583BEA@.microsoft.com...
>> All the MSDB stuff is in the instmsdb.sql script which I think should
>> be in the INSTALL directory for your instance. It's unlikely that you
>> understand log shipping well enough to get everything back to a useable
>> state if only some of the tables were dropped so your number one option
>> is to restore an old backup and number to is to ask customer support
>> for help.
>> --
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> Use of included script samples are subject to the terms specified at
>> http://www.microsoft.com/info/cpyright.htm
>> "Willie Bodger" <williebnospam@.lap_ink.c_m> wrote in message
>> news:OTOVdZHeHHA.1216@.TK2MSFTNGP03.phx.gbl...
>> So...
>> I *accidentally* deleted some of the msdb.dbo log shipping tables,
>> could anyone out there help me out with the table generation scripts
>> so that I don't have to re-install SQL 2000?
>> Willie
>>
>>
>
Wednesday, March 21, 2012
Log Shipping Monitoring
When I execute the following SP:
EXEC msdb..sp_get_log_shipping_monitor_info @.secondary_database_name =
'pubs%'
I get some information regarding [copy_delta] and [load_delta]
I'm pretty sure copy_delta are there number of files copied over from the
source server. I don't know what the load_delta means though. Sometimes it
shows a low number then sometimes it shows a high number. I intially
thought it was the number of transaction logs that got loaded into the
standby server but when that number hits 69 and it only copied 3, it doesn't
make sense. There is also no documenation on BOL or microsoft's web site on
this.
Regards,
Tim
Hi Tim,
Based on my research, load_delta indicates the the difference in minutes
between the last updated date of the last backup file and the last updated
date of the last loaded file. In ths code of the sp_log_shipping_in_sync
stored procedure, which is called in sp_get_log_shipping_monitor_info, you
may see the following codes.
SELECT @.delta = DATEDIFF (mi, @.last_updated, @.compare_with)
Also, the @.last_updated is @.restoredt, which is got from the following
codes.
EXECUTE @.rv = sp_log_shipping_get_date_from_file @._primary_database_name,
@.last_backup_filename, @.backupdt OUTPUT
IF (@.rv <> 0)
SElECT @.backupdt = @.last_backup_last_updated
the@.compare_with is @.backupdt, which is got form the followig codes.
EXECUTE @.rv = sp_log_shipping_get_date_from_file @._primary_database_name,
@.last_loaded_filename, @.restoredt OUTPUT
IF (@.rv <> 0)
SElECT @.restoredt = @.last_loaded_last_updated
Regards,
Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
|||Thanks,
this is exactly what I am looking for.
Regards,
Tim
""Yuan Shao"" <v-yshao@.online.microsoft.com> wrote in message
news:PIofhxLNEHA.928@.cpmsftngxa10.phx.gbl...
> Hi Tim,
> Based on my research, load_delta indicates the the difference in minutes
> between the last updated date of the last backup file and the last
updated
> date of the last loaded file. In ths code of the sp_log_shipping_in_sync
> stored procedure, which is called in sp_get_log_shipping_monitor_info, you
> may see the following codes.
> SELECT @.delta = DATEDIFF (mi, @.last_updated, @.compare_with)
> Also, the @.last_updated is @.restoredt, which is got from the following
> codes.
> EXECUTE @.rv = sp_log_shipping_get_date_from_file @._primary_database_name,
> @.last_backup_filename, @.backupdt OUTPUT
> IF (@.rv <> 0)
> SElECT @.backupdt = @.last_backup_last_updated
> the@.compare_with is @.backupdt, which is got form the followig codes.
> EXECUTE @.rv = sp_log_shipping_get_date_from_file @._primary_database_name,
> @.last_loaded_filename, @.restoredt OUTPUT
> IF (@.rv <> 0)
> SElECT @.restoredt = @.last_loaded_last_updated
> Regards,
> Michael Shao
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> This posting is provided "as is" with no warranties and confers no rights.
>
>
EXEC msdb..sp_get_log_shipping_monitor_info @.secondary_database_name =
'pubs%'
I get some information regarding [copy_delta] and [load_delta]
I'm pretty sure copy_delta are there number of files copied over from the
source server. I don't know what the load_delta means though. Sometimes it
shows a low number then sometimes it shows a high number. I intially
thought it was the number of transaction logs that got loaded into the
standby server but when that number hits 69 and it only copied 3, it doesn't
make sense. There is also no documenation on BOL or microsoft's web site on
this.
Regards,
Tim
Hi Tim,
Based on my research, load_delta indicates the the difference in minutes
between the last updated date of the last backup file and the last updated
date of the last loaded file. In ths code of the sp_log_shipping_in_sync
stored procedure, which is called in sp_get_log_shipping_monitor_info, you
may see the following codes.
SELECT @.delta = DATEDIFF (mi, @.last_updated, @.compare_with)
Also, the @.last_updated is @.restoredt, which is got from the following
codes.
EXECUTE @.rv = sp_log_shipping_get_date_from_file @._primary_database_name,
@.last_backup_filename, @.backupdt OUTPUT
IF (@.rv <> 0)
SElECT @.backupdt = @.last_backup_last_updated
the@.compare_with is @.backupdt, which is got form the followig codes.
EXECUTE @.rv = sp_log_shipping_get_date_from_file @._primary_database_name,
@.last_loaded_filename, @.restoredt OUTPUT
IF (@.rv <> 0)
SElECT @.restoredt = @.last_loaded_last_updated
Regards,
Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
|||Thanks,
this is exactly what I am looking for.
Regards,
Tim
""Yuan Shao"" <v-yshao@.online.microsoft.com> wrote in message
news:PIofhxLNEHA.928@.cpmsftngxa10.phx.gbl...
> Hi Tim,
> Based on my research, load_delta indicates the the difference in minutes
> between the last updated date of the last backup file and the last
updated
> date of the last loaded file. In ths code of the sp_log_shipping_in_sync
> stored procedure, which is called in sp_get_log_shipping_monitor_info, you
> may see the following codes.
> SELECT @.delta = DATEDIFF (mi, @.last_updated, @.compare_with)
> Also, the @.last_updated is @.restoredt, which is got from the following
> codes.
> EXECUTE @.rv = sp_log_shipping_get_date_from_file @._primary_database_name,
> @.last_backup_filename, @.backupdt OUTPUT
> IF (@.rv <> 0)
> SElECT @.backupdt = @.last_backup_last_updated
> the@.compare_with is @.backupdt, which is got form the followig codes.
> EXECUTE @.rv = sp_log_shipping_get_date_from_file @._primary_database_name,
> @.last_loaded_filename, @.restoredt OUTPUT
> IF (@.rv <> 0)
> SElECT @.restoredt = @.last_loaded_last_updated
> Regards,
> Michael Shao
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> This posting is provided "as is" with no warranties and confers no rights.
>
>
Log Shipping Monitoring
When I execute the following SP:
EXEC msdb..sp_get_log_shipping_monitor_info @.secondary_database_name = 'pubs%'
I get some information regarding [copy_delta] and [load_delta]
I'm pretty sure copy_delta are there number of files copied over from the
source server. I don't know what the load_delta means though. Sometimes it
shows a low number then sometimes it shows a high number. I intially
thought it was the number of transaction logs that got loaded into the
standby server but when that number hits 69 and it only copied 3, it doesn't
make sense. There is also no documenation on BOL or microsoft's web site on
this.
Regards,
TimHi Tim,
Based on my research, load_delta indicates the the difference in minutes
between the last updated date of the last backup file and the last updated
date of the last loaded file. In ths code of the sp_log_shipping_in_sync
stored procedure, which is called in sp_get_log_shipping_monitor_info, you
may see the following codes.
SELECT @.delta = DATEDIFF (mi, @.last_updated, @.compare_with)
Also, the @.last_updated is @.restoredt, which is got from the following
codes.
EXECUTE @.rv = sp_log_shipping_get_date_from_file @._primary_database_name,
@.last_backup_filename, @.backupdt OUTPUT
IF (@.rv <> 0)
SElECT @.backupdt = @.last_backup_last_updated
the@.compare_with is @.backupdt, which is got form the followig codes.
EXECUTE @.rv = sp_log_shipping_get_date_from_file @._primary_database_name,
@.last_loaded_filename, @.restoredt OUTPUT
IF (@.rv <> 0)
SElECT @.restoredt = @.last_loaded_last_updated
Regards,
Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.|||Thanks,
this is exactly what I am looking for.
Regards,
Tim
""Yuan Shao"" <v-yshao@.online.microsoft.com> wrote in message
news:PIofhxLNEHA.928@.cpmsftngxa10.phx.gbl...
> Hi Tim,
> Based on my research, load_delta indicates the the difference in minutes
> between the last updated date of the last backup file and the last
updated
> date of the last loaded file. In ths code of the sp_log_shipping_in_sync
> stored procedure, which is called in sp_get_log_shipping_monitor_info, you
> may see the following codes.
> SELECT @.delta = DATEDIFF (mi, @.last_updated, @.compare_with)
> Also, the @.last_updated is @.restoredt, which is got from the following
> codes.
> EXECUTE @.rv = sp_log_shipping_get_date_from_file @._primary_database_name,
> @.last_backup_filename, @.backupdt OUTPUT
> IF (@.rv <> 0)
> SElECT @.backupdt = @.last_backup_last_updated
> the@.compare_with is @.backupdt, which is got form the followig codes.
> EXECUTE @.rv = sp_log_shipping_get_date_from_file @._primary_database_name,
> @.last_loaded_filename, @.restoredt OUTPUT
> IF (@.rv <> 0)
> SElECT @.restoredt = @.last_loaded_last_updated
> Regards,
> Michael Shao
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> This posting is provided "as is" with no warranties and confers no rights.
>
>
EXEC msdb..sp_get_log_shipping_monitor_info @.secondary_database_name = 'pubs%'
I get some information regarding [copy_delta] and [load_delta]
I'm pretty sure copy_delta are there number of files copied over from the
source server. I don't know what the load_delta means though. Sometimes it
shows a low number then sometimes it shows a high number. I intially
thought it was the number of transaction logs that got loaded into the
standby server but when that number hits 69 and it only copied 3, it doesn't
make sense. There is also no documenation on BOL or microsoft's web site on
this.
Regards,
TimHi Tim,
Based on my research, load_delta indicates the the difference in minutes
between the last updated date of the last backup file and the last updated
date of the last loaded file. In ths code of the sp_log_shipping_in_sync
stored procedure, which is called in sp_get_log_shipping_monitor_info, you
may see the following codes.
SELECT @.delta = DATEDIFF (mi, @.last_updated, @.compare_with)
Also, the @.last_updated is @.restoredt, which is got from the following
codes.
EXECUTE @.rv = sp_log_shipping_get_date_from_file @._primary_database_name,
@.last_backup_filename, @.backupdt OUTPUT
IF (@.rv <> 0)
SElECT @.backupdt = @.last_backup_last_updated
the@.compare_with is @.backupdt, which is got form the followig codes.
EXECUTE @.rv = sp_log_shipping_get_date_from_file @._primary_database_name,
@.last_loaded_filename, @.restoredt OUTPUT
IF (@.rv <> 0)
SElECT @.restoredt = @.last_loaded_last_updated
Regards,
Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.|||Thanks,
this is exactly what I am looking for.
Regards,
Tim
""Yuan Shao"" <v-yshao@.online.microsoft.com> wrote in message
news:PIofhxLNEHA.928@.cpmsftngxa10.phx.gbl...
> Hi Tim,
> Based on my research, load_delta indicates the the difference in minutes
> between the last updated date of the last backup file and the last
updated
> date of the last loaded file. In ths code of the sp_log_shipping_in_sync
> stored procedure, which is called in sp_get_log_shipping_monitor_info, you
> may see the following codes.
> SELECT @.delta = DATEDIFF (mi, @.last_updated, @.compare_with)
> Also, the @.last_updated is @.restoredt, which is got from the following
> codes.
> EXECUTE @.rv = sp_log_shipping_get_date_from_file @._primary_database_name,
> @.last_backup_filename, @.backupdt OUTPUT
> IF (@.rv <> 0)
> SElECT @.backupdt = @.last_backup_last_updated
> the@.compare_with is @.backupdt, which is got form the followig codes.
> EXECUTE @.rv = sp_log_shipping_get_date_from_file @._primary_database_name,
> @.last_loaded_filename, @.restoredt OUTPUT
> IF (@.rv <> 0)
> SElECT @.restoredt = @.last_loaded_last_updated
> Regards,
> Michael Shao
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> This posting is provided "as is" with no warranties and confers no rights.
>
>
Monday, March 19, 2012
log shipping job
does anyone know about these tables on msdb: backup_movement_plans and
backup_movement_plan_database? Are they related to log shipping jobs? When we
create the log shipping jobs(copy and load) using script, how the data in
those tables get populated? and how the job know to retreive the data from
the tables? thanksI don't think these tables have anything to do with log shipping. Do you
have any third party applications running on or accessing the database?
Perhaps one such application might have added these tables for handling some
administrative tasks.
--
Anith|||Just found that these are tables from SQL Server 7.0 version which I hadn't
thought about before. Yes, these are valid log shipping related tables in
SQL Server 7.0. The log shipping scheme has changed considerably with SQL
2000 however.
Search for an article by Ron Talmage on log shipping with SQL 7.0 and you
might find some more details about these tables.
--
Anith|||we are currently on 2000 SE version, since has no EE, we have to create the
jobs to do log shipping (copy and load), so do those tables need to manually
created also? thanks
"Anith Sen" wrote:
> Just found that these are tables from SQL Server 7.0 version which I hadn't
> thought about before. Yes, these are valid log shipping related tables in
> SQL Server 7.0. The log shipping scheme has changed considerably with SQL
> 2000 however.
> Search for an article by Ron Talmage on log shipping with SQL 7.0 and you
> might find some more details about these tables.
> --
> Anith
>
>
backup_movement_plan_database? Are they related to log shipping jobs? When we
create the log shipping jobs(copy and load) using script, how the data in
those tables get populated? and how the job know to retreive the data from
the tables? thanksI don't think these tables have anything to do with log shipping. Do you
have any third party applications running on or accessing the database?
Perhaps one such application might have added these tables for handling some
administrative tasks.
--
Anith|||Just found that these are tables from SQL Server 7.0 version which I hadn't
thought about before. Yes, these are valid log shipping related tables in
SQL Server 7.0. The log shipping scheme has changed considerably with SQL
2000 however.
Search for an article by Ron Talmage on log shipping with SQL 7.0 and you
might find some more details about these tables.
--
Anith|||we are currently on 2000 SE version, since has no EE, we have to create the
jobs to do log shipping (copy and load), so do those tables need to manually
created also? thanks
"Anith Sen" wrote:
> Just found that these are tables from SQL Server 7.0 version which I hadn't
> thought about before. Yes, these are valid log shipping related tables in
> SQL Server 7.0. The log shipping scheme has changed considerably with SQL
> 2000 however.
> Search for an article by Ron Talmage on log shipping with SQL 7.0 and you
> might find some more details about these tables.
> --
> Anith
>
>
log shipping job
does anyone know about these tables on msdb: backup_movement_plans and
backup_movement_plan_database? Are they related to log shipping jobs? When we
create the log shipping jobs(copy and load) using script, how the data in
those tables get populated? and how the job know to retreive the data from
the tables? thanks
I don't think these tables have anything to do with log shipping. Do you
have any third party applications running on or accessing the database?
Perhaps one such application might have added these tables for handling some
administrative tasks.
Anith
|||Just found that these are tables from SQL Server 7.0 version which I hadn't
thought about before. Yes, these are valid log shipping related tables in
SQL Server 7.0. The log shipping scheme has changed considerably with SQL
2000 however.
Search for an article by Ron Talmage on log shipping with SQL 7.0 and you
might find some more details about these tables.
Anith
|||we are currently on 2000 SE version, since has no EE, we have to create the
jobs to do log shipping (copy and load), so do those tables need to manually
created also? thanks
"Anith Sen" wrote:
> Just found that these are tables from SQL Server 7.0 version which I hadn't
> thought about before. Yes, these are valid log shipping related tables in
> SQL Server 7.0. The log shipping scheme has changed considerably with SQL
> 2000 however.
> Search for an article by Ron Talmage on log shipping with SQL 7.0 and you
> might find some more details about these tables.
> --
> Anith
>
>
backup_movement_plan_database? Are they related to log shipping jobs? When we
create the log shipping jobs(copy and load) using script, how the data in
those tables get populated? and how the job know to retreive the data from
the tables? thanks
I don't think these tables have anything to do with log shipping. Do you
have any third party applications running on or accessing the database?
Perhaps one such application might have added these tables for handling some
administrative tasks.
Anith
|||Just found that these are tables from SQL Server 7.0 version which I hadn't
thought about before. Yes, these are valid log shipping related tables in
SQL Server 7.0. The log shipping scheme has changed considerably with SQL
2000 however.
Search for an article by Ron Talmage on log shipping with SQL 7.0 and you
might find some more details about these tables.
Anith
|||we are currently on 2000 SE version, since has no EE, we have to create the
jobs to do log shipping (copy and load), so do those tables need to manually
created also? thanks
"Anith Sen" wrote:
> Just found that these are tables from SQL Server 7.0 version which I hadn't
> thought about before. Yes, these are valid log shipping related tables in
> SQL Server 7.0. The log shipping scheme has changed considerably with SQL
> 2000 however.
> Search for an article by Ron Talmage on log shipping with SQL 7.0 and you
> might find some more details about these tables.
> --
> Anith
>
>
Subscribe to:
Comments (Atom)