Log Shipping NTFS compressed files WAN

If the compression attribute is set on both the source SQL Server directory
and the target SQL Server directory for a log shipping configuration, will
the log files be uncompressed and then recompressed when the copy is made?
Or will the files remain compressed while the copy is taking place? If
WIN2K and SS are smart enough to handle the latter, it will speed up the
transfer of files across a WAN link.This is purely an OS thing, nothing to do with SQL.
See the quote from the following KB article
http://support.microsoft.com/?kbid=251186
When you copy or move a compressed NTFS file to a different folder, NTFS
decompresses the file, copies or moves the file to the new location, and
then recompresses the file. This behavior occurs even when the file is
copied or moved between folders on the same computer. Compressed files are
also expanded before copying over the network, so NTFS compression does not
save network bandwidth
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Don Ferguson" <don@.nospamplease> wrote in message
news:eVy5m1wRDHA.1552@.TK2MSFTNGP10.phx.gbl...
If the compression attribute is set on both the source SQL Server directory
and the target SQL Server directory for a log shipping configuration, will
the log files be uncompressed and then recompressed when the copy is made?
Or will the files remain compressed while the copy is taking place? If
WIN2K and SS are smart enough to handle the latter, it will speed up the
transfer of files across a WAN link.|||Thanks Jasper!
Your response and the KB link answers my question even if this has nothing
to do with SQL Server.
I guess I need to look into SQL LiteSpeed or SQLZIP for a possible solution.
"Jasper Smith" <jasper_smith9@.hotmail.com> wrote in message
news:OZtmZexRDHA.2128@.TK2MSFTNGP12.phx.gbl...
> This is purely an OS thing, nothing to do with SQL.
> See the quote from the following KB article
> http://support.microsoft.com/?kbid=251186
> When you copy or move a compressed NTFS file to a different folder, NTFS
> decompresses the file, copies or moves the file to the new location, and
> then recompresses the file. This behavior occurs even when the file is
> copied or moved between folders on the same computer. Compressed files are
> also expanded before copying over the network, so NTFS compression does
not
> save network bandwidth
> --
> HTH
> Jasper Smith (SQL Server MVP)
> I support PASS - the definitive, global
> community for SQL Server professionals -
> http://www.sqlpass.org
> "Don Ferguson" <don@.nospamplease> wrote in message
> news:eVy5m1wRDHA.1552@.TK2MSFTNGP10.phx.gbl...
> If the compression attribute is set on both the source SQL Server
directory
> and the target SQL Server directory for a log shipping configuration, will
> the log files be uncompressed and then recompressed when the copy is made?
> Or will the files remain compressed while the copy is taking place? If
> WIN2K and SS are smart enough to handle the latter, it will speed up the
> transfer of files across a WAN link.
>
>|||I'm a big fan of SQL Litespeed, does exactly what it says on the tin :-)
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Don Ferguson" <don@.nospamplease> wrote in message
news:evh15xxRDHA.2316@.tk2msftngp13.phx.gbl...
Thanks Jasper!
Your response and the KB link answers my question even if this has nothing
to do with SQL Server.
I guess I need to look into SQL LiteSpeed or SQLZIP for a possible solution.
"Jasper Smith" <jasper_smith9@.hotmail.com> wrote in message
news:OZtmZexRDHA.2128@.TK2MSFTNGP12.phx.gbl...
> This is purely an OS thing, nothing to do with SQL.
> See the quote from the following KB article
> http://support.microsoft.com/?kbid=251186
> When you copy or move a compressed NTFS file to a different folder, NTFS
> decompresses the file, copies or moves the file to the new location, and
> then recompresses the file. This behavior occurs even when the file is
> copied or moved between folders on the same computer. Compressed files are
> also expanded before copying over the network, so NTFS compression does
not
> save network bandwidth
> --
> HTH
> Jasper Smith (SQL Server MVP)
> I support PASS - the definitive, global
> community for SQL Server professionals -
> http://www.sqlpass.org
> "Don Ferguson" <don@.nospamplease> wrote in message
> news:eVy5m1wRDHA.1552@.TK2MSFTNGP10.phx.gbl...
> If the compression attribute is set on both the source SQL Server
directory
> and the target SQL Server directory for a log shipping configuration, will
> the log files be uncompressed and then recompressed when the copy is made?
> Or will the files remain compressed while the copy is taking place? If
> WIN2K and SS are smart enough to handle the latter, it will speed up the
> transfer of files across a WAN link.
>
>

Log Shipping copy with compression

I've got several secondary servers setup against my production server, and
working fine. However, one is across a t-1, and the file copying can really
effect latency across this link.
I've been searching far an wide for a "replicator" that has a client server
component, that can do streaming compression. TRNs compress down incrediably
well. I could use a util to zip them to a unc, and then unzip on the other
side, but this seems dumb. Why oh why doesn't SMB support compression...we
have gone backwards since the z-modem days .
I'm trying to get rsync to work using cygwin, but of course it is a pain in
the butt. Does anyone know of affoardable software that does this seamly
simple task. I'm about to program my own.
Compression has been considered on the packet level, but the reason that it
is not implemented is that in general the data travelling across the wire is
binary and the compression ratio and cost involved in compressing binary
data outweighs the savings in doing so. Compressing purely textual data does
provide much better compression.
Your best bet is to zip then before sending, and then unzip them on the
other end.
"et" <et@.discussions.microsoft.com> wrote in message
news:83CF2440-9764-47D7-8163-AE47C3106035@.microsoft.com...
> I've got several secondary servers setup against my production server, and
> working fine. However, one is across a t-1, and the file copying can
really
> effect latency across this link.
> I've been searching far an wide for a "replicator" that has a client
server
> component, that can do streaming compression. TRNs compress down
incrediably
> well. I could use a util to zip them to a unc, and then unzip on the other
> side, but this seems dumb. Why oh why doesn't SMB support compression...we
> have gone backwards since the z-modem days .
> I'm trying to get rsync to work using cygwin, but of course it is a pain
in
> the butt. Does anyone know of affoardable software that does this seamly
> simple task. I'm about to program my own.
>
|||As I recall Windows 2003 was supposed to offer SMB copying of NTFS compressed
files from server to server without uncompressing in the middle.
But as I've never seen that feature advertised, I'm guessing it never made the
cut before release.

> I've been searching far an wide for a "replicator" that has a client server
> component, that can do streaming compression. TRNs compress down incrediably
> well. I could use a util to zip them to a unc, and then unzip on the other
> side, but this seems dumb. Why oh why doesn't SMB support compression...we
> have gone backwards since the z-modem days .
> I'm trying to get rsync to work using cygwin, but of course it is a pain in
> the butt. Does anyone know of affoardable software that does this seamly
> simple task. I'm about to program my own.
>
Neil Pike. Protech Computing Ltd
Reply here - no email
SQL FAQ (484 entries) see
http://forumsb.compuserve.com/gvforu...?SRV=MSDevApps
(faqxxx.zip in lib 7)
or http://www.ntfaq.com/Articles/Index...partmentID=800
or www.sqlserverfaq.com
or www.mssqlserver.com/faq