Troubleshoot a Slow Database in SQL Server 2008

http://www.petri.co.il/troubleshoot-slow-database-in-sql-server-2008.htm

 

Troubleshooting database slowness can be both fairly straightforward and tricky at the same time.  Most of the time the problems will present themselves to you right away and the fixes will be fairly easy too, but there are those times when the exact issue will elude you and even when you find it there is no really good solution.

 

Here, we're going to concentrate on that low hanging fruit that will get you through around 90% of your database speed issues.

First Up: Determine If it Really Is an SQL Server Issue

Let’s say that you’ve definitely determined that the issue is inside SQL Server via Troubleshooting a Slow Database Server: Is SQL Server the Cause? .  The first thing to do inside SQL Server is to see which query is causing the problems.  To do this, you need to open a query window and type the following line of code:

Select * from sys.sysprocesses order by cpu desc

This of course, depends on what your external investigation revealed.  If it revealed a CPU issue, then the above query is what you want to use.

If it revealed a disk issue, then you’ll want to change the order by clause to “order by physical_io desc ”.  And of course if it revealed memory issues, then you’ll want to change your order by clause to “order by memusage desc ”.

Each of these order clauses tells you what the most expensive queries are in terms of what you’re ordering by.  So the “order by cpu desc” clause puts the highest CPU queries at the top of the list.  These are the queries you want to concentrate on.

Let's just assume in this case that CPU is the problem.  There are a number of things inside a query that could be causing it to use high CPU, and since this article is about diagnosing, we're going to leave most of that for another time.  There really are just too many factors to get into in a single article.  Needless to say though, that once you find the offending query or queries, you can pass that information along to your DBAs or whoever deals with these issues and have them look at it.

Note: Unless you’ve got some experience fixing T-SQL coding issues, we highly suggest you don’t attempt it by yourself.

Digging Deeper

Assuming that the 3 variations of the query above come back within normal parameters, you’ll need to check some other things in that same table.  This is also the query you would start with if your initial investigation didn’t reveal anything out of whack.  So this time we’re going to check for blocking by typing this query:

Select * from sys.sysprocesses

We could order it, but this is just as easy.  This time you want to concentrate on the blocked column.  A little blocking in your database is ok, and is certainly natural as long as these blocks are coming and going, but if you’ve got a single process that’s blocking everything else, then that’s clearly going to be the problem.  It’s quite possible that you’ll end up with a blocking chain.  This is where a single process blocks another, which causes that to block something else, which causes that to block something else and so on.  So what you’re really looking for here is the lead blocker.  This is the process in the chain that is blocking something, but isn’t being blocked by anything itself.

spidblocked
98145
1050
121155
145121
155105

In the above example it seems like it’s jumping all over the place, but you can see that the only spid that is blocking another, but isn’t being blocked itself is 105.   Therefore spid 105 is the lead blocker and it’s the one that needs to be dealt with.  And again, once you find that lead blocker, someone has to do something about it, and finding out why it’s blocking takes more skill and should be handled by a DBA.  However, most of the time you can at least find out what that spid is doing by typing the following query:

DBCC InputBuffer(spid)

In the case above you’d type: DBCC InputBuffer(105)

Following the same model as above there’s one more column that can be very interesting at this high level and that’s lastwaittype .  This is a very interesting column because it can tell you what the offending query is waiting for to complete.  And unfortunately it’s not really that simple, but for our purposes here it’s adequate.  Here are some simplified explanations of some of the values that you’ll come across most often and that will help you know what’s going on.

Network_io – This is an easy one.  If you see this lastwaittype for an extended time you know you’re waiting on the network, and this is a good indication that there’s too much traffic.  The solution here is typically to call your networking team to look at what’s happening.

Cxpacket – This typically means that your process is waiting on other parallel processes to complete.  So what’s probably happening is you have a process running on more than one CPU and one thread finished before the rest.  To fix this you’d want to look at maybe limiting your parallelism either at the query or at the server-level.  It could also be a simple query tuning issue which is why it’s usually best to get a DBA involved.

SOS_SCHEDULER_YIELD – Long wait times here typically mean that you’re CPU bound.  You may not have enough CPU in your box, or more likely, you may have some queries that need tuning.  If things have been running OK, and this just started happening, then it’s way more likely that you’ve got queries hogging CPU.

IO_Completion – If you’ve got high wait times, then this could be a disk issue.  You could either not have enough disks for the operation or you could be running an array in degraded mode.  These are both easy enough to check.  Check your array and have your DBA check to see if the database files are configured correctly.

Concluding Notes

So as you can see it can be pretty straight-forward to get to the offending process inside SQL Server.  The fix is not always as straight-forward and often times takes a qualified DBA to know how to perform the necessary steps without breaking anything.

This article has been an introduction to finding SQL Server issues so you at least know where to start looking to apply fixes.

Final Note: We can’t stress enough that having performance baselines of all your processes will help you more than anything because you now have something to compare it to.  If you have no idea what the process normally looks like when it runs then how do you know when it’s out of whack?  For instance, many processes often take up a lot of CPU, and if you don’t know that, then you’re likely to be alarmed when you see them in the above queries.  So you may spend a lot of time chasing false issues.

智慧旅游解决方案利用云计算、物联网和移动互联网技术,通过便携终端设备,实现对旅游资源、经济、活动和旅游者信息的智能感知和发布。这种技术的应用旨在提升游客在旅游各个环节的体验,使他们能够轻松获取信息、规划行程、预订票务和安排食宿。智慧旅游平台为旅游管理部门、企业和游客提供服务,包括政策发布、行政管理、景区安全、游客流量统计分析、投诉反馈等。此外,平台还提供广告促销、库存信息、景点介绍、电子门票、社交互动等功能。 智慧旅游的建设规划得到了国家政策的支持,如《国家中长期科技发展规划纲要》和国务院的《关于加快发展旅游业的意见》,这些政策强调了旅游信息服务平台的建设和信息化服务的重要性。随着技术的成熟和政策环境的优化,智慧旅游的时机已经到来。 智慧旅游平台采用SaaS、PaaS和IaaS等云服务模式,提供简化的软件开发、测试和部署环境,实现资源的按需配置和快速部署。这些服务模式支持旅游企业、消费者和管理部门开发高性能、高可扩展的应用服务。平台还整合了旅游信息资源,提供了丰富的旅游产品创意平台和统一的旅游综合信息库。 智慧旅游融合应用面向游客和景区景点主管机构,提供无线城市门户、智能导游、智能门票及优惠券、景区综合安防、车辆及停车场管理等服务。这些应用通过物联网和云计算技术,实现了旅游服务的智能化、个性化和协同化,提高了旅游服务的自由度和信息共享的动态性。 智慧旅游的发展标志着旅游信息化建设的智能化和应用多样化趋势,多种技术和应用交叉渗透至旅游行业的各个方面,预示着全面的智慧旅游时代已经到来。智慧旅游不仅提升了游客的旅游体验,也为旅游管理和服务提供了高效的技术支持。
智慧旅游解决方案利用云计算、物联网和移动互联网技术,通过便携终端设备,实现对旅游资源、经济、活动和旅游者信息的智能感知和发布。这种技术的应用旨在提升游客在旅游各个环节的体验,使他们能够轻松获取信息、规划行程、预订票务和安排食宿。智慧旅游平台为旅游管理部门、企业和游客提供服务,包括政策发布、行政管理、景区安全、游客流量统计分析、投诉反馈等。此外,平台还提供广告促销、库存信息、景点介绍、电子门票、社交互动等功能。 智慧旅游的建设规划得到了国家政策的支持,如《国家中长期科技发展规划纲要》和国务院的《关于加快发展旅游业的意见》,这些政策强调了旅游信息服务平台的建设和信息化服务的重要性。随着技术的成熟和政策环境的优化,智慧旅游的时机已经到来。 智慧旅游平台采用SaaS、PaaS和IaaS等云服务模式,提供简化的软件开发、测试和部署环境,实现资源的按需配置和快速部署。这些服务模式支持旅游企业、消费者和管理部门开发高性能、高可扩展的应用服务。平台还整合了旅游信息资源,提供了丰富的旅游产品创意平台和统一的旅游综合信息库。 智慧旅游融合应用面向游客和景区景点主管机构,提供无线城市门户、智能导游、智能门票及优惠券、景区综合安防、车辆及停车场管理等服务。这些应用通过物联网和云计算技术,实现了旅游服务的智能化、个性化和协同化,提高了旅游服务的自由度和信息共享的动态性。 智慧旅游的发展标志着旅游信息化建设的智能化和应用多样化趋势,多种技术和应用交叉渗透至旅游行业的各个方面,预示着全面的智慧旅游时代已经到来。智慧旅游不仅提升了游客的旅游体验,也为旅游管理和服务提供了高效的技术支持。
深度学习是机器学习的一个子领域,它基于人工神经网络的研究,特别是利用多层次的神经网络来进行学习和模式识别。深度学习模型能够学习数据的高层次特征,这些特征对于图像和语音识别、自然语言处理、医学图像分析等应用至关重要。以下是深度学习的一些关键概念和组成部分: 1. **神经网络(Neural Networks)**:深度学习的基础是人工神经网络,它是由多个层组成的网络结构,包括输入层、隐藏层和输出层。每个层由多个神经元组成,神经元之间通过权重连接。 2. **前馈神经网络(Feedforward Neural Networks)**:这是最常见的神经网络类型,信息从输入层流向隐藏层,最终到达输出层。 3. **卷积神经网络(Convolutional Neural Networks, CNNs)**:这种网络特别适合处理具有网格结构的数据,如图像。它们使用卷积层来提取图像的特征。 4. **循环神经网络(Recurrent Neural Networks, RNNs)**:这种网络能够处理序列数据,如时间序列或自然语言,因为它们具有记忆功能,能够捕捉数据中的时间依赖性。 5. **长短期记忆网络(Long Short-Term Memory, LSTM)**:LSTM 是一种特殊的 RNN,它能够学习长期依赖关系,非常适合复杂的序列预测任务。 6. **生成对抗网络(Generative Adversarial Networks, GANs)**:由两个网络组成,一个生成器和一个判别器,它们相互竞争,生成器生成数据,判别器评估数据的真实性。 7. **深度学习框架**:如 TensorFlow、Keras、PyTorch 等,这些框架提供了构建、训练和部署深度学习模型的工具和库。 8. **激活函数(Activation Functions)**:如 ReLU、Sigmoid、Tanh 等,它们在神经网络中用于添加非线性,使得网络能够学习复杂的函数。 9. **损失函数(Loss Functions)**:用于评估模型的预测与真实值之间的差异,常见的损失函数包括均方误差(MSE)、交叉熵(Cross-Entropy)等。 10. **优化算法(Optimization Algorithms)**:如梯度下降(Gradient Descent)、随机梯度下降(SGD)、Adam 等,用于更新网络权重,以最小化损失函数。 11. **正则化(Regularization)**:技术如 Dropout、L1/L2 正则化等,用于防止模型过拟合。 12. **迁移学习(Transfer Learning)**:利用在一个任务上训练好的模型来提高另一个相关任务的性能。 深度学习在许多领域都取得了显著的成就,但它也面临着一些挑战,如对大量数据的依赖、模型的解释性差、计算资源消耗大等。研究人员正在不断探索新的方法来解决这些问题。
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值