Post Setup Maintenance

Hi all,
I have designed and implimented my 2K pubs and msde subscribers, anonymous
pull.
There isn't much docs on maintenance steps and less on the "Validate all
users." Does that just show validation stats in the history or will it set
the user to reinitialize if something is off or something else.
My goal would be minimal work to catch invalid data each week or day and
make it right? Suggestions ?
Mike
It will show up in the distribution agent history. You can configure it to
send a new snapshot if it fails validation or just to stop.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Tigermikefl" <Tigermikefl@.discussions.microsoft.com> wrote in message
news:69656639-A716-4E15-8857-289050ED6F61@.microsoft.com...
> Hi all,
> I have designed and implimented my 2K pubs and msde subscribers, anonymous
> pull.
> There isn't much docs on maintenance steps and less on the "Validate all
> users." Does that just show validation stats in the history or will it set
> the user to reinitialize if something is off or something else.
> My goal would be minimal work to catch invalid data each week or day and
> make it right? Suggestions ?
>
> --
> Mike
>
|||So it's the same as changing each agent to the validation agent profile.
It seems like the best option is to validate all regularly, say weekly and
have it apply a send the snapshot automatically, to keep it clean. A job to
run on weekends for the main pub.
Does that make good sense?
The other pubs have filter joins which it apparently won't validate
correcly. A subscriber side job to check table counts based on the joins
might work. Any simpler suggestions for filter join health checking?
Thanks !
Mike
If data falls in the woods and nobody is there to see it ...... ?
"Hilary Cotter" wrote:

> It will show up in the distribution agent history. You can configure it to
> send a new snapshot if it fails validation or just to stop.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Tigermikefl" <Tigermikefl@.discussions.microsoft.com> wrote in message
> news:69656639-A716-4E15-8857-289050ED6F61@.microsoft.com...
>
>
|||I seldom run validations as I have confidence replication works well.
AFAIK - validations work with join filters.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Tigermikefl" <Tigermikefl@.discussions.microsoft.com> wrote in message
news:8DEB0974-6669-4985-A479-7EB5B935E68E@.microsoft.com...[vbcol=seagreen]
> So it's the same as changing each agent to the validation agent profile.
> It seems like the best option is to validate all regularly, say weekly and
> have it apply a send the snapshot automatically, to keep it clean. A job
> to
> run on weekends for the main pub.
> Does that make good sense?
> The other pubs have filter joins which it apparently won't validate
> correcly. A subscriber side job to check table counts based on the joins
> might work. Any simpler suggestions for filter join health checking?
> Thanks !
>
> --
> Mike
> If data falls in the woods and nobody is there to see it ...... ?
>
> "Hilary Cotter" wrote: