Showing posts with label publication. Show all posts
Showing posts with label publication. Show all posts

Monday, March 26, 2012

Pushing a publication for just one subscriber?

This may be a basic question, if so, apologies in advance.
We're having to set up a new subscriber for several publications. From
what we remember, the last time we added a subscriber, running the
snapshot agent caused every subscriber (not just the new one) to get a
brand new copy of the table. This would take a considerable amount of
time, as some of the subscribers are on slow connections. Is there a
trick to just push the subscription to the one new subscriber? Many
thanks.
Im guessing what happened is someone clicked the "reinitialize all
subscriptions option" which would cause that behavior. Adding 1 subscription
will not do that.
<bourgon@.gmail.com> wrote in message
news:1119539711.905957.139680@.o13g2000cwo.googlegr oups.com...
> This may be a basic question, if so, apologies in advance.
> We're having to set up a new subscriber for several publications. From
> what we remember, the last time we added a subscriber, running the
> snapshot agent caused every subscriber (not just the new one) to get a
> brand new copy of the table. This would take a considerable amount of
> time, as some of the subscribers are on slow connections. Is there a
> trick to just push the subscription to the one new subscriber? Many
> thanks.
>

Pushing 2000 merge publication to 2005 server

I am attempting to push a SQL 2000 publication to a SQL 2005 server. I
realize that Microsoft does not recommend this, but I haven't found anything
that says that it can not be done.
When I try to register the SQL 2005 server in my Enterprise Manager I get
"To connect to this server you must use SQL Server Management Studio or SQL
Server Management Objects (SMO)".
Any ideas on how I can get around this?
I have over 100 locations that I run merge replication with.
Thanks.
Gary
Connect to all servers through SSMS (SQL Server Management Studio).
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
"gmac2" <gmac2@.discussions.microsoft.com> wrote in message
news:8F874E11-E1D1-4A6C-86EE-07C2FCE1DB35@.microsoft.com...
> I am attempting to push a SQL 2000 publication to a SQL 2005 server. I
> realize that Microsoft does not recommend this, but I haven't found
> anything
> that says that it can not be done.
> When I try to register the SQL 2005 server in my Enterprise Manager I get
> "To connect to this server you must use SQL Server Management Studio or
> SQL
> Server Management Objects (SMO)".
> Any ideas on how I can get around this?
> I have over 100 locations that I run merge replication with.
> Thanks.
> Gary
|||I am trying to do the push from the SQL 2000 end, I do not have access to the
2005 server as it belongs to a vendor. Any other ways around this?
I did get around registering the server throught publishing the database (I
had the other party create an empty database on their end) but then when I
try to push the subscriotion it can not deliver the snapshot as it gets the
sp_Msupdatesysmergeartciles has too many arguments specified (8144 error).
Thanks,
Gary
"gmac2" wrote:

> I am attempting to push a SQL 2000 publication to a SQL 2005 server. I
> realize that Microsoft does not recommend this, but I haven't found anything
> that says that it can not be done.
> When I try to register the SQL 2005 server in my Enterprise Manager I get
> "To connect to this server you must use SQL Server Management Studio or SQL
> Server Management Objects (SMO)".
> Any ideas on how I can get around this?
> I have over 100 locations that I run merge replication with.
> Thanks.
> Gary

push subscription error Xprepl.dll

I used a working publication as a template to create a publication.
Everything was good
I then opened the propeties and added a push subscribtion and
selected execute snapshot immediately.
The merge snapshot agent errored out.
A review of the session shows the following:
connection to publisher is good
connection to subscriber is good
connection to database good
execute <article>.sc good
fail: can not find DLL Xprepl.dll
Any ideas?
Is this in your binn directory? It is called xprepl.dll or xpcobrepl.dll
there.
I don't have a sql 2000 system here, but can you try this
sp_helpextendedproc and see if any of the procs reference it?
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
"mj" <mj@.discussions.microsoft.com> wrote in message
news:9F4BBB11-3610-4E9C-B961-554BB322D938@.microsoft.com...
> I used a working publication as a template to create a publication.
> Everything was good
> I then opened the propeties and added a push subscribtion and
> selected execute snapshot immediately.
> The merge snapshot agent errored out.
> A review of the session shows the following:
> connection to publisher is good
> connection to subscriber is good
> connection to database good
> execute <article>.sc good
> fail: can not find DLL Xprepl.dll
>
> Any ideas?
>
|||I will verify this shortly.
2nd question:
does the subscribing server have to be enterprise, standard or does it
matter?
"Hilary Cotter" wrote:

> Is this in your binn directory? It is called xprepl.dll or xpcobrepl.dll
> there.
> I don't have a sql 2000 system here, but can you try this
> sp_helpextendedproc and see if any of the procs reference it?
>
> --
> 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
>
> "mj" <mj@.discussions.microsoft.com> wrote in message
> news:9F4BBB11-3610-4E9C-B961-554BB322D938@.microsoft.com...
>
>
|||Latest update:
my subscriber is running sql server standard edition, service pack 3a
my publisher is running sql server enterprise edition, service pack 4
the subscriber has xprelp.dll in binn directory
and is going to run sp_helpextendedproc and get back.
I will update this link shortly.
Thanks
"mj" wrote:
[vbcol=seagreen]
> I will verify this shortly.
> 2nd question:
> does the subscribing server have to be enterprise, standard or does it
> matter?
>
>
> "Hilary Cotter" wrote:
|||This topology is supported. MS recommends running consistent service packs
between all servers of the same version.
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
"mj" <mj@.discussions.microsoft.com> wrote in message
news:0917B4D9-C17B-43E6-A481-620DAAB5F1FB@.microsoft.com...[vbcol=seagreen]
> Latest update:
> my subscriber is running sql server standard edition, service pack 3a
> my publisher is running sql server enterprise edition, service pack 4
> the subscriber has xprelp.dll in binn directory
> and is going to run sp_helpextendedproc and get back.
> I will update this link shortly.
> Thanks
>
> "mj" wrote:

Push Subscription Connection Fails

I cannot get internet connection to work for push subscription to transactional publication.

Publisher/distributor: SQL Server 2000
Subscriber: SQL Server 2000
Connection: TCP/IP, SQL Authentication. Works fine from SQLEM or Query Analyzer.
Subscription: push, transactional, schema/data already initialized.

When I run distributor agent fails with "The process could not connect to subscriber 'TEST'", error "Server does not exist or access denied".

Agent output does not give anything more specific. It fails after...
Connecting to Subscriber 'TEST'
Connecting to Subscriber 'TEST.REPL'

Profiler shows nothing happening at all.

If change subscriber setup on distributor to use trusted connection instead of SQL Auth it works fine.

Any ideas?OK, so all the replication experts are on vacation this week but I eventually managed to figure it out myself.

When defining subscribers (through 'distributor properties') use the subscriber TCP/IP address directly and not a server alias like I was doing. Silly Billy!

push publication for heterogeneous subscriber

Hi,
I have added an oracle linked server as a subscriber, when I create a push publication, I can not see the oracle linked server as an enabled subscriber under the enabled subscriber list in the 'Push Publication' wizard. Is this something I need to worry o
r this is just how linked Oracle server works?
Thanks.
Once you have created your linked server to Oracle you have to Tools | Replicaiton | Configure Distributors, Publishers, Susbcribers, select the Subscribers tab, click on new, select ole db data source, locate your Oracle Linked Server, enter the account
info, click on it.
When you create your publication make sure you enable it for hetergeneous susbcribers.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html

Monday, March 12, 2012

Pull Subscription Continues to Run Indefinitely

I have a publication that is being pulled and when I execute a UPDATE command
example: UPDATE Oils SET Description = 'This is a description'
The SQL Query Analyzer completes the command successfully.
I am receiving confirmation that more than 30,0000 rows have been updated
when I run this command.
When I go to the Replication Manager and view the Subscription it continues
to run indefinitely.
In some cases more than 8 hrs.
Are there some parameters that might need to be set when running this
process?
Any feedback is appreciated.
Thank you
open up profiler on the subscriber and see if there is any activity from the
replication process.
"BSandia" <BSandia@.discussions.microsoft.com> wrote in message
news:2B137D55-AD5A-4E61-9D77-9CB0DDF5C1B9@.microsoft.com...
>I have a publication that is being pulled and when I execute a UPDATE
>command
> example: UPDATE Oils SET Description = 'This is a description'
> The SQL Query Analyzer completes the command successfully.
> I am receiving confirmation that more than 30,0000 rows have been updated
> when I run this command.
> When I go to the Replication Manager and view the Subscription it
> continues
> to run indefinitely.
> In some cases more than 8 hrs.
> Are there some parameters that might need to be set when running this
> process?
> Any feedback is appreciated.
> Thank you
>
>
>
|||There are several optimization techniques for transactional replication one
half is to create a new distribution agent profile with a lower amount of
transactions set per commit, and the second half is to add [-MaxCmdsInTran
10000] to the log reader agent where 10000 is the maximum number of commands
per transaction. With this switch added to the execution command in the
actual log reader agent you will only send 10000 commands down the
replication pipe per transaction. The combination of these two performance
enhancements will reduce that 8 hour run to quite a bit smaller.
"BSandia" wrote:

> I have a publication that is being pulled and when I execute a UPDATE command
> example: UPDATE Oils SET Description = 'This is a description'
> The SQL Query Analyzer completes the command successfully.
> I am receiving confirmation that more than 30,0000 rows have been updated
> when I run this command.
> When I go to the Replication Manager and view the Subscription it continues
> to run indefinitely.
> In some cases more than 8 hrs.
> Are there some parameters that might need to be set when running this
> process?
> Any feedback is appreciated.
> Thank you
>
>
>
|||Thank you for your responsive posts I will give them a try.
Brett
"Richard S. Hale" wrote:
[vbcol=seagreen]
> There are several optimization techniques for transactional replication one
> half is to create a new distribution agent profile with a lower amount of
> transactions set per commit, and the second half is to add [-MaxCmdsInTran
> 10000] to the log reader agent where 10000 is the maximum number of commands
> per transaction. With this switch added to the execution command in the
> actual log reader agent you will only send 10000 commands down the
> replication pipe per transaction. The combination of these two performance
> enhancements will reduce that 8 hour run to quite a bit smaller.
> "BSandia" wrote:

Pull subscription

Hi,
I created a transactionnal publication with one pull subscription. All
work fine, the transactions are replicated on subscriber. But on the
subscriber, I have two subscriptions under the "Local subscription" in
SQL Server Management Studio with one that don't have a publication
name. I cannot see properties, I get this message :
- SQL Server is unable to complete the operation.
-
- You must manage this subscription from the Publisher because it
shares a Distribution Agent with subscriptions - to other
publications from the same publication database. (Subscription
Properties)
This subscriptions appears after I call
sp_addpullsubscription_agent...
It's normal?I suggest you to post this message to
"microsoft.public.sqlserver.replication"
You'll probably get more answers about this issue there.
--
Ekrem Önsoy
"PPaquin" <patrick.paquin@.gmail.com> wrote in message
news:1189199171.692355.60980@.19g2000hsx.googlegroups.com...
> Hi,
> I created a transactionnal publication with one pull subscription. All
> work fine, the transactions are replicated on subscriber. But on the
> subscriber, I have two subscriptions under the "Local subscription" in
> SQL Server Management Studio with one that don't have a publication
> name. I cannot see properties, I get this message :
> - SQL Server is unable to complete the operation.
> -
> - You must manage this subscription from the Publisher because it
> shares a Distribution Agent with subscriptions - to other
> publications from the same publication database. (Subscription
> Properties)
> This subscriptions appears after I call
> sp_addpullsubscription_agent...
> It's normal?
>|||Thanks, I do...
On 7 sep, 17:20, Ekrem =D6nsoy <ek...@.btegitim.com> wrote:
> I suggest you to post this message to
> "microsoft.public.sqlserver.replication"
> You'll probably get more answers about this issue there.
> --
> Ekrem =D6nsoy
> "PPaquin" <patrick.paq...@.gmail.com> wrote in message
> news:1189199171.692355.60980@.19g2000hsx.googlegroups.com...
>
> > Hi,
> > I created a transactionnal publication with one pull subscription. All
> > work fine, the transactions are replicated on subscriber. But on the
> > subscriber, I have two subscriptions under the "Local subscription" in
> > SQL Server Management Studio with one that don't have a publication
> > name. I cannot see properties, I get this message :
> > - SQL Server is unable to complete the operation.
> > -
> > - You must manage this subscription from the Publisher because it
> > shares a Distribution Agent with subscriptions - to other
> > publications from the same publication database. (Subscription
> > Properties)
> > This subscriptions appears after I call
> > sp_addpullsubscription_agent...
> > It's normal... Masquer le texte des messages pr=E9c=E9dents -
> - Afficher le texte des messages pr=E9c=E9dents -

Pull replication errors...

Hi,
the idea is to setup an offsite backup of our single sql server, have
created a publication on the MASTER server, and pulled it to the offsite
server using FTP, downloaded snapshot, replicated transactions, all appeared
to work, generated schema, but the frontend database app didnt run, loads of
various errors showing up.
decided to restore the database from disk to the backup server, to check the
app is working fine, which it now is, so all i need to do is replicated the
changes in the tables on the master server to the offsite server, only needs
to be one-way, the offsite is only for backup read only...changed the
publication to tables only, re-created snapshot and now get errors saying...
Cannot update identity column. The step failed
help please on solution or other ways to achive this.
comment the identity column update in the update proc.
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
"Matt" <mattnj@.hotmail.com> wrote in message
news:d9tqpf$gkn$1@.news.freedom2surf.net...
> Hi,
> the idea is to setup an offsite backup of our single sql server, have
> created a publication on the MASTER server, and pulled it to the offsite
> server using FTP, downloaded snapshot, replicated transactions, all
> appeared to work, generated schema, but the frontend database app didnt
> run, loads of various errors showing up.
> decided to restore the database from disk to the backup server, to check
> the app is working fine, which it now is, so all i need to do is
> replicated the changes in the tables on the master server to the offsite
> server, only needs to be one-way, the offsite is only for backup read
> only...changed the publication to tables only, re-created snapshot and
> now get errors saying...
> Cannot update identity column. The step failed
> help please on solution or other ways to achive this.
>

Friday, March 9, 2012

Pull from the DMZ?

Ok, so in my scenario, if I have a one way trust & am already replicating to the DMZ, I should be able to setup a publication on the DMZ & pull, right?
Yes, I have done this. I think you will need to make the publication on the
server in the DMZ anonymous, so you don't have to register the subscriber on
the DMZ Publisher.
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
"JLS" <jlshoop@.hotmail.com> wrote in message
news:%237vu$Du7FHA.1032@.TK2MSFTNGP11.phx.gbl...
Ok, so in my scenario, if I have a one way trust & am already replicating to
the DMZ, I should be able to setup a publication on the DMZ & pull, right?
|||Oh thanx for adding the bit about making the DMZ publication anonymous, you may have actually saved the last strand of hair on my head from being ripped out!!!!
Jude
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message news:%23NQwMFu7FHA.2040@.TK2MSFTNGP14.phx.gbl...
Yes, I have done this. I think you will need to make the publication on the
server in the DMZ anonymous, so you don't have to register the subscriber on
the DMZ Publisher.
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
"JLS" <jlshoop@.hotmail.com> wrote in message
news:%237vu$Du7FHA.1032@.TK2MSFTNGP11.phx.gbl...
Ok, so in my scenario, if I have a one way trust & am already replicating to
the DMZ, I should be able to setup a publication on the DMZ & pull, right?

Wednesday, March 7, 2012

publisher malfunction

Hi,
Has anyone seen a problem like this:
when trying to add an article to an existing publication (i.e. running
sp_addarticle) I get the following error if I run it from my workstation:
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckForData
(CheckforData()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
Connection Broken
the error is a bit more descriptive when running from the server console:
Server: Msg 8526, Level 16, State 2, Procedure sp_helpdistributor, Line 79
Cannot go remote while the session is enlisted in a distributed transaction
that has an active savepoint.
Connection Broken
Any input would be appreciated
run a dbcc opentrans and see if there is an open or orphaned transaction.
use dbcc inputbuffer to evaluate whether you can kill it or not. If so, kill
it and try to run the sp_addarticle command again.
Also is this with a remote distributor?
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
"Mor DeRor" <MorDeRor@.discussions.microsoft.com> wrote in message
news:55DBD5B3-15F1-4130-8BB8-F3B2FA7294BC@.microsoft.com...
> Hi,
> Has anyone seen a problem like this:
> when trying to add an article to an existing publication (i.e. running
> sp_addarticle) I get the following error if I run it from my workstation:
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckForData
> (CheckforData()).
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation.
> Connection Broken
> the error is a bit more descriptive when running from the server console:
> Server: Msg 8526, Level 16, State 2, Procedure sp_helpdistributor, Line 79
> Cannot go remote while the session is enlisted in a distributed
> transaction
> that has an active savepoint.
> Connection Broken
> Any input would be appreciated
|||Thanks Hilary, but it does not look like there is an open transaction. here
is the oputput of DBCC OPENTRAN:
Replicated Transaction Information:
Oldest distributed LSN : (2215838:4377:1)
Oldest non-distributed LSN : (0:0:0)
DBCC execution completed. If DBCC printed error messages, contact your
system administrator.
"Hilary Cotter" wrote:

> run a dbcc opentrans and see if there is an open or orphaned transaction.
> use dbcc inputbuffer to evaluate whether you can kill it or not. If so, kill
> it and try to run the sp_addarticle command again.
> Also is this with a remote distributor?
> --
> 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
>
> "Mor DeRor" <MorDeRor@.discussions.microsoft.com> wrote in message
> news:55DBD5B3-15F1-4130-8BB8-F3B2FA7294BC@.microsoft.com...
>
>
|||I found a solution, in case anyone else is interested. It had to do with
"remote proc trans" option being turned on. Here is a link to the forum where
I found it:
http://www.sql-server-performance.com/forum/topic.asp?TOPIC_ID=18530
"Mor DeRor" wrote:
[vbcol=seagreen]
> Thanks Hilary, but it does not look like there is an open transaction. here
> is the oputput of DBCC OPENTRAN:
> Replicated Transaction Information:
> Oldest distributed LSN : (2215838:4377:1)
> Oldest non-distributed LSN : (0:0:0)
> DBCC execution completed. If DBCC printed error messages, contact your
> system administrator.
>
> "Hilary Cotter" wrote:

Publisher cannot be droped becaused Remote Distributor down

Hi all,
I am having a problem now. I cannot drop my publisher and publication because i was uninstalled the remote distibutor before i disable al lthe publication. Now the remote distibutor no longer exist.
Can another one help me? Urgent!!I don't know of any way to remove replication using the GUI tools in the situation you've described, but it can be done fairly easily using Transact SQL stored procedure calls. Check out sp_droppublication (http://msdn.microsoft.com/library/en-us/tsqlref/ts_sp_repl2_617y.asp) and pay special attention to the @.ignore_distributor parameter. Microsoft normlly recommends that you use this only with the help of their PSS group, but your data may not be worth $750 to open a support incident with them, so you may choose to "go it alone" instead of calling them for help.

-PatP

Publisher become subcriber to other publication.

Hi,

I just want to know, is it possible to do this ?

If yes, how to do it ?

Thanks.

Yes, it's called republishing and common for merge publications. Please search Books Online for more information.|||

Thanks Greg Y.

Do you have any other reference/manual/step by step example ?

p/s: I'm using SQL server 2000.

|||

See SQL Server 2005 BOL article: Republishing Data

http://msdn2.microsoft.com/en-us/library/ms152553.aspx

|||Please note that if the same articles are involved, the root publisher (top of the replication chain) has to be setup before the republisher is setup.

Saturday, February 25, 2012

Publication w/o logreader agent. Is it possible?

Hi,
Is it possible to create a publication without creating a logreader agent at
the same time? I'm on MS SQL Server 2000 SP3a.
-- Many thanks, Oskar
Oskar - if you are talking about transactional replication, this is an
integral part of the functioning. I'm interested in why would you like to
avoid the logreader agent?
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Yes, transactional is what I am talking about. I am interested in this
because I want to have development databases published but I do not want to
have any real replication going on there. This is needed because we must have
identical "change management" in development and production environments.
Looks like I have partly solved this problem by making each development
server a publisher and a distributor, and regenerating the publication from a
script. I even could do without the snapshot agent, but getting rid of the
logreader seems to be tricky, if not impossible.
-- Thanks, Oskar
"Paul Ibison" wrote:

> Oskar - if you are talking about transactional replication, this is an
> integral part of the functioning. I'm interested in why would you like to
> avoid the logreader agent?
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
|||Oskar,
don't know if this helps, but until the snapshot has run, the log reader
isn't moving any commands to the distribution database. To prevent it
parsing the transaction log you could simply stop it.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||That's exactly what I did. I just don't like to stop it manually everytime
the development database gets refreshed - its job name and id changes at
every such refreshing.
-- Oskar
"Paul Ibison" wrote:

> Oskar,
> don't know if this helps, but until the snapshot has run, the log reader
> isn't moving any commands to the distribution database. To prevent it
> parsing the transaction log you could simply stop it.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
>
|||I'd add a piece of code at the end of the script which stops and disables
the job - that way you don't need to worry about it afterwards.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

Publication takes record off subscriber

When I synch my subscriber back to my maste. A record I created on the
subscriber is now on the master but it is not also on the subscriber
like it should be. Any ideas? Everything seems to be in order.
Never mind. Those above me decided to add filters without telling me.
Thanks for taking the time to read this.
On Thu, 28 Apr 2005 16:09:14 -0600, Shane Lim <gslim@.blizzardice.com>
wrote:

>When I synch my subscriber back to my maste. A record I created on the
>subscriber is now on the master but it is not also on the subscriber
>like it should be. Any ideas? Everything seems to be in order.

publication status

Here is what i get under sp_helpmergepublication :
status : 1
retention : 14
sync_mode : 0
allow_push : 1
allow_pull : 1
allow_anonymous : 1 <--
centralized_conflicts : 1
prority : 100.0
snapshot_ready : 0
publication_type : 0
pubid : (some value)
snapshot_jobid : (some value)
enabled_for_internet : 0
dynamic_filters : 0
has_subscription : 1
(...)
conflict_retention : 14
keep_partition_changes : 0
allow_subscription_copy : 0
allow_synctoalternate : 0
validate_subscriber_info : NULL
backward_comp_level : 40
publish_to_activeddirectory : 0
max_concurrent_merge : 0
max_concurrent_dynamic_snapshots : 0
"Hilary Cotter" wrote:
[vbcol=seagreen]
> If your publication is configured for anonymous subscribers the snapshot
> should always be ready and you should not have this problem.
> the
Is your subscriber anonymous or named?
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
"Nevrose" <Nevrose@.discussions.microsoft.com> wrote in message
news:F9C8C56F-6CBF-47B0-87E0-E2DDC9B3520D@.microsoft.com...[vbcol=seagreen]
> Here is what i get under sp_helpmergepublication :
> status : 1
> retention : 14
> sync_mode : 0
> allow_push : 1
> allow_pull : 1
> allow_anonymous : 1 <--
> centralized_conflicts : 1
> prority : 100.0
> snapshot_ready : 0
> publication_type : 0
> pubid : (some value)
> snapshot_jobid : (some value)
> enabled_for_internet : 0
> dynamic_filters : 0
> has_subscription : 1
> (...)
> conflict_retention : 14
> keep_partition_changes : 0
> allow_subscription_copy : 0
> allow_synctoalternate : 0
> validate_subscriber_info : NULL
> backward_comp_level : 40
> publish_to_activeddirectory : 0
> max_concurrent_merge : 0
> max_concurrent_dynamic_snapshots : 0
>
> "Hilary Cotter" wrote:
obtain[vbcol=seagreen]
|||Anonymous.
I have 2 suscribers.
Here is what i've got from sp_helpmergepullsubscription for both of them :
status 0 = All jobs are waiting to start
subscriber_type 3 = Anonymous
subscription_type 2 = Anonymous
priority 0.0
sync_type 1 = Automatic
enabled_for_synmgr 1
last_updated NULL
publisher_login NULL
publisher_password (nothing here)
publisher_security_mode 1 = Windows Authentication
distributor_login sa
distributor_password (nothing here)
distributor_security_mode 1 = Windows Authentication
use_ftp 0 = Subscription is not using FTP
offload_agent 0 = The agent cannot be remotely activated
use_interactive_resolver 0 = The interactive resolver is not used
dynamic_snapshot_location NULL
last_sync_status NULL (?, should be int)
last_sync_summary NULL
"Hilary Cotter" wrote:

> Is your subscriber anonymous or named?
> --
> 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
> "Nevrose" <Nevrose@.discussions.microsoft.com> wrote in message
> news:F9C8C56F-6CBF-47B0-87E0-E2DDC9B3520D@.microsoft.com...
> obtain
>
>

Publication script error

Hello,
I am creating Publication through sql script. I have created Publication on
my machine using wizard and after that I created the script for the
publication. When I am running this script on another sql server it is giving
me an error saying Distributor not configured properly. What I need to do to
remove this error? Can this problem be solved by running some sql script?
Becoz I am creating all this through Installshield. So I need the script of
this. Please Help...
Sounds like replication is not installed on this server. Go to tools,
replication, enable replication and follow the prompts accepting the
defaults.
"Subin" <Subin@.discussions.microsoft.com> wrote in message
news:567DC900-D413-4769-916C-E24FF90B9A0E@.microsoft.com...
> Hello,
> I am creating Publication through sql script. I have created Publication
> on
> my machine using wizard and after that I created the script for the
> publication. When I am running this script on another sql server it is
> giving
> me an error saying Distributor not configured properly. What I need to do
> to
> remove this error? Can this problem be solved by running some sql script?
> Becoz I am creating all this through Installshield. So I need the script
> of
> this. Please Help...

publication retention to increase, how to avoid missing metadata after cleanup

I currently use 7 days for subscription expiration setting for my two merge publications, which will cause metadata to clean up very 7 days. Now I need to increase the retention period to be 14 days. How I can avoid missing metadata after cleanup? Microsoft ms151188 (http://msdn2.microsoft.com/en-us/library/ms151188.aspx) warns that publisher may not have enough metadata, which may lead to non-convergence. I want to change this setting without causing any data loss.

Thanks much,

I don't think changing retention setting will cause metadata loss. Of course if you want to be 100% sure, quiesce the system and then change the setting.

Publication Problem

Hello,
I want to Create Publication with the Wizard but i always have a great
problem: After i click on okay on the Specify Snapshot Folder i always get
the following error:
"SQL Server Enterprise Manager could not retrieve information about the
Distributor of the database. Error 1038: Cannot use empty object or column
names. Use a single space if necessary."
And when i click on okay and the "Choose Publication Database" screen
appears i cannnot choose any database because in there do not appear any
databases.
What went wrong here?
Can anybody please help me here?
regards
patrick
PS: When i want to create a new Table for a Database a similar error occurs:
An unexpected error happened during this operation.
[Microsoft SQL-DMO (ODBC SQLState: 42000) - Cannot use empty object or
column names. Use a single space if necessary.
Maybe this could help to explain me what went wrong in my Enterprise Manager
that the Publication does not work correctly?
Hello,
I installed the Microsoft SQL Server 2000 on my machine once more and
fortunately the Publicaten worked. I did it like it is quoted in your posted
doc-file and on this
<a
href=http://msdn.microsoft.com/SQL/SQLCE/default.aspx?pull=/msdnmag/issues/03/09/datapoints/default.aspx> ReplicationExample
site, because i want to go through the sample of this site.
But it were to good to be true if all would be work, when i deploy the
sample application from this site on the Emulator and presses the
Synch-Button of the application, the following error occurs in a message box
on the display:
Error #1 of 1
Error Code: -2147012867
Message: A request to send data to the computer running IIS has failed. For
more information, see HRESULT.[,,,,]
Minor Err.: 28037
Source: Microsoft SQL Server 2000 Windows CE Edition.
Do know what went wrong here or do i have forgotten anything during the
Create Virtual Directory Wizard or the Publication Wizard or anything else?
Hopefully you are willing to help me again, because i do not simply look
through it.
regards
patrick
PS: I did all as i quoted it in the previous posting and once more my IIS,
SQL Server 2000 and VS.NET are all on the same machine.

Publication not enabled to use an independent agent

I've created a snapshot replication between 2 databases on 2 different
servers to run once a day. The snapshot has worked but when the
distribution job runs it fails within a few seconds. I've looked at the
job history and the following error message is recorded:
Publication 'EmailDB' is not enabled to use an independent agent. The
step failed.
I think this may be because I've defined the publication so that
anonymous pull subscriptions are not allowed. If not does anyone know
what the problem could be. If it is how do I alter the publication so
that they are allowed - the option doesn't appear to be changeable with
the publication properties window in EM.
TIA
Laurence Breeze
drop your subscriptions and try this
sp_changepublication 'pubs4','independent_agent','true'
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
"Laurence Breeze" <laurence_breeze@.yahoo.co.uk> wrote in message
news:4289AD77.5070305@.yahoo.co.uk...
> I've created a snapshot replication between 2 databases on 2 different
> servers to run once a day. The snapshot has worked but when the
> distribution job runs it fails within a few seconds. I've looked at the
> job history and the following error message is recorded:
> Publication 'EmailDB' is not enabled to use an independent agent. The
> step failed.
> I think this may be because I've defined the publication so that
> anonymous pull subscriptions are not allowed. If not does anyone know
> what the problem could be. If it is how do I alter the publication so
> that they are allowed - the option doesn't appear to be changeable with
> the publication properties window in EM.
> TIA
> Laurence Breeze
>

publication include new tables created automatically?

Hi All,
I have a merge replication on a SQL 2000 database to a remote site.
I have selected "publish all" in publication properties. Now if I a new
table is created, does it automatically runs the snapshot agent and include
that table in to the table schema?
Thanks in advance for the answer... :-)
Maani...
Using sp_addmergearticle followed by running the snapshot agent and merge
agents should be enough.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .