zettelkasten/OneNoteExport/Kommunikationstechnologie/Sharepoint/Performance tests/10_SQL.md
Ralf Koop 5a108aa2b4 .
2023-08-25 23:29:11 +02:00

3.1 KiB

SQL

Mittwoch, 13. November 2019

11:27

 

http://www.informit.com/articles/article.aspx?p=2131832&seqNum=3

 

Hardware Requirements for the SQL Database Role Servers

The heaviest hitter of all the SharePoint roles is the SQL database server role. This server role houses the SharePoint databases, where nearly all content in a SharePoint environment is stored. The databases house document libraries, documents, lists, sites, site collections, and their contents. For obvious reasons, this server role is highly critical for SharePoint and requires a significant amount of hardware resources. Following are several key hardware requirements for the SQL database role:

  • Disk space: Because SharePoint content is stored in the databases, the SQL database role server requires a large amount of disk space. How much disk space depends on how much content is stored in SharePoint, but assume the worst: When document versioning is turned on, SharePoint can consume much more space than people realize, even with new features in SharePoint 2013 such as Shredded Storage.

  • Disk performance: The amount of disk I/O power required can be fairly substantial. Microsoft requires at least 0.25 input/output operations per second (IOPS) per gigabyte (GB) of storage, and recommends around 2.0 IOPS per GB for optimal performance.

  • Processor: The SQL database role works best when multiple processor cores are allocated to the database role. SQL Server is built to be multithreaded and can use whatever you give it. Today's multicore processors and virtualization platforms that provide for up to eight cores to be allocated (such as Hyper-V 2012) are the perfect fit for SharePoint.

  • Memory: Server memory requirements are also high for the database role. The same general rule of thumb applies: The more memory allocated, the better an SQL server performs. The total amount of memory recommended varies depending on how heavily utilized the server is, but it is common to have SQL servers with 24GB, 32GB, 64GB, or more.

 

Aus <http://www.informit.com/articles/article.aspx?p=2131832&seqNum=3>

 

 

https://docs.microsoft.com/de-de/sql/relational-databases/performance-monitor/monitor-cpu-usage?view=sql-server-ver15

 

Um die CPU-Nutzungsrate festzustellen, rufen Sie am besten im Systemmonitor den Leistungsindikator Prozessor: Prozessorzeit (%) auf. Dieser Leistungsindikator überwacht die Zeit, die die CPU zur Verarbeitung eines Threads benötigt, der sich nicht im Leerlauf befindet. Ein konstanter Status von 80-90 % kann darauf hinweisen, dass ein CPU-Upgrade notwendig ist oder weitere Prozessoren hinzugefügt werden müssen. Bei Multiprozessorsystemen sollte für jeden Prozessor eine separate Instanz dieses Leistungsindikators überwacht werden. Dieser Wert stellt die Summe der Prozessorzeit für einen bestimmten Prozessor dar. Um den Durchschnitt für alle Prozessoren zu ermitteln, müssen Sie dagegen den Leistungsindikator System: Gesamtprozessorzeit (%) aufrufen.

 

Aus <https://docs.microsoft.com/de-de/sql/relational-databases/performance-monitor/monitor-cpu-usage?view=sql-server-ver15>