New to Replication

Anand,
here are some sites which have step-by-step examples:
http://www.mssqlcity.com/Articles/Replic/Replic.htm
http://www.sqlservercentral.com/arti...ticleList.asp?
categoryid=26
BOL is currently the best resource 'bookwise' but keep an
eye out for Hilary's forthcoming book.
As for tables without PK - yes they can be replicated
using snapshot or merge, but not using transactional.
HTH,
Paul Ibison
actually in most cases I have seen you can extend tables without pk's to add
PK's to them. There are two approaches
1) in every instance I have run across there will be the functional
equivalent of a PK, in other words a candidate key. This is because the app
that uses these tables must be able to uniquely identify a record in order
to know what record to update or delete. So, by carefully studying these
tables and the data in them, as well as how the app intereacts with the
tables and data you can determine the candidate keys and convert them into
PK's, which you can replicate.
2) see this link for the other approach
http://groups.google.com/groups?selm...&output=gplain
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:29c801c470a1$57be6e80$a401280a@.phx.gbl...
> Anand,
> here are some sites which have step-by-step examples:
> http://www.mssqlcity.com/Articles/Replic/Replic.htm
> http://www.sqlservercentral.com/arti...ticleList.asp?
> categoryid=26
> BOL is currently the best resource 'bookwise' but keep an
> eye out for Hilary's forthcoming book.
> As for tables without PK - yes they can be replicated
> using snapshot or merge, but not using transactional.
> HTH,
> Paul Ibison