Transation Replication won't hold permissions
- From: bob.morrow@xxxxxxxxxxxxxxxxxxxxxxx
- Date: 14 Nov 2006 08:41:37 -0800
We replicate a portion of our data to another server to support our
website. This has been ongoing for several years and the data is
maintained on a two year cycle. Every two years the entire process is
torn down and rebuilt usually without a great many problems.
This year when the subscriber database is created using the "Yes,
initialize the schema and data" selection on the Initialize
Subscription screen, the tables that are created do not hold the
permissions that are assigned. However if I do not use this process
initially the stored proceedures are not created in the subscription
database to insert, update, delete, etc. I have been creating the
database then deleting all the tables and replication publication; then
scripting them with the permissions and restarting the publication with
the "No, Subscriber already has schema and data" option. This is
tedious and prone to error.
Anyone know why the first process will not hold permissions after
working well for so many years. Our only change is the live data is now
on a clustered server.
Bob
.
- Prev by Date: 2005 Replication
- Next by Date: Re: transaction replication timeout
- Previous by thread: 2005 Replication
- Next by thread: Re: transaction replication timeout
- Index(es):
Relevant Pages
|