|
SQLCompress.NET 2.0 Beta Announced |
|
Written by SQLCompress.NET Support
|
|
May 09, 2008 at 06:39 AM |
|
SQLCompress.NET team has been quietly working on a new version for SQL Server 2008! |
|
Last Updated ( May 09, 2008 at 06:49 AM )
|
|
Read more...
|
|
|
Which compression implementation should I use? |
|
Written by SQLCompress.NET Support
|
|
Jan 20, 2007 at 09:40 AM |
|
SQLCompress.NET provides several implementations:
- Fast Deflate (recommended): This implementation is VERY fast with very little overhead.
- Base or Benchmark: This implementation should NOT be used for compression. This is included for benchmarking purposes ONLY. It allows developers to determine how much overhead their compression libraries add to an implementation. The implementation does not compresses anything but does add block and compression headers increasing LOB size.
We recommend the use of Fast Deflate for compression purposes and Basic (or Benchmark) for comparison purposes.
|
|
Last Updated ( Feb 13, 2007 at 11:53 PM )
|
|
|
Improving Data Transfer With SQLCompress.NET |
|
Written by SQLCompress.NET Support
|
|
Nov 19, 2005 at 07:34 AM |
|
Microsoft SQL Server provides three types of replication as a synchronization mechanism: Snapshot, Transactional and Merge replication. All these replications deliver transactions or snapshots to remote servers over a LAN or WAN. This can be bandwidth intensive which in turn delays the synchronization process.
SQLCompress.NET allows compression on variable length columns (not only blobs) reducing bandwidth usage and improving performance by:
- Reducing the amount of replicated data
- Reducing snapshot size
- Reducing disk utilization
Write Comment (1044 comments) |
|
Last Updated ( Jan 05, 2007 at 01:18 PM )
|
|
Read more...
|
|
|
|
