Post reply

Database Mirroring

  • August 8, 2012 at 12:46 am

    #1522971

    Is it change endpoints from instance level?

    The below one is my real time server setups

    Principal Mirror Endpoint Port

    -------- ------- --------- -----

    Default (Server1) Default (Server1) 5022 1433

    Default (Server2) named1 (Server1) ? ?

    Default (Server3) named2 (Server1) ? ?

    Help on this...

    Thanks.

    Pradeep

  • August 8, 2012 at 12:51 am

    #1522973

    Robert, Pls find the attached one for more clarification.

    Pradeep

  • August 8, 2012 at 8:51 am

    #1523158

    You need to make sure that the port for the endpoint is not already being used. So on the same server, use a different port for each endpoint.

    Only 1 thing can listen to a port/IP.

    My blog: SQL Soldier[/url]
    SQL Server Best Practices:     SQL Server Best Practices
    Twitter: @SQLSoldier
    My book: Pro SQL Server 2008 Mirroring[/url]
    Microsoft Certified Master: SQL Server, Data Platform MVP
    Database Engineer at BlueMountain Capital Management[/url]

  • August 8, 2012 at 9:30 am

    #1523202

    Hi Pradeep,

    You may not be able to mirror 1000 databases to DR site.,

    Because,

    On a 32-bit system, database mirroring can support a maximum of about 10 databases per server instance because of the numbers of worker threads that are consumed by each database mirroring session.

    Please refer the link below:

    http://msdn.microsoft.com/en-us/library/ms366349(v=sql.90).aspx

    Thanks,

    Mohammed

  • August 8, 2012 at 10:37 pm

    #1523556

    yes robert, now i can able to mirror with different endpoint port.

    Thanks for your helping...

    Pradeep

  • August 8, 2012 at 10:39 pm

    #1523557

    Hi Mohammed,

    Yes, we are going to change 64 bit OS.

    Pradeep

  • August 8, 2012 at 10:46 pm

    #1523559

    what is the meaning for the below one

    "Timeout value for determining partner outage"

    Ex:ALTER DATABASE [AdventureWorks] SET PARTNER TIMEOUT 20;

    Pradeep

  • August 8, 2012 at 11:26 pm

    #1523564

    The timeout is mostly relevant if you have automatic failover configured. The timeout value is basically the number of seconds that a partner can fail to be contacted before it is considered disconnected.

    In reality, what really happens is that the partner databases ping each other once per second. The timeout vlaue is the number of consecutive ping failures + one more that must occur for a partner to be disconnected. So if timeout is 10 (the default) the partner will be considered disconnected after 11 consecutive ping failures. Depending on how everything is configured and which partner is disconnected, it can mean different things.

    It could result in a mirroring failover or simply changing the mirroring state to disconencted and/or synchronizing.

    My blog: SQL Soldier[/url]
    SQL Server Best Practices:     SQL Server Best Practices
    Twitter: @SQLSoldier
    My book: Pro SQL Server 2008 Mirroring[/url]
    Microsoft Certified Master: SQL Server, Data Platform MVP
    Database Engineer at BlueMountain Capital Management[/url]

Viewing 8 posts - 31 through 37 (of 37 total)

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