SQL DB index replication

Hi All,

We have a database on SQL server 2008 R2 which gets replicated to another database on different server. The replication is one way from Server A to server B. On Server A we delete an index, after 5 minutes it comes back.

What could it be that is cause this?

Thanks,
LVL 1
skyjumperdudeAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

DcpKingCommented:
Sounds strange, but ... read here:

"Index changes are not propagated to Subscribers: if you drop a column at the Publisher and a dependent index is dropped, the index drop is not replicated. You should drop the index at the Subscriber before dropping the column at the Publisher, so that the column drop succeeds when it is replicated from the Publisher to the Subscriber. If synchronization fails because of an index at the Subscriber, manually drop the index and then rerun the Merge Agent."

You may have dropped an index (among other things) successfully at the publisher but it can't drop at the subscriber. Quite why it cames back on the publisher I don't know: are there any log events?

hth

Mike
0
Vitor MontalvãoMSSQL Senior EngineerCommented:
Check if someone or something (a job maybe) as recreated the index.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Eugene ZCommented:
what type of replication do you have?
..you may need to drop index on all "partners" DBs
0
Ryan McCauleyData and Analytics ManagerCommented:
Does this happen to a specific index, or to any index you drop on the source database? Can you use SQL Profiler to watch the instance and see when the index is recreated? You can filter the monitoring for just statements containing INDEX, so you'll get a timestamp when it happens - from there (and the details like workstation and login), you'll get some details about where it came from.

I'd suspect it's not related to replication at all, but that's a distraction - there's no reason I can think of why replication would alter the publishing database, and I'd look instead for a scheduled job of some kind that's recreating it.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server 2008

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.