"Hilary Cotter" wrote:

> If its uni-directional data flow I would use transactional replication from
> the publisher to the dev machines and pull it use Windows Synchronization
> Manager. If you need bi-directional data flow use merge replication.
>
> While the technology is complex, it is very solid.
>
> --
> Hilary Cotter
> Director of Text Mining and Database Strategy
> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
>
> This posting is my own and doesn't necessarily represent RelevantNoise's
> positions, strategies or opinions.
>
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
>
>
> "IronYuppie" <IronYuppie@discussions.microsoft.com> wrote in message
> news:B54EB332-4FD6-4D4A-9775-885F529CE25F@microsoft.com...
> >I have a bunch of portable machines on which I do development, and I was
> > wondering if anyone has any great mechanisms for doing synch between all
> > the
> > machines. Any preferences? I looked at pub and subscribe, but it seems
> > needlessly complex for this as well as the fact that any of the databases
> > may
> > be online or offline at any time, and the changes can occur anywhere.
> >
> > Any thoughts?
>
>