Data compression over "low bandwidth" lines

Does anyone know a wayto compress data between two database connections over "low bandwidth" lines in order to speedup datatransfer?
Used connections are Oracle<->SQL2000 and SQL2000<->SQL2000.Use a VPN that supports compression to manage the TCP/IP connection?

-PatP|||VPN will slow down the transmission. If I m not wrong , the VPN does encryption rather than compression. What have you implemented to sync both oracle to SQL server database?|||Found the IPTunnelManager: www.apbsoft.com

Data Compression Applicability

Hi,

Can you tell me whether the compression intended for Katmai is suitable for OLTP applications?

I know that Oracle has had compression for a number of years, but it is not particularly useful for tables subject to a reasonable degree of inserts/updates. It would be great if Katmai compression could be used across the board with substantial space savings for every application type. What's the story ?

Many Thanks,

Derek

The main focus for this release is data warehouse scenarios, but we have a compression scheme that might be useful for OLTP applications as well.

We will be supporting compressing for both bulk load and normal DML operations.

More information will come when compression becomes part of a future CTP.

Thanks,

Data communication compression?

Hi,
Do you know if there is any tool which can compress the trafic between a
client and an SQL server?
I really talk about communication compression NOT storage compression.
We have some remote sites with a low bandwidth and they have to upload some
data every week. its too slow today.
so if there is no option to compress the communication himself, I'll change
the strategy to export, zip, and copy the file. but this method add a layer
of complexity in the process so I prefer to not do this.
thanks for your guides.
Jerome.
On Jun 11, 2:15 pm, "Jeje" <willg...@.hotmail.com> wrote:
> Hi,
> Do you know if there is any tool which can compress the trafic between a
> client and an SQL server?
> I really talk about communication compression NOT storage compression.
> We have some remote sites with a low bandwidth and they have to upload some
> data every week. its too slow today.
> so if there is no option to compress the communication himself, I'll change
> the strategy to export, zip, and copy the file. but this method add a layer
> of complexity in the process so I prefer to not do this.
> thanks for your guides.
> Jerome.
Hi Jerome
This would be something done at the lowest network layers as the
actual format of the packets needs to be the same for SQL Server to
understand them.
If you are doing a total data refresh then to cut down what you
transfer you may want to consider only distributing a differences. If
the data is rarely queries and response then maybe something like
using SOAP may be an alternative to your database.
John

Data communication compression?

Hi,
Do you know if there is any tool which can compress the trafic between a
client and an SQL server?
I really talk about communication compression NOT storage compression.
We have some remote sites with a low bandwidth and they have to upload some
data every week. its too slow today.
so if there is no option to compress the communication himself, I'll change
the strategy to export, zip, and copy the file. but this method add a layer
of complexity in the process so I prefer to not do this.
thanks for your guides.
Jerome.On Jun 11, 2:15 pm, "Jeje" <willg...@.hotmail.com> wrote:
> Hi,
> Do you know if there is any tool which can compress the trafic between a
> client and an SQL server?
> I really talk about communication compression NOT storage compression.
> We have some remote sites with a low bandwidth and they have to upload some
> data every week. its too slow today.
> so if there is no option to compress the communication himself, I'll change
> the strategy to export, zip, and copy the file. but this method add a layer
> of complexity in the process so I prefer to not do this.
> thanks for your guides.
> Jerome.
Hi Jerome
This would be something done at the lowest network layers as the
actual format of the packets needs to be the same for SQL Server to
understand them.
If you are doing a total data refresh then to cut down what you
transfer you may want to consider only distributing a differences. If
the data is rarely queries and response then maybe something like
using SOAP may be an alternative to your database.
John

Data communication compression?

Hi,
Do you know if there is any tool which can compress the trafic between a
client and an SQL server?
I really talk about communication compression NOT storage compression.
We have some remote sites with a low bandwidth and they have to upload some
data every week. its too slow today.
so if there is no option to compress the communication himself, I'll change
the strategy to export, zip, and copy the file. but this method add a layer
of complexity in the process so I prefer to not do this.
thanks for your guides.
Jerome.On Jun 11, 2:15 pm, "Jeje" <willg...@.hotmail.com> wrote:
> Hi,
> Do you know if there is any tool which can compress the trafic between a
> client and an SQL server?
> I really talk about communication compression NOT storage compression.
> We have some remote sites with a low bandwidth and they have to upload som
e
> data every week. its too slow today.
> so if there is no option to compress the communication himself, I'll chang
e
> the strategy to export, zip, and copy the file. but this method add a laye
r
> of complexity in the process so I prefer to not do this.
> thanks for your guides.
> Jerome.
Hi Jerome
This would be something done at the lowest network layers as the
actual format of the packets needs to be the same for SQL Server to
understand them.
If you are doing a total data refresh then to cut down what you
transfer you may want to consider only distributing a differences. If
the data is rarely queries and response then maybe something like
using SOAP may be an alternative to your database.
John