How to handle - Adding Encryption to Publisher

  • I am new to replication.

    The first thing I have been asked to do is to add encryption to the usual fields in a published database.

    The environment is sql server 2000

    The publisher there are multiple subscribers and the publisher subscribes to itself.

    What I do know:

    I know encryption will change datatype and length on the table.

    I know this will break replication.

    Current status:

    I scripted the current replication

    Current approach:

    Collect ftp account and pasword (some snapshots is deployed via FTP)

    Collect article information

        exec sp_helparticle

    Drop article from every publication

       exec sp_droparticle

    Encrypt table field

       Run script to create articles

     

     

     

     

      

     

  • What kind of encryption you are doing?

     

    MohammedU
    Microsoft SQL Server MVP

  • Developers have come up with a .net algorithm that puts out

    a varchar(150) string.

     

    My approach is to add a columns:

    encryptedSSN

    encryptedpassword

    populate columns

    use sp_addMergecolumn to article

    re-initialize

Viewing 3 posts - 1 through 2 (of 2 total)

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