Post reply

Replication

  • January 21, 2014 at 11:41 pm

    #396143

    Comments posted to this topic are about the item Replication

  • January 21, 2014 at 11:41 pm

    #1682269

    Nice easy on thanks.

    Hope this helps...

    Ford Fairlane
    Rock and Roll Detective

  • January 22, 2014 at 12:23 am

    #1682278

    Nice question, thanks.

    Need an answer? No, you need a question
    My blog at https://sqlkover.com.
    MCSE Business Intelligence - Microsoft Data Platform MVP

  • January 22, 2014 at 1:25 am

    #1682282

    Forgot it, so I had to make some RnD to get it right.

    Thanks & Best Regards,
    Hany Helmy
    SQL Server Database Consultant

  • January 22, 2014 at 1:27 am

    This was removed by the editor as SPAM

  • January 22, 2014 at 1:34 am

    #1682284

    Thank you for post, Good one Steve.

    (actually, couple of days ago tried it on SIMPLE model, and was sure (to my knowledge) that it will work on this model, and was not sure for other two because I did not had any practical experience on it (and I didn't want to refer the MSDN). So I picked the 3rd choice... if the choices were more with different combinations then, for sure I would have definitely chose the wrong answer :-D)

    ww; Raghu
    --
    The first and the hardest SQL statement I have wrote- "select * from customers" - and I was happy and felt smart.

  • January 22, 2014 at 5:46 am

    #1682354

    Nice question. Thanks.

    Sujeet Singh

  • January 22, 2014 at 6:43 am

    #1682371

    Good question. I didn't think it would work with simple, but didn't check MSDN to make sure. The stuff I don't use seems to escape the memory banks faster than I would like.

    Tally Tables - Performance Personified
    String Splitting with True Performance
    Best practices on how to ask questions

  • January 22, 2014 at 7:00 am

    #1682380

    Raghavendra Mudugal (1/22/2014)

    Thank you for post, Good one Steve.

    (actually, couple of days ago tried it on SIMPLE model, and was sure (to my knowledge) that it will work on this model, and was not sure for other two because I did not had any practical experience on it (and I didn't want to refer the MSDN). So I picked the 3rd choice... if the choices were more with different combinations then, for sure I would have definitely chose the wrong answer :-D)

    Let not discount random chance! 😉

    Thanks to Steve for the question.

    [font="Verdana"]Please don't go. The drones need you. They look up to you.[/font]
    Connect to me on LinkedIn

  • January 22, 2014 at 7:19 am

    #1682387

    Thanks for the question.


    Everything is awesome!

  • January 22, 2014 at 7:25 am

    #1682393

    Hany Helmy (1/22/2014)

    Forgot it, so I had to make some RnD to get it right.

    Nice approach. That's the kind of response I like to see.

    Jason...AKA CirqueDeSQLeil
    _______________________________________________
    I have given a name to my pain...MCM SQL Server, MVP
    SQL RNNR
    Posting Performance Based Questions - Gail Shaw[/url]
    Learn Extended Events

  • January 22, 2014 at 9:35 am

    #1682487

    nice and easy..

    Thanks Steve.

  • January 22, 2014 at 10:35 am

    #1682516

    Thanks for the easy question Steve.

    Having worked a lot with all types of replication this might have been easier to answer for me that the 45% that have not found it so easy.

  • January 23, 2014 at 1:06 pm

    #1682911

    Interesting question. I thought it worked for all models, but ir's so long since I last looked at replication that I thought I might be wrong, so checked in MSDN. The page I checked was The Transaction Log, which seems to say that log records are retained until the data has been replicated only in full recovery model, which seems to me to imply that transactional replication will not work in either simple or bulk-logged model, so (thinking that MSDN was more likely to have that right than my memory) I picked that answer - the wrongest one of the three.

    Is that page wrong, or do the other recovery models have some method of delaying the discard of log records pending replication other than by setting log_reuse_wait to 6 in the affected records? Or perhaps in this question "replication works" means "snapshot replication works" (snapshot uses value 7, not value 6, to delay truncation)?

    Tom

  • January 23, 2014 at 1:22 pm

    #1682920

    L' Eomot Inversé (1/23/2014)

    Interesting question. I thought it worked for all models, but ir's so long since I last looked at replication that I thought I might be wrong, so checked in MSDN. The page I checked was The Transaction Log, which seems to say that log records are retained until the data has been replicated only in full recovery model, which seems to me to imply that transactional replication will not work in either simple or bulk-logged model, so (thinking that MSDN was more likely to have that right than my memory) I picked that answer - the wrongest one of the three.

    Is that page wrong, or do the other recovery models have some method of delaying the discard of log records pending replication other than by setting log_reuse_wait to 6 in the affected records? Or perhaps in this question "replication works" means "snapshot replication works" (snapshot uses value 7, not value 6, to delay truncation)?

    When replication is used, the log is not reused even when you are in simple recovery. Once replication has catched up, it will be available for reuse. (In full recovery, log records will not be reused until both the log backup and replication have catched up).

    Hugo Kornelis, SQL Server/Data Platform MVP (2006-2016)
    Visit my SQL Server blog: https://sqlserverfast.com/blog/
    SQL Server Execution Plan Reference: https://sqlserverfast.com/epr/

Viewing 15 posts - 1 through 15 (of 21 total)

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