This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(51.2, 55.00000000000001%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
One of the database is having performance issue. We have rebuild index but performance is still an issue. Please advice what other solutions can be used to increase performance.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(211.20000000000002, 78%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECZ%3C/text%3E%3C/svg%3E)
Hi,
What is the specific manifestation of the performance issue in your database? Whether there is pressure on memory, CPU, and I/O, and whether the blocking occurs.
@ Criszhan-msft- Thank you for quick response. The problem seems to be that we can extract the data very quickly on the Server A but it is very slow when we use a linked server from Server B.
Hi, do you mean the linked server from server B connect to server A. So the query through the linked server is slow, did this happen suddenly?
@Cris Zhan-MSFT , so when the query from server A when connects to server B through linked server it is very slow
Can you please show us the queries that you are using?
Please also post SELECT @@version from both servers.
@Erland Sommarskog - sure I will have a better understanding tomorrow and share the query with you
One of the database is having performance issue
Databases as it don't have performance issues, but may queries running against it. So you have to identify expensive/long runing queries.
See for example https://www.sqlshack.com/how-to-identify-slow-running-queries-in-sql-server/
Before we can start talk about solutions to increase performance, you need to track down more precisely where the problem is. If you are on SQL 2016 or later, Query Store is a great tool to track down slow queries.
@Erland Sommarskog , yes plan on using query store to track down slow queries. Will there be any performance issue if query store is enabled in SQL 2016.
Normally, Query Stored is said to result in an overhead of 2-3%. But if you an application that submits many unparameterised queries, Query Store can really add insult to injury on a system that is always crumbling.
Then again, you need to make analysis to find out what is troubling your system. Just applying measures blindly is pointless, so you must acquire knowledge.