Live Partial Table / column replication
You could also solve this with a trigger that populates the copy of the table on insert/update/delete. It wasn't clear in the question that these tables are actually on different servers, and that the subscriber was unreliable. In that case you could simply log ship to the subscriber - you can get pretty close to real time here, though you will have to kick users out temporarily as you restore new logs. If log shipping the entire database is a concern, then you could instead use a trigger to populate another database on the same instance - which only has this table and the required columns populated - and then log ship that database to the other instance:



I have a blog post on making log shipping work much more like a set of readable secondaries:L


Readable Secondaries on a Budget


You can also look at these posts for an approach I've used to do something a lot like replication but with more control, less impact, and none of the troubleshooting nightmares:


Schema Switch-A-Roo
Schema Switch-A-Roo : Part 2


I also talk about some ways to provide read-only copies of the data for reporting at the end of this post:


Bad habits : Putting NOLOCK everywhere