Database A is set to FULL Recovery Model (ought to be anyway, if it is having continuous data entry during the working day).
Log Backups are taken at intervals (e.g. 10 minutes as you describe)
The log backup is "shipped" (copied) to Server B and restored onto the database there.
The database on Server B is "read only" (you would need full replication if you wanted the database on Server B to be read-write)
This is not quite how you describe it ("Backup just the Raw SQL Data"), so possibly the answer to a different question?!!
To copy "just data" you would have to use SQL Commands.
INSERT INTO ServerB.RemoteDatabaseName.dbo.TableName
SELECT *
FROM ServerA.LocalDatabaseName.dbo.TableName
(The actual code needs to be smarter than this - Insert new records, Update modified ones, Delete stale ones)
for this to work well, particularly on large tables, it needs some "clue" as to what has changed - e.g. a Modify Date. But for large tables, and large volumes of data, it is likely to be very intrusive to database users. We only use this type of approach (on large volumes of data) as an overnight process.
Can they not just run reports on the Live database and save all this aggravation?