Post reply

A Transactional Replication Primer

  • November 3, 2006 at 10:23 am

    #175095

    Comments posted here are about the content posted at temp

    Regards,

    Cláudia Rego

    www.footballbesttips.com

  • November 20, 2006 at 3:23 am

    #672888

    Claudia, Your primer is excellent. Very informative etc. One issue which I have been trying to overcome is, I have an archive database on the subscriber receiving transactions from a publisher. Next developers make a change to the schema at the publisher. I end up having to rename my archive database on the subscriber ( as I don't want to lose this data ) and re-snapshot the updated publication to yet another archive database. I haven't yet discovered any way of overcoming this. Again excellent article and thank you. Derek

  • November 20, 2006 at 4:09 am

    #672893

    I am working on a problem of replication from Spain to UK and this article makes interesting reading...thanks go to the author

    Derek: If you want a perfect copy of the database you should try "Log-Shipping".

    Pro: perfect copy of your database is maintained on your archive server, including all schema changes + data.

    Con: the archive database must be in ReadOnly mode (but isn't that the idea of an archive anyway?)

    If you don;t want to pay for the Enterprise version of SQL2k then there is a DIY solution contained in MS Back Office Resource Kit v4.5...I have been using this to maintain a DR copy of our DB's here in the UK for over 6 months now without a glitch.

    😉

     

  • November 20, 2006 at 8:34 am

    #672980

    We are running SQL Server 2000 (sp3a) on Windows 2003 clustered. We are just starting to use Log Shipping for Disaster Recovery. Basically shipping the logs across the MAN to another building and restoring there. To be honest I inherited the Archiving solution we have in place and as such had not thought of using Log Shipping. I'll certainly give it some thought. Without going into too much detail, we have a number of activities which take place at quarter end which may complicate things. But thanks very much for the input. Well worth discussing further here with our corporate DBA. Derek

  • November 20, 2006 at 9:55 am

    #673010

    The link to how you fix the IDENTITY is not working. Eere is the correct link.

    http://www.sqlservercentral.com/columnists/crego/repl/figure22.jpg

    I would also recommend against "fixing" the IDENTITY in this maner. When you do this the table is complete rebuilt. Click the little script icon to see what it is doing. A better option would be to set it as IDENTITY NOT FOR REPLICATION and then add the schema option of 0x04 to your publications.

    Bert

  • November 20, 2006 at 1:00 pm

    #673048

    Hi Claudia,

    Great read!  I am interested in creating a replication and log shipping from the same database.  The replication will be used for reporting while log shipping is used for warm standby.  Currently we already implemented log shipping using home grown scripts.  Do you have any details on how to implement replication with log shipping running?

    Thanks.

  • November 20, 2006 at 1:00 pm

    #673047

    Hi Claudia,

    Great read!  I am interested in creating a replication and log shipping from the same database.  The replication will be used for reporting while log shipping is used for warm standby.  Currently we already implemented log shipping using home grown scripts.  Do you have any details on how to implement replication with log shipping running?

    Thanks.

  • November 20, 2006 at 2:56 pm

    #673079

    Hi,

    Great article!

    A few comments:

    1. Regarding the custom stored procedures, you can eliminate the need of them by changing the article properties, and selecting not to use sp's instead of insert/update/delete commands. This way you can skip messing up with the stored procs.

    2. The identity can certainly be used at the subscriber if you select it "Not for replication". Same thing for check constaints, triggers etc.

    Cheers,

      Meir.

  • November 23, 2006 at 7:38 am

    #673676

    I'm very happy with your feedback.

    I hope it helps who is trying to setting up this type of replication.

    About log-shipping i don't have experience on this.

    Cláudia

    Regards,

    Cláudia Rego

    www.footballbesttips.com

  • April 11, 2007 at 7:00 pm

    #699945

    new to tranactional replication.....

    If the idea is to replicate the database, why doesn't it replicat all the tables, is there a way to replicate the ones without primary keys?

  • April 12, 2007 at 3:05 pm

    #700229

    Transactional Replication requires a primary key in order to replicate etc. Other method of replicating data which would include tables without primary keys would be Log Shipping. A different topic etc. Rgds Derek

  • October 1, 2007 at 7:25 pm

    #737954

    this seems using SQL Server 2000, not 2005.


    Xiong Chen

  • October 1, 2007 at 7:26 pm

    #737955

    this seems using SQL Server 2000, not 2005.


    Xiong Chen

Viewing 13 posts - 1 through 12 (of 12 total)

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