Log Shipping vs. ASE Replicator vs. Replication Server

Dear all,

We have recently looked into buying Replication Server, but
potentially have decided not to move forward.

We are looking into ASE Replicator or Log Shipping instead. 
What are your thoughts about both strategies (database is
about 30 GB in size, can afford up to 2 hour down time,
etc.)?

We first got a quote for Replication Server and were under
the impression that since Replication Server only uses one
CPU, you only have to pay for a single CPU license.  We just
learned today that since we have a 8 CPU server, we will
have to pay for a 8 CPU license.  They gave us a price
breakdown like...

Replication Server License Costs:

1 CPU = $10,000
2 CPU = $20,000
3 CPU = $30,000
etc..

First we are shocked that the CPU costs jump up so
aggresively.  Especailly since we have a 8 CPU box.

So with this in mind... Is Log Shipping or ASE Replicator a
realistic option for a Warm Standby solution?
0
Susan
7/14/2008 11:40:05 AM
sybase.ase.administration 7058 articles. 2 followers. Follow

12 Replies
2324 Views

Similar Articles

[PageSpeed] 32

Have you looked into purchasing more of a commodity box for repserver?  Why 
do you need an 8-cpu platform to run repserver?

A decent dual-core G3 running Linux RedHat/SUSE could do the job for you at 
a greatly reduced price.

Replicator is probably out of the question as it can very quickly reach a 
ceiling regarding throughput.  Of course this all depends on how much 
replication activity is required.

Log shipping can work, and I've seen others on these and other forums tout 
it's capabilities.  If you are not going down the replication server path, 
this would probably be my choice.

<Susan Mills> wrote in message news:487b3b15.77c1.1681692777@sybase.com...
> Dear all,
>
> We have recently looked into buying Replication Server, but
> potentially have decided not to move forward.
>
> We are looking into ASE Replicator or Log Shipping instead.
> What are your thoughts about both strategies (database is
> about 30 GB in size, can afford up to 2 hour down time,
> etc.)?
>
> We first got a quote for Replication Server and were under
> the impression that since Replication Server only uses one
> CPU, you only have to pay for a single CPU license.  We just
> learned today that since we have a 8 CPU server, we will
> have to pay for a 8 CPU license.  They gave us a price
> breakdown like...
>
> Replication Server License Costs:
>
> 1 CPU = $10,000
> 2 CPU = $20,000
> 3 CPU = $30,000
> etc..
>
> First we are shocked that the CPU costs jump up so
> aggresively.  Especailly since we have a 8 CPU box.
>
> So with this in mind... Is Log Shipping or ASE Replicator a
> realistic option for a Warm Standby solution? 


0
Sherlock
7/14/2008 1:58:16 PM
On Jul 14, 1:40=A0pm, Susan Mills wrote:
> Dear all,
>
> We have recently looked into buying Replication Server, but
> potentially have decided not to move forward.
>
> We are looking into ASE Replicator or Log Shipping instead.
> What are your thoughts about both strategies (database is
> about 30 GB in size, can afford up to 2 hour down time,
> etc.)?
>
> We first got a quote for Replication Server and were under
> the impression that since Replication Server only uses one
> CPU, you only have to pay for a single CPU license. =A0We just
> learned today that since we have a 8 CPU server, we will
> have to pay for a 8 CPU license. =A0They gave us a price
> breakdown like...
>
> Replication Server License Costs:
>
> 1 CPU =3D $10,000
> 2 CPU =3D $20,000
> 3 CPU =3D $30,000
> etc..
>
> First we are shocked that the CPU costs jump up so
> aggresively. =A0Especailly since we have a 8 CPU box.
>
> So with this in mind... Is Log Shipping or ASE Replicator a
> realistic option for a Warm Standby solution?

I wouldn't use ASE replicator for anything like this. However, log
shipping is certainly feasible, especially if a 2 hour downtime is
acceptable.
The setup is pretty straightforward - you have to write some scripts,
but they should be pretty straightforward - and with a 30GB db it is
feasible to do a full resync fairly often if your IO subsystem is
reasonably fast.

Michael
0
mpeppler
7/14/2008 2:02:12 PM
Thank you both for your quick response and great feedback. 
I just learned that the database size is only 1 GB.  This
may even be more the reason to use Log Shipping instead of
buying a full license for Replication Server.

Thank you for all your help!



> On Jul 14, 1:40=a0pm, Susan Mills wrote:
> > Dear all,
> >
> > We have recently looked into buying Replication Server,
> > but potentially have decided not to move forward.
> >
> > We are looking into ASE Replicator or Log Shipping
> > instead. What are your thoughts about both strategies
> > (database is about 30 GB in size, can afford up to 2
> > hour down time, etc.)?
> >
> > We first got a quote for Replication Server and were
> > under the impression that since Replication Server only
> > uses one CPU, you only have to pay for a single CPU
> > license. =a0We just learned today that since we have a 8
> > CPU server, we will have to pay for a 8 CPU license.
> > =a0They gave us a price breakdown like...
> >
> > Replication Server License Costs:
> >
> > 1 CPU =3d $10,000
> > 2 CPU =3d $20,000
> > 3 CPU =3d $30,000
> > etc..
> >
> > First we are shocked that the CPU costs jump up so
> > aggresively. =a0Especailly since we have a 8 CPU box.
> >
> > So with this in mind... Is Log Shipping or ASE
> > Replicator a realistic option for a Warm Standby
> solution?
>
> I wouldn't use ASE replicator for anything like this.
> However, log shipping is certainly feasible, especially if
> a 2 hour downtime is acceptable.
> The setup is pretty straightforward - you have to write
> some scripts, but they should be pretty straightforward -
> and with a 30GB db it is feasible to do a full resync
> fairly often if your IO subsystem is reasonably fast.
>
> Michael
0
Susan
7/15/2008 1:41:58 AM
This is a multi-part message in MIME format.
--------------070006090806020607080405
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Michael,

If everything is  

>is pretty straightforward



then why Sybase does not provide adequate scripts 
(like Oracle and MS) and why Rep.Server is the huge product ?
Unfortunately "devil is always in details" I think.

Regards,
Eugene


mpeppler@peppler.org wrote:

>On Jul 14, 1:40 pm, Susan Mills wrote:
>  
>
>>Dear all,
>>
>>We have recently looked into buying Replication Server, but
>>potentially have decided not to move forward.
>>
>>We are looking into ASE Replicator or Log Shipping instead.
>>What are your thoughts about both strategies (database is
>>about 30 GB in size, can afford up to 2 hour down time,
>>etc.)?
>>
>>We first got a quote for Replication Server and were under
>>the impression that since Replication Server only uses one
>>CPU, you only have to pay for a single CPU license.  We just
>>learned today that since we have a 8 CPU server, we will
>>have to pay for a 8 CPU license.  They gave us a price
>>breakdown like...
>>
>>Replication Server License Costs:
>>
>>1 CPU = $10,000
>>2 CPU = $20,000
>>3 CPU = $30,000
>>etc..
>>
>>First we are shocked that the CPU costs jump up so
>>aggresively.  Especailly since we have a 8 CPU box.
>>
>>So with this in mind... Is Log Shipping or ASE Replicator a
>>realistic option for a Warm Standby solution?
>>    
>>
>
>I wouldn't use ASE replicator for anything like this. However, log
>shipping is certainly feasible, especially if a 2 hour downtime is
>acceptable.
>The setup is pretty straightforward - you have to write some scripts,
>but they should be pretty straightforward - and with a 30GB db it is
>feasible to do a full resync fairly often if your IO subsystem is
>reasonably fast.
>
>Michael
>  
>


--------------070006090806020607080405
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
  <title></title>
</head>
<body bgcolor="#99ffff" text="#000099">
Michael,<br>
<br>
If everything is&nbsp;&nbsp;
<pre wrap=""><blockquote type="cite"><pre wrap="">is pretty straightforward</pre></blockquote>

then why Sybase does not provide adequate scripts 
(like Oracle and MS) and why Rep.Server is the huge product ?
Unfortunately "devil is always in details" I think.

Regards,
Eugene

</pre>
<pre wrap="">
</pre>
<a class="moz-txt-link-abbreviated" href="mailto:mpeppler@peppler.org">mpeppler@peppler.org</a> wrote:<br>
<blockquote
 cite="mid3c0b57b7-08bb-4a0e-8ac0-2b4a9134417c@x41g2000hsb.googlegroups.com"
 type="cite">
  <pre wrap="">On Jul 14, 1:40&nbsp;pm, Susan Mills wrote:
  </pre>
  <blockquote type="cite">
    <pre wrap="">Dear all,

We have recently looked into buying Replication Server, but
potentially have decided not to move forward.

We are looking into ASE Replicator or Log Shipping instead.
What are your thoughts about both strategies (database is
about 30 GB in size, can afford up to 2 hour down time,
etc.)?

We first got a quote for Replication Server and were under
the impression that since Replication Server only uses one
CPU, you only have to pay for a single CPU license. &nbsp;We just
learned today that since we have a 8 CPU server, we will
have to pay for a 8 CPU license. &nbsp;They gave us a price
breakdown like...

Replication Server License Costs:

1 CPU = $10,000
2 CPU = $20,000
3 CPU = $30,000
etc..

First we are shocked that the CPU costs jump up so
aggresively. &nbsp;Especailly since we have a 8 CPU box.

So with this in mind... Is Log Shipping or ASE Replicator a
realistic option for a Warm Standby solution?
    </pre>
  </blockquote>
  <pre wrap=""><!---->
I wouldn't use ASE replicator for anything like this. However, log
shipping is certainly feasible, especially if a 2 hour downtime is
acceptable.
The setup is pretty straightforward - you have to write some scripts,
but they should be pretty straightforward - and with a 30GB db it is
feasible to do a full resync fairly often if your IO subsystem is
reasonably fast.

Michael
  </pre>
</blockquote>
<br>
</body>
</html>

--------------070006090806020607080405--
0
Eugene
7/15/2008 7:24:41 PM

Eugene Korolkov wrote:
> then why Sybase does not provide adequate scripts 
> (like Oracle and MS)

What would you define as an 'adequate' script?

Over the years I've set up log shipping for at least a dozen different companies.

Each time the requirements were different enough to require a different set of scripts:

- dump to file system vs dump to tape
- dump locally vs dump remotely
- dump to a single stripe vs dump to multiple stripes (fixed # vs variable #)
- dump stripes to same directory vs dump stripes to different directories
- dump using compression vs dump without compression
- old compression method vs new compression method
- error handling requirements
- pre- and post- operational requirements
- regularly scheduled jobs vs threshold-initiated vs a mix of the two
- kick off from crontab vs kick from scheduler software
- automatically load into remote dataserver vs let another script handle the loading
- archiving/deletion rules for 'old' dump files

While the concept in all cases is the same, the implemenation is always a little varied.

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

If you wish to use ASE's job scheduler you could take a look at the templates provided for dumping databases and logs.
0
Mark
7/15/2008 8:30:15 PM
What are the biggest deciding factors to decide between Log
Shipping vs. buying/using Replication Server?

Our RTO is 2 to 3 hours.

There are 12 databases (each 600 MB).

Total database space is 7.2 GB

> Susan M.
0
Susan
7/16/2008 3:17:58 AM
On Jul 16, 5:17=A0am, Susan Mills wrote:
> What are the biggest deciding factors to decide between Log
> Shipping vs. buying/using Replication Server?
>
> Our RTO is 2 to 3 hours.
>
> There are 12 databases (each 600 MB).
>
> Total database space is 7.2 GB
>
> > Susan M.


One of the main questions is the level of scripting competence
available. If you have people on staff (or contractors) that have a
good level of shell or perl or ... scripting skills, then building a
log shipping solution should be pretty straightforward - at a guess a
couple of weeks worth of work.

Otherwise you'd probably be better off with rep server, as you can
then turn to Sybase TS in case of problems and get things smoothed
out.

Michael
0
mpeppler
7/16/2008 7:12:26 AM
On Tue, 15 Jul 2008 12:24:41 -0700, Eugene Korolkov wrote:

> Michael,
> 
> If everything is  
> 
>>is pretty straightforward
> 
> 
> 
> then why Sybase does not provide adequate scripts 
> (like Oracle and MS) and why Rep.Server is the huge product ?
> Unfortunately "devil is always in details" I think.

Sure - but it also depends on what you are trying to achieve.

RepServer is a generic system that can solve a large number of problems,
in particular for multiple-site data availability in large organizations.
It could be considered overkill for a system where one "simply" wants to
be able to revert to a "recent" image of the data in case of a major
problem.

For the record I haven't implemented such a solution in a very long time
(the last time was around 1994 or so :-), but that doesn't mean that it
isn't a valid choice in some situations.

Michael
-- 
Michael Peppler           -                 Peppler Consulting SaRL
mpeppler@peppler.org      -                  http://www.peppler.org
Sybase DBA/Developer      -   TeamSybase: http://www.teamsybase.com
Sybase on Linux FAQ       -   http://www.peppler.org/FAQ/linux.html

0
Michael
7/16/2008 6:29:30 PM
A smattering of issues to consider ...

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

Depending on the complexity of your log shipping requirements ... a set of shell scripts can be 
written/tested/implemented in a couple days (assuming some basic shell scripting knowledge).

Shell scripting will cost you the time it take to write the script.

If you dump-n-load with standby access then the remote database can be used for read-only access, though you'll need to 
kick out users when you wish to load a database/tranaction-log dump file.

If you don't use dump-n-load with standby access then the remote database is not available to you for any sort of work 
until you issue an 'online database' command.  Once the database has been brought online you've typically broken the 
dump-n-load cycle and will not be able to load any more log dump files, ie, you'll have to resync the remote database 
beginning with a full database dump.

If you use log shipping you can do something like the following:

dump database, load database
dump log, load log
dump log, load log
dump database, don't bother loading database
dump log, load log
dump log, load log

You'll want to keep intermediate dumps for recovery purposes, but skipping the loading of intermediate db dumps will 
save you some time on the remote system.

One downside to log shipping is that database corruption in the primary database will brought over and loaded into the 
remote database; this is due to the replication/copying of data at the binary level.

Also, log shipping is an all-or-nothing operation.  It's not very easy to dump-n-load *part* of a database or table.

Log shipping: easy to understandy; easy to implement; easy to maintain; cheap to implement; limited functionality other 
than moving a binary copy of your data between dataserers

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

Replication server will cost you a good bit of resources (money, time, hardware) for product licensing, training, and 
implementing scripts/tools for monitoring.  If you plan to add/drop tables on a regular basis you're looking at the 
addtional cost to manage said activities.

Replication server has a moderate learning curve that should not be taken lightly.

Replication server has a *LOT* of capabilities that may come in handy on down the road, eg, partial data replication, 
distribution of data to different remote sites, rollup of data from different source databases, replication of data 
between different RDBMSs, the ability (via function strings) to manipulate replicated data on the fly, and on and on and on.

Corruption in the primary database will not be propagated to the remote database because replication server passed the 
data in transacational (ie, SQL text) form.

Replication server: relatively steep learning curve; more complicated to implement; more complicated to maintain; 
expensive to implement; robust functionality






Susan Mills wrote:
> What are the biggest deciding factors to decide between Log
> Shipping vs. buying/using Replication Server?
> 
> Our RTO is 2 to 3 hours.
> 
> There are 12 databases (each 600 MB).
> 
> Total database space is 7.2 GB
> 
>> Susan M.
0
Mark
7/16/2008 10:10:28 PM
Thank you all for your great feedback.  Breaking down the
Pros vs. Cons of Log Shipping and Replication Server was
extremely helpful.  Thank you for doing this.  These are all
very good points and all need to be thought through
thouroughly.  We will use your advice and will take a
cautious approach.

Thank you! :)

Susan M.



> A smattering of issues to consider ...
>
> ------------------
>
> Depending on the complexity of your log shipping
> requirements ... a set of shell scripts can be
> written/tested/implemented in a couple days (assuming some
> basic shell scripting knowledge).
>
> Shell scripting will cost you the time it take to write
> the script.
>
> If you dump-n-load with standby access then the remote
> database can be used for read-only access, though you'll
> need to  kick out users when you wish to load a
> database/tranaction-log dump file.
>
> If you don't use dump-n-load with standby access then the
> remote database is not available to you for any sort of
> work  until you issue an 'online database' command.  Once
> the database has been brought online you've typically
> broken the  dump-n-load cycle and will not be able to load
> any more log dump files, ie, you'll have to resync the
> remote database  beginning with a full database dump.
>
> If you use log shipping you can do something like the
> following:
>
> dump database, load database
> dump log, load log
> dump log, load log
> dump database, don't bother loading database
> dump log, load log
> dump log, load log
>
> You'll want to keep intermediate dumps for recovery
> purposes, but skipping the loading of intermediate db
> dumps will  save you some time on the remote system.
>
> One downside to log shipping is that database corruption
> in the primary database will brought over and loaded into
> the  remote database; this is due to the
> replication/copying of data at the binary level.
>
> Also, log shipping is an all-or-nothing operation.  It's
> not very easy to dump-n-load *part* of a database or
> table.
>
> Log shipping: easy to understandy; easy to implement; easy
> to maintain; cheap to implement; limited functionality
> other  than moving a binary copy of your data between
> dataserers
>
> ----------------------------
>
> Replication server will cost you a good bit of resources
> (money, time, hardware) for product licensing, training,
> and  implementing scripts/tools for monitoring.  If you
> plan to add/drop tables on a regular basis you're looking
> at the  addtional cost to manage said activities.
>
> Replication server has a moderate learning curve that
> should not be taken lightly.
>
> Replication server has a *LOT* of capabilities that may
> come in handy on down the road, eg, partial data
> replication,  distribution of data to different remote
> sites, rollup of data from different source databases,
> replication of data  between different RDBMSs, the ability
> (via function strings) to manipulate replicated data on
> the fly, and on and on and on.
>
> Corruption in the primary database will not be propagated
> to the remote database because replication server passed
> the  data in transacational (ie, SQL text) form.
>
> Replication server: relatively steep learning curve; more
> complicated to implement; more complicated to maintain;
> expensive to implement; robust functionality
>
>
>
>
>
>
> Susan Mills wrote:
> > What are the biggest deciding factors to decide between
> > Log Shipping vs. buying/using Replication Server?
> >
> > Our RTO is 2 to 3 hours.
> >
> > There are 12 databases (each 600 MB).
> >
> > Total database space is 7.2 GB
> >
> >> Susan M.
0
Susan
7/18/2008 4:32:03 AM
> What would you define as an 'adequate' script?

Personally ? an adequate script is One pair (source/target) of 
shell/SQL that does not break and can be used by/with/for ...

> - dump to file system vs dump to tape
> - dump locally vs dump remotely
> - dump to a single stripe vs dump to multiple stripes (fixed # vs variable #)
> - dump stripes to same directory vs dump stripes to different directories
> - dump using compression vs dump without compression
> - old compression method vs new compression method
> - error handling requirements
> - pre- and post- operational requirements
> - regularly scheduled jobs vs threshold-initiated vs a mix of the two
> - kick off from crontab vs kick from scheduler software
> - automatically load into remote dataserver vs let another script 
> handle the loading
> - archiving/deletion rules for 'old' dump files
> 
> While the concept in all cases is the same, the implemenation is always 
> a little varied.

.... and the variations are in set up, config, variables, pipes, tees, 
of the One pair.

-- 
Cheers
Derek
Senior Sybase DBA / Information Architect
Copyright � 2008 Software Gems Pty Ltd
Quality Standards = Zero Maintenance + Zero Surprises
Performance Standards = Predictability + Scaleability

0
Derek
7/27/2008 4:11:52 PM
> On 2008-07-14 21:40:05 +1000, Susan Mills said:

Most of the issue has been answered.  I will address the remaining one ...

> Replication Server License Costs:
> 
> 1 CPU = $10,000
> 2 CPU = $20,000
> 3 CPU = $30,000
> etc..
> 
> First we are shocked that the CPU costs jump up so
> aggresively.  Especailly since we have a 8 CPU box.

That's a misunderstanding or a poor sales explanation job.  The 
RepServer Agent is cold as a CPU licence; the no of CPU licences 
required is whatever is on the sourced box, ie. 8 CPU ASE = 8 CPU 
RepServer licence.  It does not jump, it is not aggresive, it is just 
$10k imes CPUs on your ASE box.  Problem was the salesman should have 
told you from the outset, not later.  Just imagine what it is for cust 
who have $50k times 16 CPUs.

Log Shipping is great, and has been around since 4.2.  Somepeople put 
it down as "luke warm standby", but that is only true since the advent 
of RepServer.  You do not have to write (test, debug, handle errors) 
the scripts your self, we sell it, Unix Bourne shell only, there are 
many other partners who do.
-- 
Cheers
Derek
Senior Sybase DBA / Information Architect
Copyright � 2008 Software Gems Pty Ltd
Quality Standards = Zero Maintenance + Zero Surprises
Performance Standards = Predictability + Scaleability

0
Derek
7/27/2008 4:20:59 PM
Reply:

Similar Artilces:

ASE vs Replication server
Hello, I am using windows 2000 professional. I have installed ASE 12.5 successfully. I have created two servers and started using them perfectly. The problem is that I tried to install the replication server 12.1 in the same directory that holds the ASE. I faced some questions like overriding some files during this installation and I always says yes to the overriding. After this installation, the servers that I have created in the ASE can not be started. This is because of the overriding. Also I have reinstalled the replication server and says "No" for the over...

ASA To ASE - VS
What are the differents in terms of configuring SQL Remote Between ASA to ASE and ASE To ASE ? You should start with the Help file and then ask specific questions: Data Replication with SQL Remote PART 5. Appendix APPENDIX A. Enterprise and Anywhere: Differences There are many differences, so begin there. -- David Fishburn Sybase Please only post to the newsgroup BH Ong <bhong@tm.net.my> wrote in message news:01bf4b98$33183580$7ccdc8c8@virtual-branch... > What are the differents in terms of configuring SQL Remote Between ASA to > ASE and ASE To ASE ...

Mobilink vs ASE Replication
Hello group, I am trying to choose a way to extend an already existing ASE Replication system and I am evaluating Mobilink. Let me describe you a bit the scenario.... There is an existing Replication system with ASE Replication (around 4 or 5 sites). We want to add to that existing system a database that will be placed on ship! So we are looking into mobilink and the features that it can give us in that kind of situation.... My question is how stable, quick and error free would be a solution with mobilink. My main concern has to do with database recovery in case of an err...

Replicate SQL Anywhere Text column to ASE using Replication Server
Hi everyone, Is it possible replicate text column in SQL anywhere 5.5.04 using Replication Agent for SQL Anywhere and Replication Server 11.5 to Adaptive Server Enterprise? TIA Virginia yes. Replication of BLOBs works fine /steve -- Stephen Rice Manager Custom Support Sybase Canada Inc. email: srice@sybase.com virginia cheung wrote in message <01bdf3e7$6ed5c420$010414ac@star>... >Hi everyone, > >Is it possible replicate text column in SQL anywhere 5.5.04 using >Replication Agent for SQL Anywhere and Replication Server 11.5 to Adaptive >Server ...

Replication between ASE and ASE URGENT
HI everybody Can you help me please with the following question. We need to syncronize ASE to ASE ( bidirectional) Initially, it was planned to implement with SQL remote, but it isn't available. With replication server, it isn't a solution beacuse, the customer doesn=B4t have a comunntication channel all time. We think use Mobiliink Server to replictase ASE to ASE, but using an ASA in the middle, so that, first it replicate ASE to ASA, and later, ASA to ASE, is it this feasible ??? Thanks four your answer "Marco" <mbarrion@uniplex.com.ec> wr...

Dump/Load (from ASE 12.5.4 to ASE 15.x) - VS.
Hi All, We are in the process of planning the upgrade of our ASE 12.5.4 dataservers to ASE 15.x. What is the most recommended way to upgrade ASE dataservers from ASE 12.5.4 to ASE 15.x? Potential options: 1) Install new instances of ASE 15.x and load database dumps from our ASE 12.5.4 dataservers to the newly installed ASE 15.x dataservers. - OR - 2) Use the ASE upgrade utility (sqlupgrade) to upgrade our existing ASE 12.5.4 dataservers to ASE 15.x. What are the Pros vs. Cons for loading a 12.5.4 database into a 15.x ASE dataserver versus performing an ASE dataserv...

Replication doesn't work from ASE to SA using Replication Server
I have been setup replication between ASE 11.5 and SQL Anywhere using Repliation Server. The primary database is in ASE 11.5 and the replicate database is SQL Anywhere 5.5.04. I have been setup Open gateway for SQL Anyway, create the connection, create replciation definition and subscription. No error show on the Replication Server Manager. But If I inserted/updated/deleted data in the ASE database, no changes will be replicated to the SQL Anywhere database. No queue has been written in the outbound queue for this connection. No error also. Would anyone help me? TIA. On M...

Can Replication Server 11.5.1 replicate to ASE 12.0?
Can Replication Server 11.5.1 replicate to ASE 12.0?( as a client) Thanks Shishir. Yes Rob V. "Shishir Mehta" <smehta@worldstreet.com> wrote in message news:39A3DDB7.F957477A@worldstreet.com... > Can Replication Server 11.5.1 replicate to ASE 12.0?( as a client) > Thanks > Shishir. > > ...

ASE 11.9.2 -> ASE 12.5 Migration over Replication Server?
Hi, I've heared about the possibility to migrate an ASE (11.9.2->12.5, both 32bit) over the Replication server. Is it also possible with this solution to increase the page size (old ASE 11.9.2 with 2k -> new ASE 12.5 with 4k)? If yes, could anybody explain me please how that works? We've been using Rep. Server only for warm standby. Thank you in advance. Best regards, Marco Stroech ______________________________________________________ Marco Stroech Databases AOL Deutschland � Millerntorplatz 1 � 20359 Hamburg � Germany +49 (40) 36159-7454 � fax: +49 (40...

Replication ASE
Hi, How can i replicate data between 2 ASE servers using SQL Remote, because when i use ssxtract it extracts a anywhere database .db. other question is i wanto replicate data via email, is microsoft exchage server enough for this or i'll need other mail server. thanks in advance Joan jmcd wrote in message <37616E0E.91D29322@else.com.pe>... >Hi, > >How can i replicate data between 2 ASE servers using SQL Remote, because >when i use ssxtract it extracts a anywhere database .db. > Hi I try this type of replication. In documentation i d...

2-way replication from ASE to ASE
We are looking at implementing replication server bi-directional. Specifically, we have two databases (for redundancy) on two differnet physical servers, two different ASE databases, but the two databases are named the same, and same architecture. Sybase Learning suggested the only way to do this is to use stored procedures (request function). This is not really bi-directional and does not have the data available in the secondary immediately. Using stored procedures will cause a complete re-write of the application, so it is not really worth it. What we wanted it to do is that i...

ASE Replicator / ASE 12.5
Welcome, Adaptive Server Enterprise/12.5.0.3/EBF 10696 IR/P/Linux Intel/Linux 2.4.7-10smpi686/rel12503/1915/32-bit/OPT/ I had started ASE Replicator with primary connection xxx (with subs,articles,etc.), then I changed primary connection into yyy (and the rest). Everything was fine. But when I try to back to xxx primary connection Sybase returns me this error: 1> sp_addprimaryconn "xxx" 2> go Msg 32000, Level 20, State 0: Server 'ASE_Rep', Procedure 'sp_addprimaryconn', Line 1: Command <sp_addprimaryconn> failed - Could not add Primary...

PB with ASE vs DB2 vs Oracle
We're currently in the middle of deciding which of the above DB platforms to migrate to (ASA at 12GB just doesn't cut it). Are there any stability or other issues relating to connecting PB8 to any of the above that I should be aware of. Although any information on any issues is appreciated, I'm particularly interested in stability of PB. I've been running PB8 Ent Eval against each of the engines and had problems with stability when connecting to DB2, but want to make sure this is not a general problem with connecting to DB2 as I've not been able to patch PB8 yet...

Replication ASA-ASE stops because ASE is full
I have a replication between a consolidated DB on ASE and 4 remote DB on ASA. During a replication, ssremote was unable to apply messages from the remotes because the segments of the consolidated DB where full. The message of ssremote was : E. 03/31 06:00:06. bourget: Error 1105: Can't allocate space for object 'depot' in database 'stp_qual' because 'default' segment is full/has no free extents. If you ran out of space in syslogs, dump the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to increase size of the segment. I have increas...

Web resources about - Log Shipping vs. ASE Replicator vs. Replication Server - sybase.ase.administration

DNA replication - Wikipedia, the free encyclopedia
DNA replication is a biological process that occurs in all living organisms and copies their DNA ; it is the basis for biological inheritance ...

Facebook Slashes Data Replication With HDFS RAID
Avoiding replication is a key component of efficient data storage , and one method Facebook uses to accomplish this task is HDFS RAID , which ...

PolSci Replication (@PolSciReplicate) on Twitter
Sign in Sign up To bring you Twitter, we and our partners use cookies on our and other websites. Cookies help personalize Twitter content, tailor ...

Encryption in demand for backup and replication: Veeam
When it comes to backup and replication, Veeam has found encryption is one of the most requested feature by businesses.

John Sands Australia cuts data replication time from 14 hours to three
Corporate data replication was taking up to 14 hours to complete at greeting card company John Sands Australia until data acceleration software ...

EMC gives VMware admins the reins to replication and recovery
EMC is putting replication and recovery into the hands of VMware administrators with a software version of its RecoverPoint appliance that's ...

Facebook Slashes Data Replication With HDFS RAID - SocialTimes
Avoiding replication is a key component of efficient data storage , and one method Facebook uses to accomplish this task is HDFS RAID , which ...


Violin to bring deduplication, replication, other tools to all-flash storage arrays
Violin Memory plans to add deduplication, thin provisioning, snapshots and other features in a software update for its all-flash storage arrays, ...

Art & Craft: The Story of an Art Forger Whose Artwork Replication Isn't Actually Illegal
Let me just start off by saying that I don't condone illegal forgery or theft—but I do think that someone who can put the art world in a tizzy ...

Resources last updated: 12/3/2015 6:12:32 PM