The views and opinions expressed in this blog are those solely of the author(s) and do not necessarily reflect Microsoft’s current policy, position, or branding. For official announcements and guidance on Dynamics 365 apps and services, please visit the Microsoft Dynamics 365 Blog.
Personalized Community is here!
Quickly customize your community to find the content you seek.
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2020 Release Wave 2Discover the latest updates and new features to Dynamics 365 planned through March 2021.
Release overview guides and videos Release Plan | Preview 2020 Release Wave 2 TimelineWatch the 2020 Release Wave 1 virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
This post is in continuation to my earlier post. Please check if you missed.
Database Replication – Part I
Database Replication – Part II
Database Replication – Part III
Database Replication – Part IV
As committed in this post we will continue to cover practical approach, Next step from last post.
We will create a subscription using SQL Server Management Studio
To create the subscription
The New Subscription Wizard launches.
Setting database permissions at the Subscriber
When setting up SQL Server replication you might see an error message from the Transactional Replication Log Reader Agent which reads like the following.
Often this error message can come from the database not having a valid owner, or the SQL Server is not being able to correctly identify the owner of the database.
Often this is easiest to fix by changing the database owner by using the sp_changedbowner system stored procedure as shown below. The sa account is a reliable account to use to change the ownership of the database to.
EXEC sp_changedbowner ‘sa’
EXEC sp_changedbowner ‘sa’
Once the database ownership has been changed the log reader will probably start working right away. If it doesn’t quickly restarting the log reader should resolve the problem.
While this does require changes to the production database, there is no outage required to make these changes.
To view the synchronization status of the subscription
The current synchronization status of the subscription is displayed.
Validating the Subscription and Measuring Latency
We will use tracer tokens to verify that changes are being replicated to the Subscriber and to determine latency, the time it takes for a change made at the Publisher to appear to the Subscriber.
To insert a tracer token and view information on the token
This way we are done with Database Replication Setup.
Will come up with more topic soon.
Business Applications communities