11 2011 档案
摘要：【介绍】SQL Server 通过WORKER, SCHEDULER, TASK等来对任务进行调度和处理。了解这些概念，对于了解SQL Server 内部是如何工作，是非常有帮助的。通常来讲，SCHEDULER个数是跟CPU个数相匹配的 。除了几个系统的SCHEDULER以外，每一个SCHEDULER都映射到一个CPU，如下面的查询结果所示，我们有四个CPU，也就有相应四个SCHEDULER。而WORKER (又称为WORKER THREAD), 则是工作线程。在一台服务器上，我们可以有多个工作线程。因为每一个工作线程要耗费资源，所以，SQL Server有一个最大工作线程数。一个TASK进来
阅读全文
posted @ 2011-11-28 11:03
摘要：首先看下面这段代码，可以看出：blocked-process是被阻塞的进程，执行的sql是select * from temp1blocking-process是正在产生阻塞的进程，执行的sql是select * from temp1 with(nolock)如果你偶尔抓到了这样的report，肯定会奇怪吧，为什么呢？理论下面的sql不会对上面的sql产生阻塞。<blocked-process-report> <blocked-process> <process id="process3d92550" taskpriority="0&
阅读全文
posted @ 2011-11-25 14:55
摘要：原文：http://sqlserverpedia.com/wiki/SAN_Performance_Tuning_with_SQLIODownloading and Configuring SQLIO[Download SQLIO from Microsoft]Notice that I said SQLIO, not SQLIOSIM. Experienced database administrators will often direct you to SQLIOSIM because it's easier to use and mimics SQL Server's
阅读全文
posted @ 2011-11-22 16:45
摘要：Well, this is often a tricky situation, where you are running into Virtual Address Fragmentation and getting OOM (out-of-memory)errors in your SQL Server. More often than not there is confusion between physical memory pressure vs. virtual memory pressure. Adding more RAM is definitely not a solution
阅读全文
posted @ 2011-11-15 16:07
摘要：http://blogs.msdn.com/b/distributedservices/archive/2008/11/12/troubleshooting-msdtc-issues-with-the-dtcping-tool.aspxEvery day the Distributed Services support team in Microsoft helps customers in troubleshooting some of the most common Distributed Transaction errors which are a direct result of MS
阅读全文
posted @ 2011-11-03 15:29
摘要：订阅库中有很多的死锁现象，MSreplication_subscriptions表中有8条记录，死锁大概是1小时40个，如下所示：deadlock-listdeadlock victim=processdbf1c8 process-list process id=processdbf1c8 taskpriority=0 logused=2116 waitresource=PAGE: 6:1:3304140 waittime=577 ownerId=1250752686 transactionname=user_transaction lasttranstarted=2011-11-03T09:
阅读全文
posted @ 2011-11-03 09:22
|
||
