<div>
<div class="content wysiwyg-content">
Currently we are using SQL Server 2008 R2 and looking to go forward with Denali. <br />
<br />
We will have 25,000 users connecting to an AX environment (SQL DB and Cube) and could be up to 10,000 concurrent users.<br />
<br />
For our solution we have decided to log ship the AX database every 5-15mins and use this replicated db for all the cube and most of the reporting connections to ensure that the main server never gets overloaded or any issues come with processing the certain cubes every 5-15mins.<br />
<br />
My question is what is the best approach to get this data across to the &quot;replicated&quot; server?<br />
1. Log Shipping: <br />
&nbsp; &nbsp; &nbsp;a. Pros; easy to set up, no need to have pk on each table;<br />
&nbsp; &nbsp; &nbsp;b. Dis; User currently running reports connected to replicated db will be disconnected when the db gets log shipped every 5-15mins.<br />
2. Replication:<br />
&nbsp; &nbsp; &nbsp; a. Pro: very fast, no downtime<br />
&nbsp; &nbsp; &nbsp; b. Dis: Complicated to set up and easy to fail.<br />
3. Mirror:<br />
&nbsp; &nbsp; &nbsp; a. Pro: fast<br />
&nbsp; &nbsp; &nbsp; b. Dis: can't connect whilst being mirrored.<br />
<br />
Can anyone confirm which you would feel is the best approach with the pros and cons. From my understanding log shipping would be best however the major issue is users getting disconnected whilst running reports?<br />
<br />

</div>
</div>


Currently we are using SQL Server 2008 R2 and looking to go forward with Denali. 

We will have 25,000 users connecting to an AX environment (SQL DB and Cube) and could be up to 10,000 concurrent users.

For our solution we have decided to log ship the AX database every 5-15mins and use this replicated db for all the cube and most of the reporting connections to ensure that the main server never gets overloaded or any issues come with processing the certain cubes every 5-15mins.

My question is what is the best approach to get this data across to the "replicated" server?
1. Log Shipping: 
     a. Pros; easy to set up, no need to have pk on each table;
     b. Dis; User currently running reports connected to replicated db will be disconnected when the db gets log shipped every 5-15mins.
2. Replication:
      a. Pro: very fast, no downtime
      b. Dis: Complicated to set up and easy to fail.
3. Mirror:
      a. Pro: fast
      b. Dis: can't connect whilst being mirrored.

Can anyone confirm which you would feel is the best approach with the pros and cons. From my understanding log shipping would be best however the major issue is users getting disconnected whilst running reports?



Log Shipping vs Replication vs Mirroring

Microsoft SQL Server 2008 is a suite of relational database management system (RDBMS) products providing multi-user database access functionality.Component services include integration (SSIS), reporting (SSRS), analysis (SSAS), data quality, master data, T-SQL and performance tuning. Major improvements include the  Always On technologies and support for unstructured data types.