Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 7931013
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 3, 20262026-06-03T20:35:52+00:00 2026-06-03T20:35:52+00:00

I replicate a table from one SQL Server 2008 instance to another which already

  • 0

I replicate a table from one SQL Server 2008 instance to another which already works fine. I’d also like to set a field in the replicated table on the target instance of the SQL Servers, but I’m not quite sure whether this is allowed (even though it seems to work).

Reason behind this: Replication from server A to B, processing of rows on server B and then setting (e.g. a flag such as “processed”) when the row has been processed. This information is not available on server A and can only be set on server B.

A more cumbersome way would involve a separate table on server B which would have to keep entries of IDs in the replicated table that have already been processed, but maybe this is not necessary?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-03T20:35:54+00:00Added an answer on June 3, 2026 at 8:35 pm

    With Transactional Replication, by default the Subscribers should be treated as read-only. This is because if data has been changed at a Subscriber – whether it be inserts, updated, or deletes – it can not only cause data consistency errors, but a reinitialization could wipe the Subscriber data out as article @pre_creation_cmd is set to drop by default.

    If you’re going to be updating data at the Subscribers then I would suggest using Updatable Subscriptions for Transactional Replication, Peer to Peer Replication, or Merge Replication.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

We want to replicate data from one database to several others (on another server).
Is it possible to use SQL Server's replication service to replicate from table A
I would like to replicate the permissions from one database to another. Could that
Background information Let's say I have two database servers, both SQL Server 2008. One
Below is my query which is in Storedprocedure(SQL Server 2008) will return list of
We are using SQL 2008 Transactional replication to replicate data from our production database
I have a SQL Server 2008 many-to-many relationship table ( Assets ) with two
I have a view in a SQL Server 2008 db that simply exposes about
Let's say I've got a SQL 2008 database table with lots of records associated
I am trying to create a stored procedure in SQL Server 2008 where I

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.