Tracing the Replication Server Transactions to Target Databases

Trace transactions that Replication Server sends to all replicate databases.

Because the trace is not specific to a connection and can get quite large, Sybase recommends that you do not keep the trace function turned on.

Use isql to log in to Replication Server.
Turn the trace on. Output from the trace function is written to the Replication Server log.
```
trace "on",dsi,dsi_buf_dump
go
```

Use isql to insert one row in the active database:

insert into t1 values (1,'first row',getdate())
go
(1 row affected)

Update the row in the active database:

update t1 set c = getdate()
go
(1 row affected)

View the trace output in the Replication Server log file, $SYBASE/REP-15_5/install/repservername.log:

T. 2009/10/28 22:09:08. (138): Command(s) to
'wingak1505i.pubs2':
T. 2009/10/28 22:09:08.
(138):'begin transaction
[0a] update dbo.t1 set
c='20091028 22:09:07:703'
where a=1 and b='first row'
and c='20091028
22:05:53:843' '

Note: To turn off the tracing function in Replication Server, use:

trace "off",dsi,dsi_buf_dump
go