you stream all the DML operations as required from the publisher to the subscriber.
Transactional replication has a hierarchy,
with transactions being replicated from the publisher to the subscriber.
Because transactional replication assumes a hierarchical structure,
with read-only sub-scribers it works well as a scale-out solution
where you want to distribute data to multiple SQL Server 2005 instances for reporting purposes,
as shown in Figure 32-8.
Database users can connect to any one of the subscribers to generate reports,
although there will be some latency between data being modified on the publisher
and it being replicated to the subscribers,
which depends on your hardware and network infrastructure.
Because the HR, Marketing and Sales department
are all located at the Head Office in Sydney on the same LAN continous replication has been configured.
Consequently those departments should only experience a minor latency of a few seconds.
For the branch office located in Darwin, which is connected via a WAN link,
it is sufficient to replicate every hour as a degree of latency is acceptable.
Source: Microsoft SQL 2005 Administrator's Companion,
Page 1102-1104