• durai nagarajan - Wednesday, August 16, 2017 6:35 AM

    prem.m38 - Monday, August 14, 2017 7:09 AM

    Hi Team,
    Existing setup :
     Standalone SQL Server 2014   Enterprise edition  with 512 GB RAM and 120 Cores. Total size of 48 Databases are around 11 TB.
    (SQL Server detected 4 sockets with 15 cores per socket and 30 logical processors per socket, 120 total logical processors; using 120 logical processors based on SQL Server licensing. This is an informational message; no user action is required.)
    currently batch jobs runs from morning 3 AM to 4 PM. Process flow like this.Flat files to  staging databases. Then staging to ODS databases.ODS to DDS staging .DDS staging to DDS.DDS to all datamarts like CMIS,FP,ALM,ABM,dashboards.

    We are planning to move to two node cluster with SQL server 2016 with load balancing by splitting our databases 52 into 26 each on both instances on both nodes. We are planning to split the resources between both nodes.Will we get any performance issues by doing this ?? please suggest.

    1. what is the cluster node configurations, is it same or half as existing server?.
    2.  What is the plan if one node is down, is CPU and RAM taken to consideration.

    half of existing server.yes that's true if one node is down other node may not able to perform due to resource crunch.Anyway we are planning to do a testing.