If its going only from the main server to the pc's use transactional
replication. If its going both ways use merge replication.
You can replicate to msde from SQL server 2005 using transactional, and you
can replicate back and forth using merge replication.
SQL 2005 does not support replicating to Access. SQL 2005 does support
replicating to SQL 2005 Express.
--
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 [quoted text, click to view] "bob britton" <rbritton@willcare.com> wrote in message
news:ukzf%23dK6GHA.400@TK2MSFTNGP06.phx.gbl...
> With MSSQL2005, what technologies does MS provide to support an
> application environment based upon a central server model replicating
> updateable data to clients (XP)?
>
> Imagine if you will having MSSQL2005 on the back end. Imagine, if you
> will, having 300 PCs running a .Net app needing DB storage that has
> content synched / replicated to the central DB server.
>
> what are the de jure approaches for this model?
>
> with Sybase iAnywhere, it seems to lend itself towards this model very
> well. Can someone explain to me Microsoft's recommentation for such an
> architecture?
>
> Does MSDE support replication to MSSQL2005? how about MS Access? how about
> SQL Express 2005?
>
> In other words, what client DB technology do i look at putting in place to
> be local storage that is replicatable to a Central DB running MSSQL2005?
>
> warmest regards
>
> bob.
>