New Question Regarding LOG SHIPPING & MASTERDB

I got log shipping to partially work *lol* any how what my new issue is,
the masterdb, any good documentation? Ive tried searching google and find
very little on that matter.

Thank youI guess I forgot to mention this is SQL 2000 Enterprise.

Sorry :) and thank you in advance|||You don't need to log ship your master database. It should be small
enough that you can back it up when you need to. Back it up once a day
and whenever you make changes to your other databases ie add or drop a
database, change size etc. In most cases your master might go days or
even weeks without any changes.

smyers1972 wrote:
> I guess I forgot to mention this is SQL 2000 Enterprise.
> Sorry :) and thank you in advance|||Thank you I will try it out and see if I can restore it... I tried to
restore it before but had drive location issues i.e. logs were on drive L
but on the log ship to server they are drive D, i reworked the scheme and
made them identical to the original box... will see how it goes...
Thanks!

New indexes not shipped to secondary server

I am running SQL 2k on WinS2003 servers. We are using Log Shipping,
leaving our secondary in a Read-Only state to be used for reporting. I
have a need to get a new index on the secondary server (to decrease the
14 hour run time for a report). Our primary is in Full Recovery mode
as well.
I have created the index on my primary and expected it to be created on
the secondary when the logs were shipped this morning, only to find
that the Index was not created on the secondary.
I am not very familiar with Log Shipping and our in house expert is
unavailable.
Any thoughts on what gives?
I would even take pointers on where to start looking to find the
problem.
Meredith Ryan> I have created the index on my primary and expected it to be created on
> the secondary when the logs were shipped this morning, only to find
> that the Index was not created on the secondary.
>
You need the logs shipped AND applied for this to occur.
"mryan" <coffegrl@.gmail.com> wrote in message
news:1143761656.789619.3450@.v46g2000cwv.googlegroups.com...
> I am running SQL 2k on WinS2003 servers. We are using Log Shipping,
> leaving our secondary in a Read-Only state to be used for reporting. I
> have a need to get a new index on the secondary server (to decrease the
> 14 hour run time for a report). Our primary is in Full Recovery mode
> as well.
> I have created the index on my primary and expected it to be created on
> the secondary when the logs were shipped this morning, only to find
> that the Index was not created on the secondary.
> I am not very familiar with Log Shipping and our in house expert is
> unavailable.
> Any thoughts on what gives?
> I would even take pointers on where to start looking to find the
> problem.
> Meredith Ryan
>|||The logs had been applied. I guess I should have been a bit more
specific.

New indexes not shipped to secondary server

I am running SQL 2k on WinS2003 servers. We are using Log Shipping,
leaving our secondary in a Read-Only state to be used for reporting. I
have a need to get a new index on the secondary server (to decrease the
14 hour run time for a report). Our primary is in Full Recovery mode
as well.
I have created the index on my primary and expected it to be created on
the secondary when the logs were shipped this morning, only to find
that the Index was not created on the secondary.
I am not very familiar with Log Shipping and our in house expert is
unavailable.
Any thoughts on what gives?
I would even take pointers on where to start looking to find the
problem.
Meredith Ryan
> I have created the index on my primary and expected it to be created on
> the secondary when the logs were shipped this morning, only to find
> that the Index was not created on the secondary.
>
You need the logs shipped AND applied for this to occur.
"mryan" <coffegrl@.gmail.com> wrote in message
news:1143761656.789619.3450@.v46g2000cwv.googlegrou ps.com...
> I am running SQL 2k on WinS2003 servers. We are using Log Shipping,
> leaving our secondary in a Read-Only state to be used for reporting. I
> have a need to get a new index on the secondary server (to decrease the
> 14 hour run time for a report). Our primary is in Full Recovery mode
> as well.
> I have created the index on my primary and expected it to be created on
> the secondary when the logs were shipped this morning, only to find
> that the Index was not created on the secondary.
> I am not very familiar with Log Shipping and our in house expert is
> unavailable.
> Any thoughts on what gives?
> I would even take pointers on where to start looking to find the
> problem.
> Meredith Ryan
>
|||The logs had been applied. I guess I should have been a bit more
specific.

New indexes not shipped to secondary server

I am running SQL 2k on WinS2003 servers. We are using Log Shipping,
leaving our secondary in a Read-Only state to be used for reporting. I
have a need to get a new index on the secondary server (to decrease the
14 hour run time for a report). Our primary is in Full Recovery mode
as well.
I have created the index on my primary and expected it to be created on
the secondary when the logs were shipped this morning, only to find
that the Index was not created on the secondary.
I am not very familiar with Log Shipping and our in house expert is
unavailable.
Any thoughts on what gives?
I would even take pointers on where to start looking to find the
problem.
Meredith Ryan> I have created the index on my primary and expected it to be created on
> the secondary when the logs were shipped this morning, only to find
> that the Index was not created on the secondary.
>
You need the logs shipped AND applied for this to occur.
"mryan" <coffegrl@.gmail.com> wrote in message
news:1143761656.789619.3450@.v46g2000cwv.googlegroups.com...
> I am running SQL 2k on WinS2003 servers. We are using Log Shipping,
> leaving our secondary in a Read-Only state to be used for reporting. I
> have a need to get a new index on the secondary server (to decrease the
> 14 hour run time for a report). Our primary is in Full Recovery mode
> as well.
> I have created the index on my primary and expected it to be created on
> the secondary when the logs were shipped this morning, only to find
> that the Index was not created on the secondary.
> I am not very familiar with Log Shipping and our in house expert is
> unavailable.
> Any thoughts on what gives?
> I would even take pointers on where to start looking to find the
> problem.
> Meredith Ryan
>|||The logs had been applied. I guess I should have been a bit more
specific.