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.