Log in
::
Register
::
Not logged in
Home
Tags
Articles
Editorials
Stairways
Forums
Scripts
Videos
Blogs
QotD
Books
Ask SSC
SQL Jobs
Training
Authors
About us
Contact us
Newsletters
Write for us
Recent Posts
Recent Posts
Popular Topics
Popular Topics
Home
Search
Members
Calendar
Who's On
Home
»
SQL Server 7,2000
»
Replication
»
Transactional Replication - Snapshot is not...
Transactional Replication - Snapshot is not getting applied to subscriber
Rate Topic
Display Mode
Topic Options
Author
Message
Hemant Korde
Hemant Korde
Posted Thursday, November 15, 2012 5:34 AM
Forum Newbie
Group: General Forum Members
Last Login: Tuesday, January 15, 2013 12:05 PM
Points: 6,
Visits: 132
Need Help:
I have looked everywhere but I cannot find help for this specific topic. Any help to pinpoint the problem and how to fix it will be highly appreciated:
We are running SQL Server 2005. I have created a trans replication on a single subscriber. Both servers are in the same network (no MPLS required for data transfer). When I looked at the snapshot agent, it shows sucessfully completed status. I can also see the snapshot folder. Logreader is running and shows number of articles transferred. Distributor shows it is running sfor over 9 hours since I initially created the replication. However, nothing is getting applied to the subscriber.
Can anyone gone through the same problem, list out what I need to check and how to fix this problem. I am unable to find exact answer anywhere on the internet.
Thanks.
HK
Post #1385102
David Benoit
David Benoit
Posted Thursday, November 15, 2012 7:39 AM
SSCrazy
Group: General Forum Members
Last Login: Tuesday, May 21, 2013 7:56 AM
Points: 2,063,
Visits: 3,441
In SSMS connected to the Publisher, expand Replication, Local Publications, Select the publication you are referring to and expand, right click on the subscription select "View Synchronization Status" and let me know what you see. Also right click on the publication and select "View Snapshot Agent Status" and provide that information.
Thanks.
David
@SQLTentmaker
SQL Tentmaker
“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot
Post #1385161
Hemant Korde
Hemant Korde
Posted Thursday, November 15, 2012 8:02 AM
Forum Newbie
Group: General Forum Members
Last Login: Tuesday, January 15, 2013 12:05 PM
Points: 6,
Visits: 132
Thank you for your quick response. I appreciate your help.
I looked at the Replication in question. The snapshot Agent is showing that the snapshot was generated (in 4:02 minutes). Aslo, the syncronization status is showing in progress and shoeing transactions being processed. No error anywhere, not even in Replication Monitor which shows status excellent.
Post #1385175
David Benoit
David Benoit
Posted Thursday, November 15, 2012 8:07 AM
SSCrazy
Group: General Forum Members
Last Login: Tuesday, May 21, 2013 7:56 AM
Points: 2,063,
Visits: 3,441
Ok, since you are not seeing anything on the subscriber, we need to make sure that you are indeed sending it to the correct subscriber. You will need to expand the publication and right click on the subscription and select Properties. Please verify the Subscriber is the correct server and the Subscription database is correct as well. Check the Status also and let me know what you see.
David
@SQLTentmaker
SQL Tentmaker
“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot
Post #1385178
Hemant Korde
Hemant Korde
Posted Thursday, November 15, 2012 8:19 AM
Forum Newbie
Group: General Forum Members
Last Login: Tuesday, January 15, 2013 12:05 PM
Points: 6,
Visits: 132
David, thank you so much. You solved my probelm. I did find that the publisher was sending it to the wrong subscriber. I had checked this erlier but must have missed the name, we have several subscribers with similar names. After your email, I rechecked and found the error.
Greatly appreiate it.
Hemant
Post #1385193
David Benoit
David Benoit
Posted Thursday, November 15, 2012 8:30 AM
SSCrazy
Group: General Forum Members
Last Login: Tuesday, May 21, 2013 7:56 AM
Points: 2,063,
Visits: 3,441
Great. Glad that worked. If that wasn't the issue I was going to be hitting the "stumped" button pretty quickly. :)
David
@SQLTentmaker
SQL Tentmaker
“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot
Post #1385200
Hemant Korde
Hemant Korde
Posted Thursday, November 15, 2012 8:07 PM
Forum Newbie
Group: General Forum Members
Last Login: Tuesday, January 15, 2013 12:05 PM
Points: 6,
Visits: 132
dave,
Sorry, I take that back. I was looking at the wrong subscription propertiers this morning. Meaning, the correct subscription property is showing correct publisher and subscriber. However, the syncronization is showing below message, if you can explain what that means..
The concurrent snapshot for publication 'ADT_Tables_For_100.60' is not available because it has not been fully generated or the Log Reader Agent is not running to activate it. If generation of the concurrent snapshot was interrupted, the Snapshot Agent fo[/b]
Thanks again,
Hemant
Post #1385433
« Prev Topic
|
Next Topic »
Permissions
You
cannot
post new topics.
You
cannot
post topic replies.
You
cannot
post new polls.
You
cannot
post replies to polls.
You
cannot
edit your own topics.
You
cannot
delete your own topics.
You
cannot
edit other topics.
You
cannot
delete other topics.
You
cannot
edit your own posts.
You
cannot
edit other posts.
You
cannot
delete your own posts.
You
cannot
delete other posts.
You
cannot
post events.
You
cannot
edit your own events.
You
cannot
edit other events.
You
cannot
delete your own events.
You
cannot
delete other events.
You
cannot
send private messages.
You
cannot
send emails.
You
may
read topics.
You
cannot
rate topics.
You
cannot
vote within polls.
You
cannot
upload attachments.
You
may
download attachments.
You
cannot
post HTML code.
You
cannot
edit HTML code.
You
cannot
post IFCode.
You
cannot
post JavaScript.
You
cannot
post EmotIcons.
You
cannot
post or upload images.
Copyright © 2002-2013 Simple Talk Publishing. All Rights Reserved.
Privacy Policy.
Terms of Use.
Report Abuse.