Is there a way to set up a normal copy from a foreign database to Sql
Server 2000 without hitting the transaction log. We are not concerned
with this as we are only using Sql Server 2000 for reporting purposes,
but the transfer of about 80 files takes about 2 hours and we would like
to cut that down if possible.

Also, is there a way to shrink the log file (it is now 7GB) as it is
empty and will likely stay pretty empty. I was going to copy the
database files to bring back to my office for testing and I don't want
to take an empty log file of 7GB. I suppose I could just create another
log file after attaching the data file to my system.

Lastly, how do I find out how much of the file is filled (for example
the Tran log is 7GB, but should be empty now).

Thanks,

Tom.

You will always hit the T Log in some shape or form. I presume you mean the
destination log file.

Examples of minimising this hit/+ speeding things up would be to

1. Change recovery model to SIMPLE on destination.
2. Minimise indexes on destination
3. Remove triggers on destination


Are these DBs on the same server? Are you seeing Netowrk slowdown?

Have a look at these articles to see about reducing file sizes


http://www.support.microsoft.com/?id=317375 Log File Grows too big
http://www.support.microsoft.com/?id=110139 Log file filling up
http://www.mssqlserver.com/faq/logs-shrinklog.asp Shrink File
http://www.support.microsoft.com/?id=315512 Considerations for Autogrow
and AutoShrink
http://www.support.microsoft.com/?id=256650 INF: How to Shrink the SQL
Server 7.0 Tran Log
http://www.support.microsoft.com/?id=272318 INF: Shrinking Log in SQL
Server 2000 with DBCC SHRINKFILE


--

----------------------------

Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org


"Thomas Scheiderich" <tfs (AT) deltanet (DOT) com> wrote