reinitialized subscription - more info

Running - Win 2K / SQL 2K
I am constantly, once a week or so,getting an error on a
transactional publication that I have...
The subscription(s) have been marked inactive and must be
reinitialized. NoSync subscriptions will need to be
dropped and recreated.
This publication is set up to be continious and is
checked daily to verify it is running. I will come in
one morning and there will be an error. There are 15
remote locations using a transactional/continous
publication to move data to the main office.
How can I prevent this from happening?
What is causing this?
Is there some logging option I can turn on to see more
info about the transactions?
Larry....
By default is a publisher and subscriber have not "talked to" each other for
14 days the subscriber is marked inactive and the subscription may be
dropped. You must reinitialize, regenerate and redistribute the snapshot to
clear this condition.
You can set the interval by right clicking on your publication, selecting
properties and in the subscription expiration section, set a long expiration
value.
I normally run scripts that detect whether the distribution agent has
replicated a transaction to the subscriber in the last 24 hours, and if not,
it raises an alert which causes operations to be paged.
This raises the visibility of these errors.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"larry..." <anonymous@.discussions.microsoft.com> wrote in message
news:9b3601c43446$63f03c20$a401280a@.phx.gbl...
> Running - Win 2K / SQL 2K
> I am constantly, once a week or so,getting an error on a
> transactional publication that I have...
> The subscription(s) have been marked inactive and must be
> reinitialized. NoSync subscriptions will need to be
> dropped and recreated.
> This publication is set up to be continious and is
> checked daily to verify it is running. I will come in
> one morning and there will be an error. There are 15
> remote locations using a transactional/continous
> publication to move data to the main office.
> How can I prevent this from happening?
> What is causing this?
> Is there some logging option I can turn on to see more
> info about the transactions?
> Larry....
>

reinitialized subscription

Running - Win 2K / SQL 2K
I am constantly getting an error on a merge
publication/subscription that I have...
The subscription(s) have been marked inactive and must be
reinitialized. NoSync subscriptions will need to be
dropped and recreated.
How can I prevent this from happening?
What is causing this?
Larry...
you normally get this error when your subscribers haven't connected to your
publisher within 14 days for transactional and merge publications.
The way to prevent this is to ensure your subscriber connects to your
publisher within this period.
Exactly how frequently are you getting this error?
"larry" <anonymous@.discussions.microsoft.com> wrote in message
news:89a401c432b4$81e001e0$a401280a@.phx.gbl...
> Running - Win 2K / SQL 2K
> I am constantly getting an error on a merge
> publication/subscription that I have...
> The subscription(s) have been marked inactive and must be
> reinitialized. NoSync subscriptions will need to be
> dropped and recreated.
> How can I prevent this from happening?
> What is causing this?
> Larry...
|||.....Exactly how frequently are you getting this error?
Hilary,
I get this on one of my continous transactional
subscriptions once every couple of weeks. I check
replication every day and in fact, the SQL server agent
gets restarted every night @. 2:00 am.
Larry...

Reindexation

I have a very large database, in wich the indexes are constantly "getting lost". I execute DBCC Reindex and everything goes back to normal. Still, I don't know why this happens. I have to run this process once or twice a week, sometimes as a scheduled task, some others manually.
Why are the indexes 'getting lost'?
What could be wrong with the database?
Thanks in advance

Can you elaborate on what you mean by "indexes are getting lost"...are you saying the index no longer exists? That cannot be the case because dbcc reindex implies you have an index that is being reindexed.

Thx

Ajay

|||

I'm deeply sorry for not being able to put this in other way. It's just that i do not understand what is happening, even less how to ask it or explain it... someone told me that "the indexes get corrupted". Still, I don't know what this means, or why...

Thans again

Eduardo

|||

You might find some help with the DBCC commands. They will help you with physical and logical errors. Here is a good link for an introduction to those:

http://www.informit.com/guides/content.asp?g=sqlserver&seqNum=30&rl=1

And here is a more in-depth explanation of the DBCC CHECKDB command:

http://msdn2.microsoft.com/en-us/library/aa258278(SQL.80).aspx