Post reply

Replication: How to replicate more than 275 columns table

  • August 26, 2009 at 9:54 pm

    #385258

    Hello All,

    I need the method of replicating a table having more than 275 columns. Can I do as given below, or is there any method ?

    One of the ways we can do is split Original_Table in to two tables that will have common columns CLM. All operations to be carried out on this two tables for every transaction on Original_Table with the common CLM.

    Let us call both tables as (1) Original_Table as Original_Table with all the columns (2) Original_Table_Additional to have additional columns, say about 50 and CLM. The data for 250 columns will go to (1) and remaining will go to (2). Further we may put trigger on (2) and update the 50 columns in (1).

    Please advise, thanks in advance.

    Regards

    Raju

  • August 27, 2009 at 2:29 pm

    #1045871

    If you have more then 255 columns if possible go for log shipping or other technique.

    For replication: normalize the tables(as you stated) and replicate both tables.

    HTH

    Vinay

    Thanx.
    Vinay

    http://rdbmsexperts.com/Blogs/
    http://vinay-thakur.spaces.live.com/
    http://twitter.com/ThakurVinay

  • August 27, 2009 at 9:20 pm

    #1046027

    Thank you very much Mr. Vinay

    Regards

    Raju

  • August 28, 2009 at 9:01 am

    #1046289

    I have to ask: Why would someone design a database with a table containing 275 columns? I can't imagine a valid business reason for doing this.

  • August 28, 2009 at 9:37 am

    #1046317

    normalization would be the way to go .... even with 275 columns still there and mirroring or log shipping is chosen over replication ...... its still a bad idea to have that many columns ...

    -------------------------------------------------
    -Amit
    Give a man a fish and he'll ask for a lemon. Teach a man to fish and he wont get paged on weekends !! :w00t: - desparately trying to fish [/size]

  • August 29, 2009 at 5:16 am

    #1046471

    Thanks Amit for the reply.

    That is the existing premise for me. I can not normalize now that needs lot of efforts due to dependencies. I need to give solution on top of the existing. Ofcorse the database ha more than 1500 tables and nearly 100 gig having lots of operations. This is the only table has such issue.

    Once more thanks for the concern expressed.

    Regards

    Raju

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

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