Bi directional Transactional replication with only selected fields

  • Hello Every one,

    Just caught up with some replication question again.

    1. Is it possible to publish only selected fields in a table with transactional replication?

    2. Is there any possibility to do data type conversion during publication to match up with the subscriber data type?

    Ta

  • sqllearner-339367 (10/28/2009)


    Hello Every one,

    Just caught up with some replication question again.

    1. Is it possible to publish only selected fields in a table with transactional replication?

    2. Is there any possibility to do data type conversion during publication to match up with the subscriber data type?

    Ta

    1. Yes, you can select a specific list of columns when you create the publication.

    2. I'm not sure but why wouldn't you make the tables identical on both subscriber and publisher. You seriously run the risk for problems if you don't.

    David

    @SQLTentmaker

    “He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot

  • I guess you cannot have transformations while publishing. Can't remember where did I read it.


    Bru Medishetty

    Blog -- LearnSQLWithBru

    Join on Facebook Page Facebook.comLearnSQLWithBru

    Twitter -- BruMedishetty

  • David/ Bru,

    Data model between Live and Development are different. This is the reason , I was asking whether any transformation is possible during publication. I will have to come up with some alternative now.

    Perhaps best way is to have Old data base copy on your development server and use transactional replication to Sync it. Once there are in sync use stored procedure (trnsaformation) to Load data to development server and update the copy database with result which automatically updates the live server.

    What are your suggestions?

  • David Benoit (10/28/2009)


    1. Yes, you can select a specific list of columns when you create the publication.

    2. I'm not sure but why wouldn't you make the tables identical on both subscriber and publisher. You seriously run the risk for problems if you don't.

    We omitted fields in one scenario because we did not want credit card information to be replicated to the reporting database.

  • I am not entirely sure if you can do transformations but you can write custom procedures to handle the pre and post changes to the subscriber

    remembering from memory, in sql 2000 you had the data transformations -> allow data transformations option, which allowed you to use DTS to transform data before distributing it to a subscriber, so I would imagine there is a SQL 2005 equivalent.

    --------------------------------------------------------------------------------------
    [highlight]Recommended Articles on How to help us help you and[/highlight]
    [highlight]solve commonly asked questions[/highlight]

    Forum Etiquette: How to post data/code on a forum to get the best help by Jeff Moden[/url]
    Managing Transaction Logs by Gail Shaw[/url]
    How to post Performance problems by Gail Shaw[/url]
    Help, my database is corrupt. Now what? by Gail Shaw[/url]

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply