ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Sizing a Server and Disks - SQL VM

    IT Discussion
    esxi host vmware sql server virtual machine
    11
    112
    8.0k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • DashrenderD
      Dashrender @scottalanmiller
      last edited by

      @scottalanmiller said in Sizing a Server and Disks - SQL VM:

      @dashrender said in Sizing a Server and Disks - SQL VM:

      @tim_g said in Sizing a Server and Disks - SQL VM:

      @hobbit666 said in Sizing a Server and Disks - SQL VM:

      @tim_g said in Sizing a Server and Disks - SQL VM:

      We have a Hyper-V host with two tiers of storage: an all SSD RAID, and an all HDD RAID.

      WHen I set up the MS SQL server (mainly for MS Dynamics purposes, but it also serves some other critical business functions), I had to do it according to what the Dynamics consultant suggested:

      • MS SQL VM: (virtual disk (os drive letter))
        • serv-SQL.vhdx (C:)
        • serv-SQL-DATA.vhdx (D:)
        • serv-SQL-LOG.vhdx (E:)
        • serv-SQL-BACKUP.vhdx (F:)

      The D and E virtual disks are located on the SSD RAID on the physical host, the other two are on the HDD RAID.

      The stuff needing to be fast like the TempDB, Log, main DB, etc is all on SSD... while the backups and the OS are on the HDD RAID.

      I do have SSD caching for the HDD RAID, so the other stuff is actually sped up, though not 100% of the time. Most writes are anyways.

      How have you got you disks split? Is it 50/50 SSD/Spinning?

      I'm not sure what you're asking.

      But the physical Hyper-V Host simply has two physical RAIDs.

      • HOST
        • 1st RAID (which is a RAID10)
          • SSDs
        • 2nd RAID (also a RAID10)
          • HDDs

      These RAIDs are completely separate. On the HOST, the SSD RAID is the D: drive, and the HDD RAID is the E: drive. I store the virtual machine virtual disks (the .vhdx disks) on the one it needs to go on depending on IOPS requirements. For example, the database and log virtual disks of MS SQL virtual machines go on the D: drive of the HOST, and the OS and Backup .vhdx virtual disks of that virtual machine go on the E: drive of the HOST.

      What is your 😄 Drive?

      The smile drive is where you store the memes.

      /sigh - it displace the letter c followed by colon as 😄
      again /sigh.

      black3dynamiteB scottalanmillerS 2 Replies Last reply Reply Quote 0
      • black3dynamiteB
        black3dynamite @Dashrender
        last edited by

        @dashrender said in Sizing a Server and Disks - SQL VM:

        @scottalanmiller said in Sizing a Server and Disks - SQL VM:

        @dashrender said in Sizing a Server and Disks - SQL VM:

        @tim_g said in Sizing a Server and Disks - SQL VM:

        @hobbit666 said in Sizing a Server and Disks - SQL VM:

        @tim_g said in Sizing a Server and Disks - SQL VM:

        We have a Hyper-V host with two tiers of storage: an all SSD RAID, and an all HDD RAID.

        WHen I set up the MS SQL server (mainly for MS Dynamics purposes, but it also serves some other critical business functions), I had to do it according to what the Dynamics consultant suggested:

        • MS SQL VM: (virtual disk (os drive letter))
          • serv-SQL.vhdx (C:)
          • serv-SQL-DATA.vhdx (D:)
          • serv-SQL-LOG.vhdx (E:)
          • serv-SQL-BACKUP.vhdx (F:)

        The D and E virtual disks are located on the SSD RAID on the physical host, the other two are on the HDD RAID.

        The stuff needing to be fast like the TempDB, Log, main DB, etc is all on SSD... while the backups and the OS are on the HDD RAID.

        I do have SSD caching for the HDD RAID, so the other stuff is actually sped up, though not 100% of the time. Most writes are anyways.

        How have you got you disks split? Is it 50/50 SSD/Spinning?

        I'm not sure what you're asking.

        But the physical Hyper-V Host simply has two physical RAIDs.

        • HOST
          • 1st RAID (which is a RAID10)
            • SSDs
          • 2nd RAID (also a RAID10)
            • HDDs

        These RAIDs are completely separate. On the HOST, the SSD RAID is the D: drive, and the HDD RAID is the E: drive. I store the virtual machine virtual disks (the .vhdx disks) on the one it needs to go on depending on IOPS requirements. For example, the database and log virtual disks of MS SQL virtual machines go on the D: drive of the HOST, and the OS and Backup .vhdx virtual disks of that virtual machine go on the E: drive of the HOST.

        What is your 😄 Drive?

        The smile drive is where you store the memes.

        /sigh - it displace the letter c followed by colon as 😄
        again /sigh.

        I got caught with that too. I need to remember to use C:\ instead.

        1 Reply Last reply Reply Quote 0
        • scottalanmillerS
          scottalanmiller @Dashrender
          last edited by

          @dashrender said in Sizing a Server and Disks - SQL VM:

          @scottalanmiller said in Sizing a Server and Disks - SQL VM:

          @dashrender said in Sizing a Server and Disks - SQL VM:

          @tim_g said in Sizing a Server and Disks - SQL VM:

          @hobbit666 said in Sizing a Server and Disks - SQL VM:

          @tim_g said in Sizing a Server and Disks - SQL VM:

          We have a Hyper-V host with two tiers of storage: an all SSD RAID, and an all HDD RAID.

          WHen I set up the MS SQL server (mainly for MS Dynamics purposes, but it also serves some other critical business functions), I had to do it according to what the Dynamics consultant suggested:

          • MS SQL VM: (virtual disk (os drive letter))
            • serv-SQL.vhdx (C:)
            • serv-SQL-DATA.vhdx (D:)
            • serv-SQL-LOG.vhdx (E:)
            • serv-SQL-BACKUP.vhdx (F:)

          The D and E virtual disks are located on the SSD RAID on the physical host, the other two are on the HDD RAID.

          The stuff needing to be fast like the TempDB, Log, main DB, etc is all on SSD... while the backups and the OS are on the HDD RAID.

          I do have SSD caching for the HDD RAID, so the other stuff is actually sped up, though not 100% of the time. Most writes are anyways.

          How have you got you disks split? Is it 50/50 SSD/Spinning?

          I'm not sure what you're asking.

          But the physical Hyper-V Host simply has two physical RAIDs.

          • HOST
            • 1st RAID (which is a RAID10)
              • SSDs
            • 2nd RAID (also a RAID10)
              • HDDs

          These RAIDs are completely separate. On the HOST, the SSD RAID is the D: drive, and the HDD RAID is the E: drive. I store the virtual machine virtual disks (the .vhdx disks) on the one it needs to go on depending on IOPS requirements. For example, the database and log virtual disks of MS SQL virtual machines go on the D: drive of the HOST, and the OS and Backup .vhdx virtual disks of that virtual machine go on the E: drive of the HOST.

          What is your 😄 Drive?

          The smile drive is where you store the memes.

          /sigh - it displace the letter c followed by colon as 😄
          again /sigh.

          Just don't displace your colon!

          ObsolesceO 1 Reply Last reply Reply Quote 0
          • ObsolesceO
            Obsolesce @scottalanmiller
            last edited by

            @scottalanmiller said in Sizing a Server and Disks - SQL VM:

            @dashrender said in Sizing a Server and Disks - SQL VM:

            @scottalanmiller said in Sizing a Server and Disks - SQL VM:

            @dashrender said in Sizing a Server and Disks - SQL VM:

            @tim_g said in Sizing a Server and Disks - SQL VM:

            @hobbit666 said in Sizing a Server and Disks - SQL VM:

            @tim_g said in Sizing a Server and Disks - SQL VM:

            We have a Hyper-V host with two tiers of storage: an all SSD RAID, and an all HDD RAID.

            WHen I set up the MS SQL server (mainly for MS Dynamics purposes, but it also serves some other critical business functions), I had to do it according to what the Dynamics consultant suggested:

            • MS SQL VM: (virtual disk (os drive letter))
              • serv-SQL.vhdx (C:)
              • serv-SQL-DATA.vhdx (D:)
              • serv-SQL-LOG.vhdx (E:)
              • serv-SQL-BACKUP.vhdx (F:)

            The D and E virtual disks are located on the SSD RAID on the physical host, the other two are on the HDD RAID.

            The stuff needing to be fast like the TempDB, Log, main DB, etc is all on SSD... while the backups and the OS are on the HDD RAID.

            I do have SSD caching for the HDD RAID, so the other stuff is actually sped up, though not 100% of the time. Most writes are anyways.

            How have you got you disks split? Is it 50/50 SSD/Spinning?

            I'm not sure what you're asking.

            But the physical Hyper-V Host simply has two physical RAIDs.

            • HOST
              • 1st RAID (which is a RAID10)
                • SSDs
              • 2nd RAID (also a RAID10)
                • HDDs

            These RAIDs are completely separate. On the HOST, the SSD RAID is the D: drive, and the HDD RAID is the E: drive. I store the virtual machine virtual disks (the .vhdx disks) on the one it needs to go on depending on IOPS requirements. For example, the database and log virtual disks of MS SQL virtual machines go on the D: drive of the HOST, and the OS and Backup .vhdx virtual disks of that virtual machine go on the E: drive of the HOST.

            What is your 😄 Drive?

            The smile drive is where you store the memes.

            /sigh - it displace the letter c followed by colon as 😄
            again /sigh.

            Just don't displace your colon!

            Keep it clean!

            1 Reply Last reply Reply Quote 0
            • hobbit666H
              hobbit666
              last edited by

              Running a 7 day DPACK (now liveoptics)

              scottalanmillerS 1 Reply Last reply Reply Quote 1
              • scottalanmillerS
                scottalanmiller @hobbit666
                last edited by

                @hobbit666 said in Sizing a Server and Disks - SQL VM:

                Running a 7 day DPACK (now liveoptics)

                Have fun, see you next week 🙂

                1 Reply Last reply Reply Quote 1
                • hobbit666H
                  hobbit666
                  last edited by

                  Had to stop the DPACK and re-run.

                  Hopefully results tomorrow afternoon 🙂

                  1 Reply Last reply Reply Quote 0
                  • hobbit666H
                    hobbit666
                    last edited by hobbit666

                    OK so are you ready for Slide show city 🙂 here comes the graphs 🙂

                    Basic Layout of the 3-2-1
                    0_1519119149915_Layout-Info.png

                    1 Reply Last reply Reply Quote 0
                    • hobbit666H
                      hobbit666
                      last edited by

                      Page1
                      0_1519116184121_ExecutiveSummary.png

                      1 Reply Last reply Reply Quote 0
                      • hobbit666H
                        hobbit666
                        last edited by

                        Page2
                        0_1519116225747_ExecutiveStorageSummary.png

                        1 Reply Last reply Reply Quote 0
                        • hobbit666H
                          hobbit666
                          last edited by

                          Page9
                          0_1519116271774_VMFS-SQL.png

                          1 Reply Last reply Reply Quote 0
                          • hobbit666H
                            hobbit666
                            last edited by

                            Page10
                            0_1519116560510_VMFS3.png

                            1 Reply Last reply Reply Quote 0
                            • hobbit666H
                              hobbit666
                              last edited by

                              Page11
                              0_1519116579573_VMFS5.png

                              1 Reply Last reply Reply Quote 0
                              • hobbit666H
                                hobbit666
                                last edited by

                                Page13-15
                                0_1519116621487_ServerRecord.png
                                0_1519116628716_DiskRecord.png
                                0_1519116636945_ClusterDisks.png

                                1 Reply Last reply Reply Quote 0
                                • hobbit666H
                                  hobbit666
                                  last edited by

                                  Page5 - ESXi Host 3 - This one only runs the SQL VM
                                  0_1519116697390_ESXi4.png

                                  1 Reply Last reply Reply Quote 0
                                  • hobbit666H
                                    hobbit666
                                    last edited by

                                    Page6 - ESXi Host 2
                                    0_1519116732604_ESXi2.png

                                    1 Reply Last reply Reply Quote 0
                                    • hobbit666H
                                      hobbit666
                                      last edited by

                                      Page7 - ESXI host 1
                                      0_1519116966575_ESXi1.png

                                      1 Reply Last reply Reply Quote 0
                                      • hobbit666H
                                        hobbit666
                                        last edited by

                                        General Info

                                        ESXi1 – Dell R710 – VMWare ESXi5.0.0
                                        2x Intel Xeon E5607 (4 core, no Hyperthreading)
                                        64GB RAM
                                        1TB Local

                                        ESXi2 – R610 - VMWare ESXi5.0.0
                                        2x Intel Xeon E5645 (6 core, 24 Threads)
                                        64GB RAM
                                        NO Local

                                        ESXi4 – R620 - VMWare ESXi5.0.0
                                        2x Intel Xeon E5-2640 (6 core, 24 Threads)
                                        64GB RAM
                                        NO Local

                                        1 Reply Last reply Reply Quote 0
                                        • 1
                                        • 2
                                        • 3
                                        • 4
                                        • 5
                                        • 6
                                        • 2 / 6
                                        • First post
                                          Last post