Log Shipping Transaction Logs.

Hi,

We currently have a couple a large Databases running on SQL 2000 SP3 Clustered Windows 2000 SP3 environment.

Log Shipping is enabled for both databases shipping to a Standalone SQL 2000 SP3 Windows 2000 SP3 box.

Log Shipping occurs every 15 mins with the Transaction Files on average being no more than 500KB in size. However, every now and then a Transaction Log comes through and it can be as big as 3.52GB.

Not sure why this is happening. Anyone got any ideas?

Regards

Paul TowlerIs this after substantial activity or reindexing?|||i think auto shrink or some other job is enabled
if iam right, the auto shrink or job gets activated and the step goes thru
which will obviously create transaction file with huge size.|||Thanks for your replies.

There is a Job to Optimise the Database which does re-index the database. I presume all the indexing changes count as changes and therefore shipped as one big Transacton file.

Hopefully there is a way to prevent these hugh Transaction Files without turning off the indexing job.

Regards
Paul Towlersql

log shipping and Full text indexing

We have FT Indexing service enabled ? How do I know if we have any full text
indexes and when I log ship and/or backup my databases in SQL 2005, does it
take care of it as well or do I have to manually move them to the other
server and back them up ?
Using SQL 2005
ThanksOn your database, go to Storage and Full Text Catalogs. See if you have any
full text catalogs there.
A full database backup also takes care of backing up your full text
catalogs. Since log shipping uses a database backup to initialize the
secondary database, the full text catalog is restored as well on this
database.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Hassan" wrote:

> We have FT Indexing service enabled ? How do I know if we have any full te
xt
> indexes and when I log ship and/or backup my databases in SQL 2005, does i
t
> take care of it as well or do I have to manually move them to the other
> server and back them up ?
> Using SQL 2005
> Thanks
>|||On your database, go to Storage and Full Text Catalogs. See if you have any
full text catalogs there.
A full database backup also takes care of backing up your full text
catalogs. Since log shipping uses a database backup to initialize the
secondary database, the full text catalog is restored as well on this
database.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Hassan" wrote:

> We have FT Indexing service enabled ? How do I know if we have any full te
xt
> indexes and when I log ship and/or backup my databases in SQL 2005, does i
t
> take care of it as well or do I have to manually move them to the other
> server and back them up ?
> Using SQL 2005
> Thanks
>

log shipping and Full text indexing

We have FT Indexing service enabled ? How do I know if we have any full text
indexes and when I log ship and/or backup my databases in SQL 2005, does it
take care of it as well or do I have to manually move them to the other
server and back them up ?
Using SQL 2005
Thanks
On your database, go to Storage and Full Text Catalogs. See if you have any
full text catalogs there.
A full database backup also takes care of backing up your full text
catalogs. Since log shipping uses a database backup to initialize the
secondary database, the full text catalog is restored as well on this
database.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Hassan" wrote:

> We have FT Indexing service enabled ? How do I know if we have any full text
> indexes and when I log ship and/or backup my databases in SQL 2005, does it
> take care of it as well or do I have to manually move them to the other
> server and back them up ?
> Using SQL 2005
> Thanks
>
|||On your database, go to Storage and Full Text Catalogs. See if you have any
full text catalogs there.
A full database backup also takes care of backing up your full text
catalogs. Since log shipping uses a database backup to initialize the
secondary database, the full text catalog is restored as well on this
database.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Hassan" wrote:

> We have FT Indexing service enabled ? How do I know if we have any full text
> indexes and when I log ship and/or backup my databases in SQL 2005, does it
> take care of it as well or do I have to manually move them to the other
> server and back them up ?
> Using SQL 2005
> Thanks
>

log shipping and Full text indexing

We have FT Indexing service enabled ? How do I know if we have any full text
indexes and when I log ship and/or backup my databases in SQL 2005, does it
take care of it as well or do I have to manually move them to the other
server and back them up ?
Using SQL 2005
ThanksOn your database, go to Storage and Full Text Catalogs. See if you have any
full text catalogs there.
A full database backup also takes care of backing up your full text
catalogs. Since log shipping uses a database backup to initialize the
secondary database, the full text catalog is restored as well on this
database.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Hassan" wrote:
> We have FT Indexing service enabled ? How do I know if we have any full text
> indexes and when I log ship and/or backup my databases in SQL 2005, does it
> take care of it as well or do I have to manually move them to the other
> server and back them up ?
> Using SQL 2005
> Thanks
>|||On your database, go to Storage and Full Text Catalogs. See if you have any
full text catalogs there.
A full database backup also takes care of backing up your full text
catalogs. Since log shipping uses a database backup to initialize the
secondary database, the full text catalog is restored as well on this
database.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Hassan" wrote:
> We have FT Indexing service enabled ? How do I know if we have any full text
> indexes and when I log ship and/or backup my databases in SQL 2005, does it
> take care of it as well or do I have to manually move them to the other
> server and back them up ?
> Using SQL 2005
> Thanks
>