<div>
I would try finding out the specific queries that are causing the issue(s) - you can get that out of the sys.dm_os_waiting_tasks dmv. &nbsp;Take a look at Paul Randal's posts on wait stats for a good idea of how to identify and go after bottlenecks:<br />
<br />
<a href="http://www.sqlskills.com/blogs/paul/wait-statistics-or-please-tell-me-where-it-hurts/" rel="ugc">http://www.sqlskills.com/b<wbr />logs/paul/<wbr />wait-stati<wbr />stics-or-p<wbr />lease-tell<wbr />-me-where-<wbr />it-hurts/</a><br />
<br />
<a href="http://sqlperformance.com/2014/06/io-subsystem/knee-jerk-waits-pageiolatch-sh" rel="ugc">http://sqlperformance.com/<wbr />2014/06/io<wbr />-subsystem<wbr />/knee-jerk<wbr />-waits-pag<wbr />eiolatch-s<wbr />h</a><br />
<br />
The general jist of it is you want to reduce the amount of pages that need to be in memory to perform any given activity, as SQL Server only performs modifications/reads against pages from memory, which means they must be read from disk into memory before they can be modified/read. &nbsp;So disk bottlenecks and/or insufficient or inappropriate use of the memory allocated to the sqlservr process could be the culprits. &nbsp;It could also be inefficient query(ies) that need to be tuned to reduce their impact on the instance.
</div>


<div>
The first and most important thing in tuning indexes is to get <b>the best clustered index on every table</b> (particularly larger and/or more frequently used tables, of course). &nbsp;Updating tables too often via nonclustered indexes leads to lots of additional locking and blocking.<br />
<br />
Determining the best clustered index requires properly analyzing existing missing index stats, index usage stats and index operational stats. &nbsp;Hint: the best clustered index is usually <b><u>not</u></b> an identity column. &nbsp;[Sure, sometimes identity is best, but it's vastly less often than what people assume.]
</div>


<div>
Yuck. <br />
<br />
Unfortunately I don't know how to help you further than <a href="https://docs.appdynamics.com/display/ADDB/PAGEIOLATCH_EX+Waits" rel="ugc">this</a>. <br />
<br />
&quot;may indicate problems with the disk subsystem&quot;<br />
<br />
I would explore a tool to check your disk/partition that your database is using for its storage.
</div>


<div>
when this problem happens focus first in the disk io subsystem, memory issues as well as storage performance.<br />
<br />
some key points to look after are:<br />
<br />
* focus on the disc &nbsp;workload instead of the spin speed.<br />
* check if the storage subsistem is being abused (overworked)<br />
* You seem to already have tuned your DB, &nbsp;check: amount\speed of disks , memory amount availability , processor speed.<br />
* Differentiate between disk issues and memory issues – , the more the memory demand the slower the incoming data<br />
<br />
for more information and testing you can check this article:<br />
<a href="http://www.sqlserver-dba.com/2012/12/sql-server-pageiolatch_ex-and-how-to-reduce-it-.html" rel="ugc">http://www.sqlserver-dba.com/2012/12/sql-server-pageiolatch_ex-and-how-to-reduce-it-.html</a>
</div>


<div>
PAGEIOLATCH_XX indicates a problem between memory and disk.<br />
<br />
This can be poorly indexed tables, resulting in to much page IO required from disk.<br />
This can be a hardware problem (bandwidth, outstanding IO queue length).<br />
<br />
From your screen shot: First go for query optimizing. Identify the queries which produce high IO.<br />
<br />
Use the default report: Top Queries by IO.
</div>


<div>
@PadawanDBA<br />
<br />
I followed the first link and ran that query which yielded this result.<br />
<br />
<a href="https://filedb.experts-exchange.com/incoming/2016/04_w15/1090605/Capture.PNG" target="_blank" title="Capture.PNG (6 KB)"><img alt="Capture.PNG" class="file-block lazyload" style="max-width: 699px;" data-src="https://filedb.experts-exchange.com/incoming/2016/04_w15/1090605/Capture.PNG" /></a><br />
For the second article i will instaal that sql sentry that is described in that article.
</div>


Capture.PNG

<div>
@ScottPletcher<br />
<br />
I'm a bit unsure about the difference between non-clustered and clustered indexes and there relation to the pageiolatch_EX. <br />
Do you have any good documentation regarding this? More specificly about when do you create one or the other?
</div>


<div>
I wouldn't necessarily say you need to install SQLSentry's full monitoring platform for it. &nbsp;That's a rather beefy application when you're troubleshooting a small issue. &nbsp;You may want to look at some more targeted tooling (that is free!). &nbsp;I'd start with:<br />
<br />
<a href="https://www.idera.com/productssolutions/freetools/statistics-aggregator-for-performance-tuning-in-sql" rel="ugc">https://www.idera.com/prod<wbr />uctssoluti<wbr />ons/freeto<wbr />ols/statis<wbr />tics-aggre<wbr />gator-for-<wbr />performanc<wbr />e-tuning-i<wbr />n-sql</a><br />
<br />
and<br />
<br />
<a href="https://www.idera.com/productssolutions/freetools/sqlcheck" rel="ugc">https://www.idera.com/prod<wbr />uctssoluti<wbr />ons/freeto<wbr />ols/sqlche<wbr />ck</a><br />
<br />
Don't get me wrong, though. &nbsp;If this is a critical system for your company, I would absolutely recommend monitoring tools similar to SQLSentry &nbsp;Performance Advisor(there are a bunch out there and SQLSentry's is one of the Top 3)
</div>


<div>
@Katherine Haines<br />
@arana<br />
<br />
Thanks for the info.<br />
In regards to the memory/ harddrive/ cpu relation there is no problem there.<br />
CPU is using around 1%<br />
Memeroy is 3 GB of the 19GB<br />
Disk doesn't seem overworked in the performance monitor.
</div>


<div>
<div class="content wysiwyg-content">
Hello,<br />
<br />
We have a service which inserts data into our database. When we run our service we noticed that it sometimes took allong time to insert our data in to the database (both insert and update queries). We investigated this and with the help of SP_WhoIsActive and the scripts from &nbsp;BrentOzar we found that we lose time because of PAGEIOLATCH_EX. <br />
When this happens the complete sql engine seems to become unresponsive. If we run a querry in the ssms at that time it will take until the hold up is released before it is able to return info.<br />
<br />
Now i'm a bit stuck on how to try and fix this. Can this be fixed?<br />
<br />
<br />
<br />
<br />
What we already tried:<br />
-Remove duplicate indexes<br />
-Cleanup unneeded indexes.<br />
-ran a query that &nbsp;to show the relation between scans, lookups, updates and seeks. <br />
<a href="https://filedb.experts-exchange.com/incoming/2016/04_w15/1090194/Capture.PNG" target="_blank" title="Capture.PNG (25 KB)"><img alt="Capture.PNG" class="file-block lazyload" style="max-width: 692px;" data-src="https://filedb.experts-exchange.com/incoming/2016/04_w15/1090194/Capture.PNG" /></a><br />
System: <br />
OS: Server 2012<br />
SQL server: standard x64 Version 12.0.2000.8<br />
<br />
<br />
Thanks in advance.
</div>
</div>


Hello,

We have a service which inserts data into our database. When we run our service we noticed that it sometimes took allong time to insert our data in to the database (both insert and update queries). We investigated this and with the help of SP_WhoIsActive and the scripts from  BrentOzar we found that we lose time because of PAGEIOLATCH_EX. 
When this happens the complete sql engine seems to become unresponsive. If we run a querry in the ssms at that time it will take until the hold up is released before it is able to return info.

Now i'm a bit stuck on how to try and fix this. Can this be fixed?




What we already tried:
-Remove duplicate indexes
-Cleanup unneeded indexes.
-ran a query that  to show the relation between scans, lookups, updates and seeks. 


System: 
OS: Server 2012
SQL server: standard x64 Version 12.0.2000.8


Thanks in advance.

Question regarding PAGEIOLATCH_EX

Microsoft SQL Server is a suite of relational database management system (RDBMS) products providing multi-user database access functionality.SQL Server is available in multiple versions, typically identified by release year, and versions are subdivided into editions to distinguish between product functionality. Component services include integration (SSIS), reporting (SSRS), analysis (SSAS), data quality, master data, T-SQL and performance tuning.

Microsoft SQL Server

Windows Server 2012 is the server version of Windows 8 and the successor to Windows Server 2008 R2. Windows Server 2012 is the first version of Windows Server to have no support for Itanium-based computers since Windows NT 4.0. Windows Server 2012, now in its second release (Windows Server 2012 Release 2) includes Foundation, Essentials, Standard and Datacenter, and does not support IA-32 or IA-64 processors.