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

Wednesday, March 28, 2012

Problem with job

Hi there,

Actually I'm trying to replicate a production database to a development server using merge publication. (I'm using Microsoft SQL Server 2005 - 9.00.2047.00).

When I created the publication job (automatically when creating the publication) I specified to get executed every 15 minutes, and later I created a subscription (push subscription) I specified it to execute continously. So I made some chenges on the data on the production server, and they get replicated every minute aprox. , and not in 15 min intervals as I defined before.... When I go to the server agent I can see the job for publication and It is supposed to be executing the publication every 15 min as I defined but this doesn't happen !!!

Is this a Bug ? Is there any fix ?

Thanks !

The subscription job, which you set to run continuously, is what's moving changes between publisher and subscriber. This runs/polls every 60 sec, which is why you're seeing changes replicated every minute. THis behavior you're seeing is by design and expected. If you want it to replicate every 15 minutes, then change the schedule for this subscription job.

I'm not sure what a "publication" job is, maybe you're referring to the snapshot agent job? For merge replication, its typical to schedule the snapshot agent to run maybe once a day, but not every 15 minutes. You may want to change it.

So no it's not a bug

|||

I've got my problem solved !!! Thank you so much !

Greg Y wrote:

The subscription job, which you set to run continuously, is what's moving changes between publisher and subscriber. This runs/polls every 60 sec, which is why you're seeing changes replicated every minute. THis behavior you're seeing is by design and expected. If you want it to replicate every 15 minutes, then change the schedule for this subscription job.

I'm not sure what a "publication" job is, maybe you're referring to the snapshot agent job? For merge replication, its typical to schedule the snapshot agent to run maybe once a day, but not every 15 minutes. You may want to change it.

So no it's not a bug

sql

Monday, March 26, 2012

Problem with Interactive Resolver

This is my question,
I already have the whole model for a Merge publication; I have tables
intended to perform resolve interactive conflicts. This configuration is
done in the publisher in sql servr 2005 and in the clients working with sql
Express. To perform data synchronizations I use Windows synchronization.
However, when synchronizing and one of the clients reaches conflict, the
following error prompt appears:
The merge process failed to get correct information about the Interactive
Resolver component from the registry. Verify that the registry exists and
that the path is correct.
Can anybody please help me' Any help wil be welcomeHi Hector
Did you check out http://tinyurl.com/qcw6p?
John
"Hector" wrote:

> This is my question,
> I already have the whole model for a Merge publication; I have tables
> intended to perform resolve interactive conflicts. This configuration is
> done in the publisher in sql servr 2005 and in the clients working with s
ql
> Express. To perform data synchronizations I use Windows synchronization.
> However, when synchronizing and one of the clients reaches conflict, the
> following error prompt appears:
> The merge process failed to get correct information about the Interactive
> Resolver component from the registry. Verify that the registry exists and
> that the path is correct.
> Can anybody please help me' Any help wil be welcome
>

Problem with Interactive Resolver

This is my question,
I already have the whole model for a Merge publication; I have tables
intended to perform resolve interactive conflicts. This configuration is
done in the publisher in sql servr 2005 and in the clients working with sql
Express. To perform data synchronizations I use Windows synchronization.
However, when synchronizing and one of the clients reaches conflict, the
following error prompt appears:
The merge process failed to get correct information about the Interactive
Resolver component from the registry. Verify that the registry exists and
that the path is correct.
Can anybody please help me' Any help wil be welcomeHi Hector
Did you check out http://tinyurl.com/qcw6p?
John
"Hector" wrote:
> This is my question,
> I already have the whole model for a Merge publication; I have tables
> intended to perform resolve interactive conflicts. This configuration is
> done in the publisher in sql servr 2005 and in the clients working with sql
> Express. To perform data synchronizations I use Windows synchronization.
> However, when synchronizing and one of the clients reaches conflict, the
> following error prompt appears:
> The merge process failed to get correct information about the Interactive
> Resolver component from the registry. Verify that the registry exists and
> that the path is correct.
> Can anybody please help me' Any help wil be welcome
>|||I'm having the same problem now!
Chris
18-Jul-06 09:08:01
This is my question,
I already have the whole model for a Merge publication; I have tables
intended to perform resolve interactive conflicts. This configuration is
done in the publisher in sql servr 2005 and in the clients working with sql
Express. To perform data synchronizations I use Windows synchronization.
However, when synchronizing and one of the clients reaches conflict, the
following error prompt appears:
The merge process failed to get correct information about the Interactive
Resolver component from the registry. Verify that the registry exists and
that the path is correct.
Can anybody please help me' Any help wil be welcome
EggHeadCafe.com - .NET Developer Portal of Choice
http://www.eggheadcafe.com

Friday, March 23, 2012

Problem with identity range

Hi,
I have a table that has different owner than DBO. When I include this table
in publication, SQL Server does not allow to enable automatic identity range
for this article.
Any help would be greatly appreciated.
Leila
If changing the owner of the object is an acceptable solutions, refer to
Microsoft Knowledge Base Article - 275312.
"Leila" wrote:

> Hi,
> I have a table that has different owner than DBO. When I include this table
> in publication, SQL Server does not allow to enable automatic identity range
> for this article.
> Any help would be greatly appreciated.
> Leila
>
>
|||Hi,
Unfortunately I must keep the owners intact. Isn't there any solution to
this problem?
Thanks
"Sasan Saidi" <SasanSaidi@.discussions.microsoft.com> wrote in message
news:F88A75E5-7A4B-42AB-8EFA-F7A48E3290D5@.microsoft.com...[vbcol=seagreen]
> If changing the owner of the object is an acceptable solutions, refer to
> Microsoft Knowledge Base Article - 275312.
>
> "Leila" wrote:
table[vbcol=seagreen]
range[vbcol=seagreen]
|||What exactly do you mean by saying that "SQL Server does not allow to enable
automatic identity range" ?
Do you get an error or it is just somehow not possible to select that option
of automatic identity range handling ?
If you are getting an error then I know what you are talking about and I
know what causes those problems - there are some known bugs in merge
replication, which are very significant in case of objects owned not by dbo.
I have developed fixes for some of those bugs and posted them in this
newsgroup (you can look for my posts). If you will not find them, I can
repost them again.
Regards,
Kestutis Adomavicius
Consultant
UAB "Baltic Software Solutions"
"Leila" <leilas@.hotpop.com> wrote in message
news:%234$ay$hpEHA.868@.TK2MSFTNGP10.phx.gbl...
> Hi,
> I have a table that has different owner than DBO. When I include this
table
> in publication, SQL Server does not allow to enable automatic identity
range
> for this article.
> Any help would be greatly appreciated.
> Leila
>
sql

Problem with identity range

Hi,
I have a table that has different owner than DBO. When I include this table
in publication, SQL Server does not allow to enable automatic identity range
for this article.
Any help would be greatly appreciated.
Leila
If changing the owner of the object is an acceptable solutions, refer to
Microsoft Knowledge Base Article - 275312.
"Leila" wrote:

> Hi,
> I have a table that has different owner than DBO. When I include this table
> in publication, SQL Server does not allow to enable automatic identity range
> for this article.
> Any help would be greatly appreciated.
> Leila
>
>
|||Hi,
Unfortunately I must keep the owners intact. Isn't there any solution to
this problem?
Thanks
"Sasan Saidi" <SasanSaidi@.discussions.microsoft.com> wrote in message
news:F88A75E5-7A4B-42AB-8EFA-F7A48E3290D5@.microsoft.com...[vbcol=seagreen]
> If changing the owner of the object is an acceptable solutions, refer to
> Microsoft Knowledge Base Article - 275312.
>
> "Leila" wrote:
table[vbcol=seagreen]
range[vbcol=seagreen]

Problem with identity range

Hi,
I have a table that has different owner than DBO. When I include this table
in publication, SQL Server does not allow to enable automatic identity range
for this article.
Any help would be greatly appreciated.
LeilaIf changing the owner of the object is an acceptable solutions, refer to
Microsoft Knowledge Base Article - 275312.
"Leila" wrote:
> Hi,
> I have a table that has different owner than DBO. When I include this table
> in publication, SQL Server does not allow to enable automatic identity range
> for this article.
> Any help would be greatly appreciated.
> Leila
>
>|||Hi,
Unfortunately I must keep the owners intact. Isn't there any solution to
this problem?
Thanks
"Sasan Saidi" <SasanSaidi@.discussions.microsoft.com> wrote in message
news:F88A75E5-7A4B-42AB-8EFA-F7A48E3290D5@.microsoft.com...
> If changing the owner of the object is an acceptable solutions, refer to
> Microsoft Knowledge Base Article - 275312.
>
> "Leila" wrote:
> > Hi,
> > I have a table that has different owner than DBO. When I include this
table
> > in publication, SQL Server does not allow to enable automatic identity
range
> > for this article.
> > Any help would be greatly appreciated.
> > Leila
> >
> >
> >