Replication problem.. Please help..

Hi,
I have set up replication successfully. Data from Publisher can be
replicated to Subscriber. I can check the data directly from Enterprise
Manager.
Before replication, the application calling the database work perfectly.
HOWEVER, after replication the application cannot operate with the
replicated tables while un-changed table still works fine.
Can anyone tell me what replication has done to the table and how to avoid
it?
Thanks so much!!
Andrew,
what type of replication are you using? It sound's like it's the presence of
new (GUID) columns and/or triggers that has caused issues. If it is the GUID
columns (merge and updating subscribers) then the app should use named
column lists and in this case it'll be invisible to the App. If you have
triggers that modify the base table then this can be an issue - I'll wait
for more info before going down that route.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Hi Paul,
Thanks for your answer..
After checking, I found the following:
1. access right of the replicated tables are all missing;
2. all default values are missing; and
3. identity column is no longer identity column. it is just a normal column.
Do you know how to fix it?
Many Thanks.. :>
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:%23YlHLGPSGHA.524@.TK2MSFTNGP10.phx.gbl...
> Andrew,
> what type of replication are you using? It sound's like it's the presence
> of new (GUID) columns and/or triggers that has caused issues. If it is the
> GUID columns (merge and updating subscribers) then the app should use
> named column lists and in this case it'll be invisible to the App. If you
> have triggers that modify the base table then this can be an issue - I'll
> wait for more info before going down that route.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||Andrew,
I assumed you were talking about the publisher. If it's the subscriber, you
need to open the article properties dialog screen (elipsis button) and on
the snapshot tab click the first 3 checkboxes. To get the permissions,
you'll need to add a post-snapshot script. For the identity column to remain
identity, I'd ask why? You must have set up a non-offline subscriber in
which case the identity attribute will never get used.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Hi Paul,
Thanks for your help.
Just found that some tables have more than 255 column and cannot pass the
vertical replication when setting the publisher. If skip those too-large
table, it works well after running the script for granting permissions.
Seems the problems is about to be solved..
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:uvPd6QaSGHA.5468@.TK2MSFTNGP14.phx.gbl...
> Andrew,
> I assumed you were talking about the publisher. If it's the subscriber,
> you need to open the article properties dialog screen (elipsis button) and
> on the snapshot tab click the first 3 checkboxes. To get the permissions,
> you'll need to add a post-snapshot script. For the identity column to
> remain identity, I'd ask why? You must have set up a non-offline
> subscriber in which case the identity attribute will never get used.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>