When using MS SQL mirroring, changed rows on the principal are pushed to the mirror.
What I imagine/guess is that the data itself is pushed over, but not indexes. (I imagine this because I think of indexes as a secondary entity that exists to improve performance, not the data per se.)
And so for example after reorganizing or rebuilding the indexes on the principal, I imagine this would not be pushed to the mirror. Good news is, it doesn't cause a surge in mirror traffic. Bad news is, the indexes must also be reorgged or rebuilt on the mirror (if desired).
Is this correct -- are indexes part of what is pushed to the mirror, or not?
EVERYTHING is mirrored. The mirror is a physical copy of the principal. All operations are reflected on the mirror: a reorganize will reorganize the mirror identically, a rebuild will result in a rebuild on the mirror, a rollback will rollback on mirror.
Just to complement the Remus excellent answer, the way mirroring works is by copying the transaction log records from the principal and replaying on the mirror. So anything that is logged into the transaction log on the principal is replayed on the mirror.