Remove inactive entries from transaction log and log shipping

When I try to take a Transaction log backup of a database (Recovery model
set to Full), I get an option to truncate the transaction log by checking
"Remove inactive entries from transaction log" check box in the backup
dialog. This basically causes the inactive portion of the transaction log
(where transaction is completes, either rolled back are committed) to be
truncated. So this potentially leads to saving of huge amount of hard disk
space.
Now, when I setup log shipping is there any similar option I can set on the
primary database? After every transaction log backup I want inactive entries
from the transaction log to be removed. Is there any way to do this? If yes,
how?. If no, why is that so? Once the backup is taken inactive log entries
on the primary database are of no use to log ship, right?
Rathna RajThe option in the backup dialog is very misleading. It basically means that
EM does *not* send the WITH NO_TRUNCATE option. This option is designed for
doing an "emergency" backup in case the database is corrupted, and I have
communicated to MS that the dialog shouldn't be misleading in this way. The
normal way to do log backup is by not specifying this option (having the
checkbox checked (I believe), the default). If the log shipping was written
by a sane individual ;-), then it should not specify this option, I.e., you
already have the desired behavior. To be certain, use a Profiler trace to
see what is going on.
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Rathna Raj" <RathnaRajT@.icode.com> wrote in message
news:%2365JEWJyDHA.1272@.TK2MSFTNGP12.phx.gbl...
> When I try to take a Transaction log backup of a database (Recovery model
> set to Full), I get an option to truncate the transaction log by checking
> "Remove inactive entries from transaction log" check box in the backup
> dialog. This basically causes the inactive portion of the transaction log
> (where transaction is completes, either rolled back are committed) to be
> truncated. So this potentially leads to saving of huge amount of hard disk
> space.
> Now, when I setup log shipping is there any similar option I can set on
the
> primary database? After every transaction log backup I want inactive
entries
> from the transaction log to be removed. Is there any way to do this? If
yes,
> how?. If no, why is that so? Once the backup is taken inactive log entries
> on the primary database are of no use to log ship, right?
> Rathna Raj
>|||Hi Rathna,
Thanks for your post. Based on my research, log shipping does done backup
log part, so transaction log should not be large. Therefore, it seems that
truncating the transaction log of the primary server manually in log
shipping is not necessary.
For more information regarding log shipping, please refer to the following
article on SQL Server Books Online. Also, the example in this article will
help describe how the log shipping works.
Topic; "Log Shipping"
Thanks for using MSDN newsgroup.
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.sql

Remote replication question

I'm not a db person so please excuse any simplicity or lack of clarity in my
question.
My company currently uses a model of remote employees updating MS Access dbs
and then transferring those dbs to the main office where they are merged with
a main Access db. The remote employees are disconnected from the company
domain/network during their workday.
The plan is to migrate the Access dbs into SQL 2000 (or 2005?) and then set
up some sort of replication topology that will allow the remote employees to
replicate their daily updates/entries to the SQL Server at the main office.
My questions are:
1) What are the possibilities for the db on the remote machines? Can MS
Access be used on the client side and the Access data replicated to the SQL
server (and if so, would data transformation be necessary?)
2) Can MSDE be used on the remote clients? If so what are the possibilities
for a front end to the client MSDE dbs?
3) How can the replication be done over the internet? I believe VPN and ftp
are possibilities and I think SSL would be a possibility if SQL 2005 is used,
can anyone point me to documentation on how to best setup replication between
the remote clients and the SQL server in the main office.
Thanks
Ideally, MSDE would be used for the sql server replication. In this case you
can't have MSDE publishers of transactional replication, so merge would be
used, with the head office as a publisher and the MSDE databases as
subscribers. This can be best done over a VPN for security. Replication over
the internet is also possible (in SQL 2000 you'd use certificates and TCP/IP
while in SQL Server 2005 you can use HTTPS). For the former option, please
check out this article:
http://www.replicationanswers.com/InternetArticle.asp
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)