distributed database

Hi ...i have to implement distributed databse..

what are the tools and components that i need to do the distribution and retrival?

i use SQL server 2005....

please help me....as soon as posible..

so argent

thanks

What do you mean by a distributed database?sql

distrib. agent remains stopped

We have a situation where if the subscriber becomes unavailable for an
extended period (say over 15 minutes), the distribution agent at the
publisher will make several attempts to re-connect to the subscriber. Once
the subscriber returns to service, the distrib. agent remains in 'failed'
status and does not reconnect to the subscriber. This causes a push and
other pending operations to fail. As a workaround, the distrib. agent. has
to be manually restarted so normal operation can continue. Is this the
default behavior or possibly a known issue.
================================================== ===
Win2003/SQLSvr2000 ver 8.00 760 (SP3)/Transactional Replic. w/updatable
subscribers/
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
"batuka" <abraxas1969@.hotmail.com> wrote in message
news:ulzKd7ZdFHA.1684@.TK2MSFTNGP09.phx.gbl...
> We have a situation where if the subscriber becomes unavailable for an
> extended period (say over 15 minutes), the distribution agent at the
> publisher will make several attempts to re-connect to the subscriber. Once
> the subscriber returns to service, the distrib. agent remains in 'failed'
> status and does not reconnect to the subscriber. This causes a push and
> other pending operations to fail. As a workaround, the distrib. agent. has
> to be manually restarted so normal operation can continue. Is this the
> default behavior or possibly a known issue.
>
> ================================================== ===
> Win2003/SQLSvr2000 ver 8.00 760 (SP3)/Transactional Replic. w/updatable
> subscribers/
>
|||schedule your distribution agent to start every 5 or 15 minutes. Then make
sure it runs continuously. This way when it stops it will restart 5-15
minutes later. You can also have the job return to stop 1 on failure of step
3.
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
"batuka" <abraxas1969@.hotmail.com> wrote in message
news:ulzKd7ZdFHA.1684@.TK2MSFTNGP09.phx.gbl...
> We have a situation where if the subscriber becomes unavailable for an
> extended period (say over 15 minutes), the distribution agent at the
> publisher will make several attempts to re-connect to the subscriber. Once
> the subscriber returns to service, the distrib. agent remains in 'failed'
> status and does not reconnect to the subscriber. This causes a push and
> other pending operations to fail. As a workaround, the distrib. agent. has
> to be manually restarted so normal operation can continue. Is this the
> default behavior or possibly a known issue.
>
> ================================================== ===
> Win2003/SQLSvr2000 ver 8.00 760 (SP3)/Transactional Replic. w/updatable
> subscribers/
>
|||Both of the suggested options worked very well. However, none of the db
updates that were done at the publisher (while the distribution agent
remained in 'stopped' status) are reflected ('or pushed') at the subscriber
db when it returned to service. Any ideas are apprecciated.
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:OxUzufadFHA.3052@.TK2MSFTNGP10.phx.gbl...
> schedule your distribution agent to start every 5 or 15 minutes. Then make
> sure it runs continuously. This way when it stops it will restart 5-15
> minutes later. You can also have the job return to stop 1 on failure of
step[vbcol=seagreen]
> 3.
> --
> 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
> "batuka" <abraxas1969@.hotmail.com> wrote in message
> news:ulzKd7ZdFHA.1684@.TK2MSFTNGP09.phx.gbl...
Once[vbcol=seagreen]
'failed'[vbcol=seagreen]
has
>

Distibution servers ...

So what happens when the Distribution Server blows a gasket? Somehow I get
the feeling that restoring from last nights backup isn't going to get things
back to normal? I ask because we are going to build a replication solution
that will fall under Sarbanes Oxely issues, one of which is documented
business continuity plans. Our solution will likely have a dedicated
distribution server and even though we haven't even budgeted hardware yet, I
am having visions of a major meltdown and a trip to the mental ward.
P.S. to Hilary Cotter. I think your replication book is great. I would
suggest that a follow up title would be a book (or additional chapters in a
new edition) that deal with such questions as replication headaches during
recovery and restoration. At least from personal experience, our worst days
as IT people are when we are under the gun to restore failed services.
Bob Castleman
DBA Poseur
Nope. Basically you need to cluster your distributor and hope for the best.
There is a kb article which describes how to recover from this.
http://support.microsoft.com/default...b;en-us;886839
I am working on an article of my own explaining how to do this.
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
"Bob Castleman" <nomail@.here> wrote in message
news:uzw0o4EcFHA.3204@.TK2MSFTNGP12.phx.gbl...
> So what happens when the Distribution Server blows a gasket? Somehow I get
> the feeling that restoring from last nights backup isn't going to get
things
> back to normal? I ask because we are going to build a replication solution
> that will fall under Sarbanes Oxely issues, one of which is documented
> business continuity plans. Our solution will likely have a dedicated
> distribution server and even though we haven't even budgeted hardware yet,
I
> am having visions of a major meltdown and a trip to the mental ward.
> P.S. to Hilary Cotter. I think your replication book is great. I would
> suggest that a follow up title would be a book (or additional chapters in
a
> new edition) that deal with such questions as replication headaches during
> recovery and restoration. At least from personal experience, our worst
days
> as IT people are when we are under the gun to restore failed services.
>
> Bob Castleman
> DBA Poseur
>
|||Thanks for the reference.
In your book there is mention of a second volume for merge replication. Is
this still in the works? Is there a publication date?
Thanks,
Bob
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:uy11nLFcFHA.720@.TK2MSFTNGP15.phx.gbl...
> Nope. Basically you need to cluster your distributor and hope for the
> best.
> There is a kb article which describes how to recover from this.
> http://support.microsoft.com/default...b;en-us;886839
> I am working on an article of my own explaining how to do this.
> --
> 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
> "Bob Castleman" <nomail@.here> wrote in message
> news:uzw0o4EcFHA.3204@.TK2MSFTNGP12.phx.gbl...
> things
> I
> a
> days
>

Dist Agent Setting

Running Win 2003 & SQL 2005
I had a problem with one of my dist agents & got backed up to the tune
of 1.55 million commands in the distribution database waiting to be
applied.
The agent has been running for 9+ hours and the number of pending
commands has not changed.
Is there a setting I can chang/make in the dist agent to get them to
process faster or atleast see the number of pending go down, so I will
know it is working.
AHIA,
Larry...
Larry - you could try reducing the -CommitBatchSize
nd -CommitBatchThreshold parameters and see if this helps.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com