Hi
Is there any step by step guide available for replication in sql 2000
server database?
thanx
Gopi
See if this helps: http://www.mssqlserver.com/replication/primer_p1.asp
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Gopi" <gopigopi@.hotmail.com> wrote in message
news:%2340cUPtsFHA.3180@.TK2MSFTNGP10.phx.gbl...
Hi
Is there any step by step guide available for replication in sql 2000
server database?
thanx
Gopi
|||Hi
http://www.mssqlcity.com/Articles/Replic/Replic.htm --Setting All
Replica (Step by step)
"Gopi" <gopigopi@.hotmail.com> wrote in message
news:%2340cUPtsFHA.3180@.TK2MSFTNGP10.phx.gbl...
> Hi
> Is there any step by step guide available for replication in sql 2000
> server database?
> thanx
> Gopi
>
|||Thanx
but i try the same, it wont work properly i dont know why.
regards
Gopi
"Narayana Vyas Kondreddi" <answer_me@.hotmail.com> wrote in message
news:eUCBg6tsFHA.1448@.TK2MSFTNGP10.phx.gbl...
> See if this helps: http://www.mssqlserver.com/replication/primer_p1.asp
> --
> HTH,
> Vyas, MVP (SQL Server)
> SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
>
> "Gopi" <gopigopi@.hotmail.com> wrote in message
> news:%2340cUPtsFHA.3180@.TK2MSFTNGP10.phx.gbl...
> Hi
> Is there any step by step guide available for replication in sql 2000
> server database?
> thanx
> Gopi
>
>
|||Thanx
i try the same thing but it doesnt work, is there anything i have to do
more? like more configuration other then wizard?
Regards
Gopi
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:eX5I5$tsFHA.3732@.TK2MSFTNGP11.phx.gbl...
> Hi
> http://www.mssqlcity.com/Articles/Replic/Replic.htm --Setting All
> Replica (Step by step)
>
>
>
> "Gopi" <gopigopi@.hotmail.com> wrote in message
> news:%2340cUPtsFHA.3180@.TK2MSFTNGP10.phx.gbl...
>
Wednesday, March 7, 2012
Replication
Saturday, February 25, 2012
Replication
Hello,
Whats's the utility / advantages of the "Transactional publication with
updatable subscriptions"
thanks for your help!!!
nico
"pralnico" <pralnico@.discussions.microsoft.com> wrote in message
news:1C221973-1029-4380-8C24-A8C55817567F@.microsoft.com...
> Hello,
> Whats's the utility / advantages of the "Transactional publication with
> updatable subscriptions"
> thanks for your help!!!
>
Transactional replication starts with a snapshot. Thereafter only the
changes are replicated (which will typically mean less network traffic /
more frequent updates / less latency between different copies of the
database).
Updateable subscriptions means that the destination servers (subscribers)
can update the data on their own SQL Servers. SQL server will update it
locally and at the same time on the Publisher database, so that the changes
can then be replicated out to the other subscribers. This is done via a
distributed transaction.
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.775 / Virus Database: 522 - Release Date: 08/10/2004
Whats's the utility / advantages of the "Transactional publication with
updatable subscriptions"
thanks for your help!!!
nico
"pralnico" <pralnico@.discussions.microsoft.com> wrote in message
news:1C221973-1029-4380-8C24-A8C55817567F@.microsoft.com...
> Hello,
> Whats's the utility / advantages of the "Transactional publication with
> updatable subscriptions"
> thanks for your help!!!
>
Transactional replication starts with a snapshot. Thereafter only the
changes are replicated (which will typically mean less network traffic /
more frequent updates / less latency between different copies of the
database).
Updateable subscriptions means that the destination servers (subscribers)
can update the data on their own SQL Servers. SQL server will update it
locally and at the same time on the Publisher database, so that the changes
can then be replicated out to the other subscribers. This is done via a
distributed transaction.
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.775 / Virus Database: 522 - Release Date: 08/10/2004
Labels:
advantages,
database,
microsoft,
mysql,
oracle,
publication,
replication,
server,
sql,
subscriptions,
transactional,
utility,
whatss,
withupdatable
Replication
when using snapshots in replication, these files get copied to the hard drive. Can they be automatically deleted after the snapshot is posted?
Thanks
Niles,
if you have anonymous subscribers then they'll stay around until the publication's subscriber's timeout value. If you have standard subscribers, these files will be removed once they have all initialized. For transactional, this is when the distribution a
gent of each subscriber has run. The agent which removes the snapshot files is the distribution cleanup agent, which runs every 10 mins. You could run this immediately (manually) after your last initialization or you could schedule it to run more frequent
ly.
HTH,
Paul Ibison
|||What is the difference between anonymous subscriptions and standard and can it be switched easily
Thanks
|||An anonymous subscription is a type of pull subscription for which detailed
information about the subscription and the Subscriber is not stored. The
Subscriber is responsible for keeping an anonymous subscription
synchronized, and they are particularly used if Subscribers use the Internet
to access publications.
sp_helpsubscription will tell you if the subscription is anonymous or
http://msdn.microsoft.com/library/de...repl3_4dym.asp
Typically, the Subscriber is not explicitly named at the Publisher when
using anonymous subscriptions. So to change from a named subscription to an
anonymous one is not so simple and you'd drop and recreate the subscription.
To see if any of this is relevant to your case have a look at the
allow_anonymous value of sp_helppublication.
HTH,
Paul Ibison
Thanks
Niles,
if you have anonymous subscribers then they'll stay around until the publication's subscriber's timeout value. If you have standard subscribers, these files will be removed once they have all initialized. For transactional, this is when the distribution a
gent of each subscriber has run. The agent which removes the snapshot files is the distribution cleanup agent, which runs every 10 mins. You could run this immediately (manually) after your last initialization or you could schedule it to run more frequent
ly.
HTH,
Paul Ibison
|||What is the difference between anonymous subscriptions and standard and can it be switched easily
Thanks
|||An anonymous subscription is a type of pull subscription for which detailed
information about the subscription and the Subscriber is not stored. The
Subscriber is responsible for keeping an anonymous subscription
synchronized, and they are particularly used if Subscribers use the Internet
to access publications.
sp_helpsubscription will tell you if the subscription is anonymous or
http://msdn.microsoft.com/library/de...repl3_4dym.asp
Typically, the Subscriber is not explicitly named at the Publisher when
using anonymous subscriptions. So to change from a named subscription to an
anonymous one is not so simple and you'd drop and recreate the subscription.
To see if any of this is relevant to your case have a look at the
allow_anonymous value of sp_helppublication.
HTH,
Paul Ibison
Replication
Hello all,
I am setup a replication from DB_A(publisher) to DB_C(subscriber), but I got
a problem after replication created
Example:
Table1 in DB_A, i tried to add a new data field. but DB_C can't see new data
field after snopshot done
Is any method can synchronizate new scheme and new table to subscriber(DB_C)
automatically?
Thanks in advanced.
Schema changes are replicated in sql server 2005 (there are some
restrictions)
In sql server 2000 you can add/drop columns using system stored procedures
(sp_addmergecolumn and sp_dropmergecolumn) so they get replicated.
If this doesnt answer your question, please LMK
MC
"beachboy" <stanley@.javacatz.com> wrote in message
news:OxM2RVWLGHA.720@.TK2MSFTNGP14.phx.gbl...
> Hello all,
> I am setup a replication from DB_A(publisher) to DB_C(subscriber), but I
> got
> a problem after replication created
> Example:
> Table1 in DB_A, i tried to add a new data field. but DB_C can't see new
> data
> field after snopshot done
> Is any method can synchronizate new scheme and new table to
> subscriber(DB_C)
> automatically?
> Thanks in advanced.
>
>
|||Assuming we're talking about SQL 2000, the correct stored procedures to call
are sp_repladdcolumn and sp_repldropcolumn.
Using these procs, there is no need to create a snapshot for the existing
subscribers - the column changes will occur as you synchronize.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Urgh.
Thank you for correcting me, it serves me right for not checking before
posting.
My apologies beachboy.
MC
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:eg2RR1WLGHA.3164@.TK2MSFTNGP11.phx.gbl...
> Assuming we're talking about SQL 2000, the correct stored procedures to
> call are sp_repladdcolumn and sp_repldropcolumn.
> Using these procs, there is no need to create a snapshot for the existing
> subscribers - the column changes will occur as you synchronize.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||Thank you for your informations
Sorry that I am not a professional of sql server
Yes. I am using SQL 2000 standard edition. How to I call those procedure
(sp_repladdcolumn and sp_repldropcolumn)?
from DB_A or from DB_C?
How about if new table added?
Thanks in advanced.
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> glsD:eg2RR1WLGHA.3164@.TK2MSFTNGP11.phx.g bl...
> Assuming we're talking about SQL 2000, the correct stored procedures to
> call are sp_repladdcolumn and sp_repldropcolumn.
> Using these procs, there is no need to create a snapshot for the existing
> subscribers - the column changes will occur as you synchronize.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||You should execute the procedures on publisher. When you synch databases,
changes will be propagated to the subscriber.
Adding new table to replication means you must generate new snapshot and
re-initialize subscriptions.
MC
"beachboy" <jpsteambun@.yahoo.com.hk> wrote in message
news:O4DtH8XLGHA.1676@.TK2MSFTNGP09.phx.gbl...
> Thank you for your informations
> Sorry that I am not a professional of sql server
> Yes. I am using SQL 2000 standard edition. How to I call those procedure
> (sp_repladdcolumn and sp_repldropcolumn)?
> from DB_A or from DB_C?
> How about if new table added?
> Thanks in advanced.
>
> "Paul Ibison" <Paul.Ibison@.Pygmalion.Com>
> glsD:eg2RR1WLGHA.3164@.TK2MSFTNGP11.phx.g bl...
>
|||oic
for new scheme modification: execute store procedure, and corrected scheme
will send at next push
for new table on database: set a new "Push New Publcation" and then
re-initialize subscription
but do I need to remove the old snopshot?
Thanks.
"MC" <marko_culo#@.#yahoo#.#com#> glsD:eS2rOAYLGHA.536@.TK2MSFTNGP09.phx.gb l...
> You should execute the procedures on publisher. When you synch databases,
> changes will be propagated to the subscriber.
> Adding new table to replication means you must generate new snapshot and
> re-initialize subscriptions.
> MC
> "beachboy" <jpsteambun@.yahoo.com.hk> wrote in message
> news:O4DtH8XLGHA.1676@.TK2MSFTNGP09.phx.gbl...
>
|||Adding a new table doesn't require a reinitialization. The new snapshot will
contain just the new table (transactional) or all articles (merge) but in
either case synchronising will just propagate the new table and not all the
other articles.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||There is a difference between adding an article (table) to the existing
replication (publication) and adding a new publication to the setup. If you
add the article, run the snapshot and then synch if you left the option to
recreate objects. If you dont recreate objects then youll need to do some
more work. LMK if thats the case.
MC
"beachboy" <jpsteambun@.yahoo.com.hk> wrote in message
news:uZZu0GZLGHA.1124@.TK2MSFTNGP10.phx.gbl...
> oic
> for new scheme modification: execute store procedure, and corrected scheme
> will send at next push
> for new table on database: set a new "Push New Publcation" and then
> re-initialize subscription
> but do I need to remove the old snopshot?
> Thanks.
>
> "MC" <marko_culo#@.#yahoo#.#com#>
> glsD:eS2rOAYLGHA.536@.TK2MSFTNGP09.phx.gb l...
>
|||Jim,
I believe that SQL Server 2005 Enterprise Edition has Oracle replication as
a feature. I have not investigated this (no need) so I do not know the
details.
RLF
"JIM.H." <JIMH@.discussions.microsoft.com> wrote in message
news:4F65866C-59DD-4907-B7AE-60114AAF57F6@.microsoft.com...
> Hello,
> Is it possible to have replication between SQL Server and Oracle DB?
> Thanks,
>
I am setup a replication from DB_A(publisher) to DB_C(subscriber), but I got
a problem after replication created
Example:
Table1 in DB_A, i tried to add a new data field. but DB_C can't see new data
field after snopshot done
Is any method can synchronizate new scheme and new table to subscriber(DB_C)
automatically?
Thanks in advanced.
Schema changes are replicated in sql server 2005 (there are some
restrictions)
In sql server 2000 you can add/drop columns using system stored procedures
(sp_addmergecolumn and sp_dropmergecolumn) so they get replicated.
If this doesnt answer your question, please LMK
MC
"beachboy" <stanley@.javacatz.com> wrote in message
news:OxM2RVWLGHA.720@.TK2MSFTNGP14.phx.gbl...
> Hello all,
> I am setup a replication from DB_A(publisher) to DB_C(subscriber), but I
> got
> a problem after replication created
> Example:
> Table1 in DB_A, i tried to add a new data field. but DB_C can't see new
> data
> field after snopshot done
> Is any method can synchronizate new scheme and new table to
> subscriber(DB_C)
> automatically?
> Thanks in advanced.
>
>
|||Assuming we're talking about SQL 2000, the correct stored procedures to call
are sp_repladdcolumn and sp_repldropcolumn.
Using these procs, there is no need to create a snapshot for the existing
subscribers - the column changes will occur as you synchronize.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Urgh.
Thank you for correcting me, it serves me right for not checking before
posting.
My apologies beachboy.
MC
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:eg2RR1WLGHA.3164@.TK2MSFTNGP11.phx.gbl...
> Assuming we're talking about SQL 2000, the correct stored procedures to
> call are sp_repladdcolumn and sp_repldropcolumn.
> Using these procs, there is no need to create a snapshot for the existing
> subscribers - the column changes will occur as you synchronize.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||Thank you for your informations
Sorry that I am not a professional of sql server
Yes. I am using SQL 2000 standard edition. How to I call those procedure
(sp_repladdcolumn and sp_repldropcolumn)?
from DB_A or from DB_C?
How about if new table added?
Thanks in advanced.
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> glsD:eg2RR1WLGHA.3164@.TK2MSFTNGP11.phx.g bl...
> Assuming we're talking about SQL 2000, the correct stored procedures to
> call are sp_repladdcolumn and sp_repldropcolumn.
> Using these procs, there is no need to create a snapshot for the existing
> subscribers - the column changes will occur as you synchronize.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||You should execute the procedures on publisher. When you synch databases,
changes will be propagated to the subscriber.
Adding new table to replication means you must generate new snapshot and
re-initialize subscriptions.
MC
"beachboy" <jpsteambun@.yahoo.com.hk> wrote in message
news:O4DtH8XLGHA.1676@.TK2MSFTNGP09.phx.gbl...
> Thank you for your informations
> Sorry that I am not a professional of sql server
> Yes. I am using SQL 2000 standard edition. How to I call those procedure
> (sp_repladdcolumn and sp_repldropcolumn)?
> from DB_A or from DB_C?
> How about if new table added?
> Thanks in advanced.
>
> "Paul Ibison" <Paul.Ibison@.Pygmalion.Com>
> glsD:eg2RR1WLGHA.3164@.TK2MSFTNGP11.phx.g bl...
>
|||oic
for new scheme modification: execute store procedure, and corrected scheme
will send at next push
for new table on database: set a new "Push New Publcation" and then
re-initialize subscription
but do I need to remove the old snopshot?
Thanks.
"MC" <marko_culo#@.#yahoo#.#com#> glsD:eS2rOAYLGHA.536@.TK2MSFTNGP09.phx.gb l...
> You should execute the procedures on publisher. When you synch databases,
> changes will be propagated to the subscriber.
> Adding new table to replication means you must generate new snapshot and
> re-initialize subscriptions.
> MC
> "beachboy" <jpsteambun@.yahoo.com.hk> wrote in message
> news:O4DtH8XLGHA.1676@.TK2MSFTNGP09.phx.gbl...
>
|||Adding a new table doesn't require a reinitialization. The new snapshot will
contain just the new table (transactional) or all articles (merge) but in
either case synchronising will just propagate the new table and not all the
other articles.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||There is a difference between adding an article (table) to the existing
replication (publication) and adding a new publication to the setup. If you
add the article, run the snapshot and then synch if you left the option to
recreate objects. If you dont recreate objects then youll need to do some
more work. LMK if thats the case.
MC
"beachboy" <jpsteambun@.yahoo.com.hk> wrote in message
news:uZZu0GZLGHA.1124@.TK2MSFTNGP10.phx.gbl...
> oic
> for new scheme modification: execute store procedure, and corrected scheme
> will send at next push
> for new table on database: set a new "Push New Publcation" and then
> re-initialize subscription
> but do I need to remove the old snopshot?
> Thanks.
>
> "MC" <marko_culo#@.#yahoo#.#com#>
> glsD:eS2rOAYLGHA.536@.TK2MSFTNGP09.phx.gb l...
>
|||Jim,
I believe that SQL Server 2005 Enterprise Edition has Oracle replication as
a feature. I have not investigated this (no need) so I do not know the
details.
RLF
"JIM.H." <JIMH@.discussions.microsoft.com> wrote in message
news:4F65866C-59DD-4907-B7AE-60114AAF57F6@.microsoft.com...
> Hello,
> Is it possible to have replication between SQL Server and Oracle DB?
> Thanks,
>
Labels:
createdexampletable1,
database,
db_a,
db_c,
gota,
microsoft,
mysql,
oracle,
publisher,
replication,
server,
setup,
sql,
subscriber
replication
wot should be the ans of the below scenario..
You are the administrator of a SQL Server 2000 computer. You want to set up snapshot replication on the server. The server will serve as Publisher and Distributor for a minimum of 40/50 Subscribers. Currently, you want to publish 3GB/4GB of data, but the data is expected to grow over time. Subscribers will receive a new snapshot each month. You want to minimize the workload on the Publisher/Distributor. Which two actions should you take to configure snapshot replication? (Each correct answer presents part of the solution. Choose two)
a. Store the snapshot in the default folder on the Publisher/Distributor.
b. Store the snapshot in an alternative folder on the Publisher/Distributor.
c. Store the snapshot in a shared folder on a file server.
d. Create pull subscriptions.
e. Create push subscriptions.I would store the snapshot on a file server
and create pull subscriptions
--
Dandy Weyn, Belgium
MCSE, MCSA, MCDBA, MCT
http://www.dandyman.net
Check my SQL Server resource pages (currently under construction)
http://www.dandyman.net/sql
"rahul" <anonymous@.discussions.microsoft.com> wrote in message
news:A26AAAD3-6275-4C3D-90D9-F97CEB0FE429@.microsoft.com...
> wot should be the ans of the below scenario...
> You are the administrator of a SQL Server 2000 computer. You want to set
up snapshot replication on the server. The server will serve as Publisher
and Distributor for a minimum of 40/50 Subscribers. Currently, you want to
publish 3GB/4GB of data, but the data is expected to grow over time.
Subscribers will receive a new snapshot each month. You want to minimize the
workload on the Publisher/Distributor. Which two actions should you take to
configure snapshot replication? (Each correct answer presents part of the
solution. Choose two)
>
> a. Store the snapshot in the default folder on the Publisher/Distributor.
> b. Store the snapshot in an alternative folder on the
Publisher/Distributor.
> c. Store the snapshot in a shared folder on a file server.
> d. Create pull subscriptions.
> e. Create push subscriptions.
>|||Although I am not a replication expert, I would choose c and d.
Pull subscriptions ( by default) cause the distribution process to run at
the subscriber ( and not the publisher) which offloads work from the
publisher... ( As a side note, SQL 2000 allows a push subscription to have
the subscriber do his own work as well, it is called remote activation..)
Storing the snapshot files somewhere OTHER than the publisher/distributor
simply means that the publisher does NOT have to do IO during the initial
sync with the subscriber..
Hope this help.s
"rahul" <anonymous@.discussions.microsoft.com> wrote in message
news:A26AAAD3-6275-4C3D-90D9-F97CEB0FE429@.microsoft.com...
> wot should be the ans of the below scenario...
> You are the administrator of a SQL Server 2000 computer. You want to set
up snapshot replication on the server. The server will serve as Publisher
and Distributor for a minimum of 40/50 Subscribers. Currently, you want to
publish 3GB/4GB of data, but the data is expected to grow over time.
Subscribers will receive a new snapshot each month. You want to minimize the
workload on the Publisher/Distributor. Which two actions should you take to
configure snapshot replication? (Each correct answer presents part of the
solution. Choose two)
>
> a. Store the snapshot in the default folder on the Publisher/Distributor.
> b. Store the snapshot in an alternative folder on the
Publisher/Distributor.
> c. Store the snapshot in a shared folder on a file server.
> d. Create pull subscriptions.
> e. Create push subscriptions.
>
You are the administrator of a SQL Server 2000 computer. You want to set up snapshot replication on the server. The server will serve as Publisher and Distributor for a minimum of 40/50 Subscribers. Currently, you want to publish 3GB/4GB of data, but the data is expected to grow over time. Subscribers will receive a new snapshot each month. You want to minimize the workload on the Publisher/Distributor. Which two actions should you take to configure snapshot replication? (Each correct answer presents part of the solution. Choose two)
a. Store the snapshot in the default folder on the Publisher/Distributor.
b. Store the snapshot in an alternative folder on the Publisher/Distributor.
c. Store the snapshot in a shared folder on a file server.
d. Create pull subscriptions.
e. Create push subscriptions.I would store the snapshot on a file server
and create pull subscriptions
--
Dandy Weyn, Belgium
MCSE, MCSA, MCDBA, MCT
http://www.dandyman.net
Check my SQL Server resource pages (currently under construction)
http://www.dandyman.net/sql
"rahul" <anonymous@.discussions.microsoft.com> wrote in message
news:A26AAAD3-6275-4C3D-90D9-F97CEB0FE429@.microsoft.com...
> wot should be the ans of the below scenario...
> You are the administrator of a SQL Server 2000 computer. You want to set
up snapshot replication on the server. The server will serve as Publisher
and Distributor for a minimum of 40/50 Subscribers. Currently, you want to
publish 3GB/4GB of data, but the data is expected to grow over time.
Subscribers will receive a new snapshot each month. You want to minimize the
workload on the Publisher/Distributor. Which two actions should you take to
configure snapshot replication? (Each correct answer presents part of the
solution. Choose two)
>
> a. Store the snapshot in the default folder on the Publisher/Distributor.
> b. Store the snapshot in an alternative folder on the
Publisher/Distributor.
> c. Store the snapshot in a shared folder on a file server.
> d. Create pull subscriptions.
> e. Create push subscriptions.
>|||Although I am not a replication expert, I would choose c and d.
Pull subscriptions ( by default) cause the distribution process to run at
the subscriber ( and not the publisher) which offloads work from the
publisher... ( As a side note, SQL 2000 allows a push subscription to have
the subscriber do his own work as well, it is called remote activation..)
Storing the snapshot files somewhere OTHER than the publisher/distributor
simply means that the publisher does NOT have to do IO during the initial
sync with the subscriber..
Hope this help.s
"rahul" <anonymous@.discussions.microsoft.com> wrote in message
news:A26AAAD3-6275-4C3D-90D9-F97CEB0FE429@.microsoft.com...
> wot should be the ans of the below scenario...
> You are the administrator of a SQL Server 2000 computer. You want to set
up snapshot replication on the server. The server will serve as Publisher
and Distributor for a minimum of 40/50 Subscribers. Currently, you want to
publish 3GB/4GB of data, but the data is expected to grow over time.
Subscribers will receive a new snapshot each month. You want to minimize the
workload on the Publisher/Distributor. Which two actions should you take to
configure snapshot replication? (Each correct answer presents part of the
solution. Choose two)
>
> a. Store the snapshot in the default folder on the Publisher/Distributor.
> b. Store the snapshot in an alternative folder on the
Publisher/Distributor.
> c. Store the snapshot in a shared folder on a file server.
> d. Create pull subscriptions.
> e. Create push subscriptions.
>
Replication
when using snapshots in replication, these files get copied to the hard drive. Can they be automatically deleted after the snapshot is posted
ThanksAn anonymous subscription is a type of pull subscription for which detailed
information about the subscription and the Subscriber is not stored. The
Subscriber is responsible for keeping an anonymous subscription
synchronized, and they are particularly used if Subscribers use the Internet
to access publications.
sp_helpsubscription will tell you if the subscription is anonymous or
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tsqlref/ts_sp_repl3_4dym.asp
Typically, the Subscriber is not explicitly named at the Publisher when
using anonymous subscriptions. So to change from a named subscription to an
anonymous one is not so simple and you'd drop and recreate the subscription.
To see if any of this is relevant to your case have a look at the
allow_anonymous value of sp_helppublication.
HTH,
Paul Ibison
ThanksAn anonymous subscription is a type of pull subscription for which detailed
information about the subscription and the Subscriber is not stored. The
Subscriber is responsible for keeping an anonymous subscription
synchronized, and they are particularly used if Subscribers use the Internet
to access publications.
sp_helpsubscription will tell you if the subscription is anonymous or
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tsqlref/ts_sp_repl3_4dym.asp
Typically, the Subscriber is not explicitly named at the Publisher when
using anonymous subscriptions. So to change from a named subscription to an
anonymous one is not so simple and you'd drop and recreate the subscription.
To see if any of this is relevant to your case have a look at the
allow_anonymous value of sp_helppublication.
HTH,
Paul Ibison
Replication
Hi,
Am trying to configure replication in SQL server 6.5. But when I to configure replication menu and select Install publishing, it gives the following error
Replication cannot be installed as @.@.SERVERNAME is NUL
Has anybody faced this kind of problem? BTW, my server name has Hyphen, but I guess that shouldn't be an issue as I had read in one of the article that in 6.5, this problem is taken care of. Could there be any other issue
Thanks very much in advanc
GYKDo you get a NULL if you run the following command?
SELECT @.@.SERVERNAME
GO
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
What hardware is your SQL Server running on?
http://vyaskn.tripod.com/poll.htm
"GYK" <anonymous@.discussions.microsoft.com> wrote in message
news:78C27465-53D5-4DDF-8A9C-1E8A8C436364@.microsoft.com...
Hi,
Am trying to configure replication in SQL server 6.5. But when I to
configure replication menu and select Install publishing, it gives the
following error;
Replication cannot be installed as @.@.SERVERNAME is NULL
Has anybody faced this kind of problem? BTW, my server name has Hyphen, but
I guess that shouldn't be an issue as I had read in one of the article that
in 6.5, this problem is taken care of. Could there be any other issue?
Thanks very much in advance
GYK|||YES
I get NULL when I run SELECT @.@.SERVERNAME
Thanks
GYK
Am trying to configure replication in SQL server 6.5. But when I to configure replication menu and select Install publishing, it gives the following error
Replication cannot be installed as @.@.SERVERNAME is NUL
Has anybody faced this kind of problem? BTW, my server name has Hyphen, but I guess that shouldn't be an issue as I had read in one of the article that in 6.5, this problem is taken care of. Could there be any other issue
Thanks very much in advanc
GYKDo you get a NULL if you run the following command?
SELECT @.@.SERVERNAME
GO
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
What hardware is your SQL Server running on?
http://vyaskn.tripod.com/poll.htm
"GYK" <anonymous@.discussions.microsoft.com> wrote in message
news:78C27465-53D5-4DDF-8A9C-1E8A8C436364@.microsoft.com...
Hi,
Am trying to configure replication in SQL server 6.5. But when I to
configure replication menu and select Install publishing, it gives the
following error;
Replication cannot be installed as @.@.SERVERNAME is NULL
Has anybody faced this kind of problem? BTW, my server name has Hyphen, but
I guess that shouldn't be an issue as I had read in one of the article that
in 6.5, this problem is taken care of. Could there be any other issue?
Thanks very much in advance
GYK|||YES
I get NULL when I run SELECT @.@.SERVERNAME
Thanks
GYK
Subscribe to:
Posts (Atom)