Replication triggers

Dear All,
the subscriber database contains no longer the (upd ,
ins , del) triggers of the replication.
How do i create them again , or do i need to drop the
subscription and do it all over again.
Please feedback urgently
Thanks in Advance
Dalia,
you should be able to script them out by creating a seaparate (fake)
subscription, and then apply them to the subscriber. I'd be a little
concerned that other details may be missing though and be tempted to
reinitialize. Also, I suspect that the excahnge type value is incorrect
which has caused this issue.
HTH,
Paul Ibison
|||I urge you to re-initialize your merge subscription(s), rerun your snapshot, and deploy it by rerunning your merge agent.
sql

Replication Subscription Error

Hi,
I tried setting a server up as the publisher, distributor and subscriber.
When I tried to create either a push or pull subscription I got the following
message:
Error 14053: Cannot load the DLL replincrementlsn extended procedure, or one
of the DLLs it references. Reason: 126(error not found).
The subscription could not be updated at this time.
The subscription could not be created.
SQL Server Enterprise Manager could not create a pull subscription to
publication XXXX
Error 14053: Cannot load the DLL replincrementlsn extended procedure, or one
of the DLLs it references. Reason: 126(error not found).
The subscription could not be updated at this time.
The subscription could not be created.
Has anyone seen this before?
Server running SQL 2000 on Windows 2000 Server
Thanks
Something is not installed correctly. Reapply your latest service pack.
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
"DavidW" <DavidW@.discussions.microsoft.com> wrote in message
news:895B9996-9D97-4CAA-84F2-FF314F842E6F@.microsoft.com...
> Hi,
> I tried setting a server up as the publisher, distributor and subscriber.
> When I tried to create either a push or pull subscription I got the
> following
> message:
> Error 14053: Cannot load the DLL replincrementlsn extended procedure, or
> one
> of the DLLs it references. Reason: 126(error not found).
> The subscription could not be updated at this time.
> The subscription could not be created.
> SQL Server Enterprise Manager could not create a pull subscription to
> publication XXXX
> Error 14053: Cannot load the DLL replincrementlsn extended procedure, or
> one
> of the DLLs it references. Reason: 126(error not found).
> The subscription could not be updated at this time.
> The subscription could not be created.
> Has anyone seen this before?
> Server running SQL 2000 on Windows 2000 Server
> Thanks
>
|||Thank you Hilary, that has resolved the problem!
"Hilary Cotter" wrote:

> Something is not installed correctly. Reapply your latest service pack.
> --
> 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
> "DavidW" <DavidW@.discussions.microsoft.com> wrote in message
> news:895B9996-9D97-4CAA-84F2-FF314F842E6F@.microsoft.com...
>
>

Replication subscriber views, locks and blocks.

Quick question, do views on the subscription server create locking and
blocking issues?
I have 2 servers set-up with transactional replication. We have scheduled
reports running on the subscribing server, most of those reports using views.
The views seem to create performance, locking and blocking issues.
Thank you very much in advance.
Message posted via http://www.droptable.com
Yes they can. You might want to consider using indexed views depending on
your version and edition of SQL Server.
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
"Frank N via droptable.com" <u10790@.uwe> wrote in message
news:5a40019273826@.uwe...
> Quick question, do views on the subscription server create locking and
> blocking issues?
> I have 2 servers set-up with transactional replication. We have scheduled
> reports running on the subscribing server, most of those reports using
> views.
> The views seem to create performance, locking and blocking issues.
> Thank you very much in advance.
> --
> Message posted via http://www.droptable.com
|||A (non-dirty) read of data takes out a shared lock and this is not peculiar
to views. If these views are used for reporting purposes, you might want to
have a replica to be used for reporting eg using transactional replication,
or database mirroring with database snapshots.
Alternatively you could allow dirty reads (NOLOCK) on the tables in
question - depends on the business constraints.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||So if we place (nolock) hints on all the tables in all the views that should
eliminate the locking?
Paul Ibison wrote:
>A (non-dirty) read of data takes out a shared lock and this is not peculiar
>to views. If these views are used for reporting purposes, you might want to
>have a replica to be used for reporting eg using transactional replication,
>or database mirroring with database snapshots.
>Alternatively you could allow dirty reads (NOLOCK) on the tables in
>question - depends on the business constraints.
>Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
Message posted via http://www.droptable.com
|||Yes - or more easily set the transaction isolation-level to read
uncommitted.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

Replication Snapshot Incorrect Parameter

After using the wizard to create a very simple snapshot. I keep receiving this message:

Replication-Replication Snapshot Subsystem: agent D700PT106-gdalcd_10-test-3 failed. The parameter is incorrect. The step failed.

Anybody have any idea what this means.

I need to ask you a few questions before I can troubleshoot this further:

1) Is this SQL2000 or SQL2005?

2) Is this a clustered system?

3) Are there anything interesting in the SQLServerAgent log?

-Raymond

Replication service error

hello everybody
when i create the subscribers . i got error . i try both account system
account and this account ...
but same error
Subscriptions were created successfully at the following Subscribers:
BOYD
SQL Server Enterprise Manager could not start the service 'SQLSERVERAGENT'
on server 'SERVER1'.
5 - (Access is denied)
Sam,
on Server1 check the domain login used by the sqlserveragent service. Make
sure it is a local administrator and that the password is correct, then
start the service manually using control panel.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||I got the same error this morning. Could you please give me more detail on
how to check the login account.
Thanks.
Perayu
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:uBf5LtLyFHA.1252@.TK2MSFTNGP09.phx.gbl...
> Sam,
> on Server1 check the domain login used by the sqlserveragent service. Make
> sure it is a local administrator and that the password is correct, then
> start the service manually using control panel.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||OK - on server1 open up control panel, administrative tools, services. Find
the sqlserveragent service (assuming the default instance), open the
properties and make sure it uses a domain user that is a local
administrator. If you are unclear about which account has these privileges,
it's probably best to get your network admin to create an account for you.
Once selected, restart the service.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Thank you so much!
It is working now.
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:OCMwK8PyFHA.2516@.TK2MSFTNGP12.phx.gbl...
> OK - on server1 open up control panel, administrative tools, services.
> Find the sqlserveragent service (assuming the default instance), open the
> properties and make sure it uses a domain user that is a local
> administrator. If you are unclear about which account has these
> privileges, it's probably best to get your network admin to create an
> account for you. Once selected, restart the service.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
|||Hello Mr Paul
still i got same problem , if have any privalage for domain account
thanks
Sam
"Perayu" wrote:

> I got the same error this morning. Could you please give me more detail on
> how to check the login account.
> Thanks.
> Perayu
> "Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
> news:uBf5LtLyFHA.1252@.TK2MSFTNGP09.phx.gbl...
>
>
|||Sam,
does this mean that you can't start the sql server agent at all? If so, make
sure that the account you're using for the sql server agent is added to the
sysadmin role. it shoyuld be in this role if your builtin\administrators are
there and the domain account is a local admin one, but many DBAs disable
this as it is seen as a security backdoor.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

Replication Scripts Stopped Working..

I have a merge publication that I always create with a script but has now stopped working with what appears to be a complete server problem.

The actual command i am executing is a simple

sp_addpublication_snapshot

but it fails with

Msg 50000, Level 16, State 1, Procedure sp_add_jobstep_internal, Line 253

The current transaction cannot be committed and cannot support operations that write to the log file. Roll back the transaction.

Msg 3931, Level 16, State 1, Procedure sp_MSadd_repl_job_unsafe, Line 376

The current transaction cannot be committed and cannot be rolled back to a savepoint. Roll back the entire transaction.

I have tried recreating the database from scratch, renaming it, renaming the publication, even disabling the publications altogether but it makes no difference. There is nothing in the sql or event logs and I cant do any work until Ive got past it - help!

I am using SQL 2005 SP2 if that makes any difference.

Thanks

Andy

It looks like you have an uncommitted transaction hanging around. Open a query window and type:

Commit Tran

GO

It will either tell you that there are no transactions to commit or commit the uncomplted transaction. At that point, re-run your script.

Hope this helps...

Scott

Replication Scripts Stopped Working..

I have a merge publication that I always create with a script but has now stopped working with what appears to be a complete server problem.

The actual command i am executing is a simple

sp_addpublication_snapshot

but it fails with

Msg 50000, Level 16, State 1, Procedure sp_add_jobstep_internal, Line 253

The current transaction cannot be committed and cannot support operations that write to the log file. Roll back the transaction.

Msg 3931, Level 16, State 1, Procedure sp_MSadd_repl_job_unsafe, Line 376

The current transaction cannot be committed and cannot be rolled back to a savepoint. Roll back the entire transaction.

I have tried recreating the database from scratch, renaming it, renaming the publication, even disabling the publications altogether but it makes no difference. There is nothing in the sql or event logs and I cant do any work until Ive got past it - help!

I am using SQL 2005 SP2 if that makes any difference.

Thanks

Andy

It looks like you have an uncommitted transaction hanging around. Open a query window and type:

Commit Tran

GO

It will either tell you that there are no transactions to commit or commit the uncomplted transaction. At that point, re-run your script.

Hope this helps...

Scott

Replication Pull subscription problem

Iam trying to pull subscription and Iam getting same error over and over again. The error says:
****SQL Server Enterprise Merger could not create a pull subscription to publication "database name"
Error 15004: Name cannot be null *****
ThanksHi

Its because of non-existence or invalid server info on sysservers table. Please follow the instructions to fix the above problem.

exec sp_dropserver <your_local_server_name> -- subscriber

exec sp_dropserver <remote_server_name> -- publisher

exec sp_addserver <your_local_server_name>,local

exec sp_addserver <remote_server_name>

shutdown -- it is mandatory to take effect otherwise you still get the same error
go

Start the sql server with SQLSERVERAGENT

exec sp_helpserver -- it should display your local server and publisher

Then, try configure pull subscription

Cheers
Sekar|||What version does this happen in? I thought Microsoft fixed this problem a while ago.

Replication problem, update on table with varchar primary key

hi
i have a problem in the distribution of a replicated table.
The execution sequence is:
-i create a table (the primary key is varchar)
-i publish this table
-i insert a row in the table (no problem in the replication)
-i update the row (no the primary key)
-there is a problem in the replication
The problem is the varchar primary key... you know why?!?!
Tnx!
Can you post the schema of the problem table here? Also is this
transactional replication.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
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
<paolofresujazz@.libero.it> wrote in message
news:1161350093.758198.225150@.f16g2000cwb.googlegr oups.com...
> hi
> i have a problem in the distribution of a replicated table.
> The execution sequence is:
> -i create a table (the primary key is varchar)
> -i publish this table
> -i insert a row in the table (no problem in the replication)
> -i update the row (no the primary key)
> -there is a problem in the replication
> The problem is the varchar primary key... you know why?!?!
> Tnx!
>
|||Hilary Cotter ha scritto:

> Can you post the schema of the problem table here? Also is this
> transactional replication.
Yes is transaction replication.
If i create a simple table with 2 field:
id: varchar(50) (primary key)
name: varchar(50)
and update the name field of a row...
Tnx Hilary

Replication problem, update on table with varchar primary key

hi
i have a problem in the distribution of a replicated table.
The execution sequence is:
-i create a table (the primary key is varchar)
-i publish this table
-i insert a row in the table (no problem in the replication)
-i update the row (no the primary key)
-there is a problem in the replication
The problem is the varchar primary key... you know why?!?!
Tnx!Can you post the schema of the problem table here? Also is this
transactional replication.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
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
<paolofresujazz@.libero.it> wrote in message
news:1161350093.758198.225150@.f16g2000cwb.googlegroups.com...
> hi
> i have a problem in the distribution of a replicated table.
> The execution sequence is:
> -i create a table (the primary key is varchar)
> -i publish this table
> -i insert a row in the table (no problem in the replication)
> -i update the row (no the primary key)
> -there is a problem in the replication
> The problem is the varchar primary key... you know why?!?!
> Tnx!
>|||Hilary Cotter ha scritto:

> Can you post the schema of the problem table here? Also is this
> transactional replication.
Yes is transaction replication.
If i create a simple table with 2 field:
id: varchar(50) (primary key)
name: varchar(50)
and update the name field of a row...
Tnx Hilarysql

Replication problem, update on table with varchar primary key

hi
i have a problem in the distribution of a replicated table.
The execution sequence is:
-i create a table (the primary key is varchar)
-i publish this table
-i insert a row in the table (no problem in the replication)
-i update the row (no the primary key)
-there is a problem in the replication
The problem is the varchar primary key... you know why?!?!
Tnx!Can you post the schema of the problem table here? Also is this
transactional replication.
--
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
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
<paolofresujazz@.libero.it> wrote in message
news:1161350093.758198.225150@.f16g2000cwb.googlegroups.com...
> hi
> i have a problem in the distribution of a replicated table.
> The execution sequence is:
> -i create a table (the primary key is varchar)
> -i publish this table
> -i insert a row in the table (no problem in the replication)
> -i update the row (no the primary key)
> -there is a problem in the replication
> The problem is the varchar primary key... you know why?!?!
> Tnx!
>|||Hilary Cotter ha scritto:
> Can you post the schema of the problem table here? Also is this
> transactional replication.
Yes is transaction replication.
If i create a simple table with 2 field:
id: varchar(50) (primary key)
name: varchar(50)
and update the name field of a row...
Tnx Hilary

Replication problem in SQL Server 2000

Hi all SQL Server experts!

I have created replication on my two servers (production and backup servers). I used wizards to create it and then generated SQL script for deleting and creating replication. For another task I came across the command sp_removedbreplication 'dbname' and I tried to use that for removing replication more easily on the servers. It seemed to not remove everything on the production server and whenever I install replication now, either by using wizards or my generated SQL scripts I get an error icon (red circle with a black X in it) on my Replication Monitor all the way down to Publisher and the publication named with the computer name. Also this icon is on Agents and Log Reader Agents but not on the actual agent.

Something must have happened when using sp_removedbreplication 'dbname' and I can't fix it. The replication works properly but i wish to not have the error icons.

Does anyone know how the error icons can be removed?

Best,
/M

The cleanest way and supported way is to drop the distributor and recreate it from scratch. However you can also look at the following tables in distribution database and delete any rows that reference your deleted publications (but take a backup of the distribution database first, and note that manually deleting these tables is unsupported):

MSpublications

MSsubscriptions

MSarticles

|||

I have checked these tables and they don't have anything that don't exist in them.

I have also dropped everything that has to do with replication and also the distribution database to use my scripts and install replication again. The replication works fines but there are still error icons on the folders. Only on the folders though and not on the actual items, e.g. agents. I am thinking of reinstalling the SQL Server. Might it be because SQL Server has replaced the actual icons with error icons and "lost" the orignial ones?

My scripts for installing replication has always worked but it is after I have used sp_removedbreplication on the distributor/publisher that these icons occur when I install replication, including using the wizards.

Best,
/M

|||Did you try disconnecting from the distributor and reconnecting to it. Sometimes the refresh of the data can cause such misbehavior. Also try restarting the sql server.|||

When deleting subscription, it's replication job may still remain. You can find it in SQL Server Agent Jobs list (in Enterprise Manager: [DB]->Management->SQL Server Agent->Jobs).

Name of the job consists of Publisher and Subscriber names. When you re-create a subscription, probably same name is generated, and job creation fails.

Use sp_delete_job stored procedure to delete the job.

|||

Thank you very much. That solved my problem.

Best,
/M

Replication problem in SQL Server 2000

Hi all SQL Server experts!

I have created replication on my two servers (production and backup servers). I used wizards to create it and then generated SQL script for deleting and creating replication. For another task I came across the command sp_removedbreplication 'dbname' and I tried to use that for removing replication more easily on the servers. It seemed to not remove everything on the production server and whenever I install replication now, either by using wizards or my generated SQL scripts I get an error icon (red circle with a black X in it) on my Replication Monitor all the way down to Publisher and the publication named with the computer name. Also this icon is on Agents and Log Reader Agents but not on the actual agent.

Something must have happened when using sp_removedbreplication 'dbname' and I can't fix it. The replication works properly but i wish to not have the error icons.

Does anyone know how the error icons can be removed?

Best,
/M

The cleanest way and supported way is to drop the distributor and recreate it from scratch. However you can also look at the following tables in distribution database and delete any rows that reference your deleted publications (but take a backup of the distribution database first, and note that manually deleting these tables is unsupported):

MSpublications

MSsubscriptions

MSarticles

|||

I have checked these tables and they don't have anything that don't exist in them.

I have also dropped everything that has to do with replication and also the distribution database to use my scripts and install replication again. The replication works fines but there are still error icons on the folders. Only on the folders though and not on the actual items, e.g. agents. I am thinking of reinstalling the SQL Server. Might it be because SQL Server has replaced the actual icons with error icons and "lost" the orignial ones?

My scripts for installing replication has always worked but it is after I have used sp_removedbreplication on the distributor/publisher that these icons occur when I install replication, including using the wizards.

Best,
/M

|||Did you try disconnecting from the distributor and reconnecting to it. Sometimes the refresh of the data can cause such misbehavior. Also try restarting the sql server.|||

When deleting subscription, it's replication job may still remain. You can find it in SQL Server Agent Jobs list (in Enterprise Manager: [DB]->Management->SQL Server Agent->Jobs).

Name of the job consists of Publisher and Subscriber names. When you re-create a subscription, probably same name is generated, and job creation fails.

Use sp_delete_job stored procedure to delete the job.

|||

Thank you very much. That solved my problem.

Best,
/M

Replication problem "can not insert null into colum step_name in sysjobs".

When trying to create a new publication using the wizzard i get the error message

"cannot insert null into colum step_name in sysjobs".

Replication was working fine on the server before. It stopped working when i installed SP3, i removed the old replication and tried setting it up again but get the error above when creating the publication.

Any ideas would be extremely useful. I have been unable to find any details of this on the web.

Many Thanks
Ash.Are you sure the clean up was successful? What I mean is there maybe some replication setups still reside in the system tables. I would check sysjobs first to see if there are unrecognized jobs in it and go from there.|||Originally posted by joejcheng
Are you sure the clean up was successful? What I mean is there maybe some replication setups still reside in the system tables. I would check sysjobs first to see if there are unrecognized jobs in it and go from there.

Thanks for the reply joejcheng.

I've tried quite a few different things. Like you the first thing I thought was to look in sysjobs and sysjobsteps, however there isn't anything in there that looks untoward.

Like you I'm inclined to think its something that hasn't been completely removed. I'd do a reinstall but its a production server so this isn't an option.

Replication problem

I am trying to set up a pull subscription replication using SQL Server
Enterprise Manager. I get an error stating:
.....It cannot create named subscription because the publication does not
allow named pull subscription...
How do I enable the named pull subscription on the publisher?
Thanks in advance.
Hi Antonin,
You may have to enable Pull Subscription and Anonymous Subscription for the
Publication.
You may achieve this by
1. Click on Tools -> Replication -> Create and Manage Publication.
2. Expand the Published Database and select the publication name.
3. Click on Properties and Subscription
4. In the Publication Properties Dialog Box
5. Switch to Subscription Option tab
6. In this tab you will find two checkboxes under "Subscription Creation"
option,
"Allow Pull Subscription"
"Allow Anonymous Subscription"
Please tick both the check boxes to allow Pull Anonymous Subscription
for that publication.
HTH
Ashish
This posting is provided "AS IS" with no warranties, and confers no rights.
|||Hi Ashish,
Thanks for your reply. I followed your instructions and it worked OK.
However, there is Last Action on the publisher " A snapshot was not
generated because no subscription needed initialization.
Antonin
"Ashish Ruparel [MSFT]" <v-ashrup@.online.microsoft.com> wrote in message
news:TeZcQaXOEHA.1016@.cpmsftngxa10.phx.gbl...
> Hi Antonin,
> You may have to enable Pull Subscription and Anonymous Subscription for
the
> Publication.
> You may achieve this by
> 1. Click on Tools -> Replication -> Create and Manage Publication.
> 2. Expand the Published Database and select the publication name.
> 3. Click on Properties and Subscription
> 4. In the Publication Properties Dialog Box
> 5. Switch to Subscription Option tab
> 6. In this tab you will find two checkboxes under "Subscription Creation"
> option,
> "Allow Pull Subscription"
> "Allow Anonymous Subscription"
> Please tick both the check boxes to allow Pull Anonymous Subscription
> for that publication.
>
> HTH
> Ashish
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>

Replication problem

I am trying to set up a pull subscription replication using SQL Server
Enterprise Manager. I get an error stating:
....It cannot create named subscription because the publication does not
allow named pull subscription...
How do I enable the named pull subscription on the publisher?
Thanks in advance.Hi Antonin,
You may have to enable Pull Subscription and Anonymous Subscription for the
Publication.
You may achieve this by
1. Click on Tools -> Replication -> Create and Manage Publication.
2. Expand the Published Database and select the publication name.
3. Click on Properties and Subscription
4. In the Publication Properties Dialog Box
5. Switch to Subscription Option tab
6. In this tab you will find two checkboxes under "Subscription Creation"
option,
"Allow Pull Subscription"
"Allow Anonymous Subscription"
Please tick both the check boxes to allow Pull Anonymous Subscription
for that publication.
HTH
Ashish
This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Ashish,
Thanks for your reply. I followed your instructions and it worked OK.
However, there is Last Action on the publisher " A snapshot was not
generated because no subscription needed initialization.
Antonin
"Ashish Ruparel [MSFT]" <v-ashrup@.online.microsoft.com> wrote in message
news:TeZcQaXOEHA.1016@.cpmsftngxa10.phx.gbl...
> Hi Antonin,
> You may have to enable Pull Subscription and Anonymous Subscription for
the
> Publication.
> You may achieve this by
> 1. Click on Tools -> Replication -> Create and Manage Publication.
> 2. Expand the Published Database and select the publication name.
> 3. Click on Properties and Subscription
> 4. In the Publication Properties Dialog Box
> 5. Switch to Subscription Option tab
> 6. In this tab you will find two checkboxes under "Subscription Creation"
> option,
> "Allow Pull Subscription"
> "Allow Anonymous Subscription"
> Please tick both the check boxes to allow Pull Anonymous Subscription
> for that publication.
>
> HTH
> Ashish
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>

Replication problem

I am trying to set up a pull subscription replication using SQL Server
Enterprise Manager. I get an error stating:
....It cannot create named subscription because the publication does not
allow named pull subscription...
How do I enable the named pull subscription on the publisher?
Thanks in advance.Hi Antonin,
You may have to enable Pull Subscription and Anonymous Subscription for the
Publication.
You may achieve this by
1. Click on Tools -> Replication -> Create and Manage Publication.
2. Expand the Published Database and select the publication name.
3. Click on Properties and Subscription
4. In the Publication Properties Dialog Box
5. Switch to Subscription Option tab
6. In this tab you will find two checkboxes under "Subscription Creation"
option,
"Allow Pull Subscription"
"Allow Anonymous Subscription"
Please tick both the check boxes to allow Pull Anonymous Subscription
for that publication.
HTH
Ashish
This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Ashish,
Thanks for your reply. I followed your instructions and it worked OK.
However, there is Last Action on the publisher " A snapshot was not
generated because no subscription needed initialization.
Antonin
"Ashish Ruparel [MSFT]" <v-ashrup@.online.microsoft.com> wrote in message
news:TeZcQaXOEHA.1016@.cpmsftngxa10.phx.gbl...
> Hi Antonin,
> You may have to enable Pull Subscription and Anonymous Subscription for
the
> Publication.
> You may achieve this by
> 1. Click on Tools -> Replication -> Create and Manage Publication.
> 2. Expand the Published Database and select the publication name.
> 3. Click on Properties and Subscription
> 4. In the Publication Properties Dialog Box
> 5. Switch to Subscription Option tab
> 6. In this tab you will find two checkboxes under "Subscription Creation"
> option,
> "Allow Pull Subscription"
> "Allow Anonymous Subscription"
> Please tick both the check boxes to allow Pull Anonymous Subscription
> for that publication.
>
> HTH
> Ashish
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>

Replication performance measurement

Hello,

I am trying some replication sample.I create a table with thousands of records in the publisher side. as I create a subscription(the subscription database is on a remote machine),
the whole table is created on the remote database.

I wanted to measure the performence as:
1. how much time was taken in filling the whole table in the subscriber side?
2. If i insert some 10000 records on publisher side, I want to measure, how much time was taken in inserting the same records on the subscriber?

How do I measure this ? Can I use some Log reader stuff.

thanks in advance

Are you talking about transactional replication? You can use replication's monitoring tool, which displays some performance information about your syncs, you can also look at the history tables located in the distribution database, such as MSSnapshot_history, MSdistribution_history, MSlogreader_history.|||You can look at less than 1minute, if that is within your LAN, if its a WAN, measure your bandwidth,even worst bandwidth u had, it wont take up more than 5minutes. The memory allocated to your SQL server need some consideration, and another factor is depend on your db design.

Replication Performance

Hi,
I made a vb.net application that create a subscriber and subscribe it to an
article that I have created.
Yesterday when I start this application it took 2 minutes to create the
subscriber and copy the database from the publisher to the subscriber
Today I start the same application but on another laptop for another
subscriber and after 55 minutes the process was not finish. I stop the
application and I delete all the objects that was create in the replication
for that new subscriber.
Because of that, users that use another application that queries the same
database
get a connection timeout.
Do you have any idea of where should I look to find the nature of the problem?
Thanks in advance!
Can you figure out at what part of the process does it stall? Creating the
database, connecting with the publisher/subscriber, deploying the snapshot?
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
"GC" <GC@.discussions.microsoft.com> wrote in message
news:D747B6EE-9078-4FC6-8CF5-ABCB148164ED@.microsoft.com...
> Hi,
> I made a vb.net application that create a subscriber and subscribe it to
> an
> article that I have created.
> Yesterday when I start this application it took 2 minutes to create the
> subscriber and copy the database from the publisher to the subscriber
> Today I start the same application but on another laptop for another
> subscriber and after 55 minutes the process was not finish. I stop the
> application and I delete all the objects that was create in the
> replication
> for that new subscriber.
> Because of that, users that use another application that queries the same
> database
> get a connection timeout.
> Do you have any idea of where should I look to find the nature of the
> problem?
> Thanks in advance!
|||sp_who2
Find out who is generating a block.
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"GC" <GC@.discussions.microsoft.com> wrote in message
news:D747B6EE-9078-4FC6-8CF5-ABCB148164ED@.microsoft.com...
> Hi,
> I made a vb.net application that create a subscriber and subscribe it to
> an
> article that I have created.
> Yesterday when I start this application it took 2 minutes to create the
> subscriber and copy the database from the publisher to the subscriber
> Today I start the same application but on another laptop for another
> subscriber and after 55 minutes the process was not finish. I stop the
> application and I delete all the objects that was create in the
> replication
> for that new subscriber.
> Because of that, users that use another application that queries the same
> database
> get a connection timeout.
> Do you have any idea of where should I look to find the nature of the
> problem?
> Thanks in advance!
|||The Process is not stall, there still activity.
When I go on the subscription of the subscriber I can see that the
subscription is running. If I do a refresh I can see that some row are
download to the subscriber
because the amount of rows that are downloaded differ each time I do a refresh
May be my problem is the way I create my Articles.
I am a beginner in replication so I dont expect to have the best strategie
the first time.
By the way I want to thank you for all the support that you do to all of us
It is appreciated.
"Hilary Cotter" wrote:

> Can you figure out at what part of the process does it stall? Creating the
> database, connecting with the publisher/subscriber, deploying the snapshot?
> --
> 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
> "GC" <GC@.discussions.microsoft.com> wrote in message
> news:D747B6EE-9078-4FC6-8CF5-ABCB148164ED@.microsoft.com...
>
>

Replication over Internet

I want to create merge publication between Server A(publisher) and Client
B(subscriber) over Internet. However, because of the security reasons Server
A cannot be directly accessed over Internet. What is the solution for this
case?
If I seperate distrbutor from Server A and enable it to be accessed directly
over Internet and Client B subscribes through distrbutor can this be a
solution?
(VPN is not allowed)
Erkan,
as far as I understand, the merge agent will need connectivity between the
publisher and subscriber to read the MSmerge_contents and MSmerge_tombstone
tables on each box, and the absence of any connectivity will preclude this
from working. However, you could investigate republishing to achieve your
goal.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)