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