This article shows how to "unmask" the sql query behind a FECTH API_CUSOR

http://www.sqlskills.com/blogs/joe/hunting-down-the-origins-of-fetch-api_cursor-and-sp_cursorfetch/

that is shown in a deadlock graph. But if only applies if one can capture the event while it is ongoing.  Is there a counter in Sql profier (2005) to indicate\capture the query behind the FETCH?  (because most of the time I find out about deadlocks long after the victim spid has been killed.)

TIA,

edm2

P.S.Of course it I captured every sql statement executed on the server that may do it but I'm trying not to overburden the server by collecting excessive info

One of the tempdb data file is 99% free. I was trying to reorganizing it's size to 50% of free space which means Tempdb data file is 100 GB out of which 99 GB is free. I am trying to resize it to 50 GB. But it wont allow me. It says

DBCC SHRINKFILE: Page 1:11557424 could not be moved because it is a work table page.

But my question is when 99 GB free space is there, why does it just dont allow??

If i have double index OrderID | ProductID 

and i try to find where ProductID = 30 AND OrderID = 20

will sql serever use in this situation the double index , i mean will it switch fields to OrderID = 20 AND ProductID 30

or it doesn't use this index and will use sequential search in the whole table?

Hi all,

Based on BOL, master and user databases' compatibility_level will not be changed to 110 on SQL Server 2012 in-place upgrade.

Database Compatibility Level After Upgrade

MCSE:Data Platform

Dear all,

My SQL Server is always alert IO alert , until often hanging and must reboot it !

It already drive me mad .

May you  give some advice ?

I already think some solution like below ? Which is better ?

1. upgrade EIP SQL Server 至 Service Pack 4 (currently Service Pack 2 )

Microsoft SQL Server 2005 Service Pack 4 RTM
http://www.microsoft.com/zh-tw/download/confirmation.aspx?id=7218

2. My Hyper-V 1.0 Convert to VMware。
3. STOP some AP 。
4. Windows 2003 to Windows 2012 R2 or (Windows 2008 R2) / SQL Server 2005 to SQL Server 2012 SP1

thank you!

the follow message is core dump .

=====================================================================                                           
       BugCheck Dump                                                                                            
=====================================================================                                           
                                                                                                                
This file is generated by Microsoft SQL Server                                                                  
version 9.00.3159.00                                                                                            
upon detection of fatal unexpected error. Please return this file,                                              
the query or program that produced the bugcheck, the database and                                               
the error log, and any other pertinent information with a Service Request.                                      
                                                                                                                
                                                                                                                
Computer type is AT/AT COMPATIBLE.                                                                              
Bios Version is VRTUAL - 5000805                                                                                 
BIOS Date: 05/05/08 20:35:56  Ver: 08.00.02                                                                     
Current time is 12:13:19 01/06/14.                                                                              
2 Intel x86 level 6, 2400 Mhz processor (s).                                                                    
Windows NT 5.2 Build 3790 CSD Service Pack 2.                                                                   
                                    
Memory                              
MemoryLoad = 60%                    
Total Physical = 4095 MB            
Available Physical = 1636 MB        
Total Page File = 7944 MB           
Available Page File = 5626 MB       
Total Virtual = 2047 MB             
Available Virtual = 559 MB          
**Dump thread - spid = 0, PSS = 0x00000000, EC = 0x00000000                                                     
***Stack Dump being sent to C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\SQLDump0019.txt             
* *******************************************************************************                               
*                                                                                                               
* BEGIN STACK DUMP:                                                                                             
*   01/06/14 12:13:19 spid 0                                                                                    
*                                                                                                               
* Non-yielding IOCP Listener                                                                                    
*                                                                                                               
* *******************************************************************************                               
* -------------------------------------------------------------------------------                               
* Short Stack Dump           

 than 15 seconds to complete on file [D:\SQLDB\callmsdb_0317_data.mdf] in database [callmsdb_0317] (62).  The OS file handle is 0x00000CB8.  The offset of the latest long I/O is: 0x0000299a6de000
2014-01-06 04:40:37.74 伺服器         The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2014-01-06 04:57:09.07 spid2s      SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\SQLDB\AP\CHTSMS\chtsms_log.LDF] in database [chtsms] (35).  The OS file handle is 0x00000B80.  The offset of the latest long I/O is: 0x0000000011fe00
2014-01-06 05:03:14.18 spid2s      SQL Server has encountered 3 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\SQLDB\Search\Search_Temp.mdf] in database [Search_Temp] (63).  The OS file handle is 0x00000CF8.  The offset of the latest long I/O is: 0x0000009049a000
2014-01-06 05:10:16.22 spid2s      SQL Server has encountered 5 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\SQLDB\Search\Search_Temp.mdf] in database [Search_Temp] (63).  The OS file handle is 0x00000CF8.  The offset of the latest long I/O is: 0x00000028438000
2014-01-06 05:17:40.66 spid2s      SQL Server has encountered 8 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\SQLDB\Search\Search_Temp.mdf] in database [Search_Temp] (63).  The OS file handle is 0x00000CF8.  The offset of the latest long I/O is: 0x0000005c9a2000
2014-01-06 05:19:11.80 spid2s      SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\SQLDB\DIP\DIP_AZ.mdf] in database [DIP_AZ] (43).  The OS file handle is 0x00000BDC.  The offset of the latest long I/O is: 0x00000000056000
2014-01-06 05:26:35.61 spid2s      SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [F:\SQLDB\AP\CCS\AP_08CCS_Data.mdf] in database [AP_08CCS] (7).  The OS file handle is 0x00000998.  The offset of the latest long I/O is: 0x0000000e160000
2014-01-06 05:27:17.15 spid2s      SQL Server has encountered 4 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\SQLDB\LeftMenu\LeftMenu08.mdf] in database [LeftMenu08] (23).  The OS file handle is 0x00000A3C.  The offset of the latest long I/O is: 0x00000194954000
2014-01-06 05:27:37.66 spid2s      SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\SQLDB\DIP\DIP_AZ.mdf] in database [DIP_AZ] (43).  The OS file handle is 0x00000BDC.  The offset of the latest long I/O is: 0x000000297f0000
2014-01-06 05:40:37.85 伺服器         The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2014-01-06 05:48:54.99 spid2s      SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\SQLDB\DIP\DIP_EZ.mdf] in database [DIP_EZ] (30).  The OS file handle is 0x00000B24.  The offset of the latest long I/O is: 0x00000068ce0000
2014-01-06 06:04:11.68 spid2s      SQL Server has encountered 3 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\SQLDB\DIP\DIP_EZ.mdf] in database [DIP_EZ] (30).  The OS file handle is 0x00000B24.  The offset of the latest long I/O is: 0x000000e615a000
2014-01-06 06:10:42.39 spid2s      SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [D:\SQLDB\callmsdb_0317_data.mdf] in database [callmsdb_0317] (62).  The OS file handle is 0x00000CB8.  The offset of the latest long I/O is: 0x00002257b80000
2014-01-06 06:10:42.39 spid2s      SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\SQLDB\TEMPDB\tempdb.mdf] in database [tempdb] (2).  The OS file handle is 0x000007A0.  The offset of the latest long I/O is: 0x000003ff820000
2014-01-06 06:35:40.12 spid2s      SQL Server has encountered 5 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\SQLDB\DIP\DIP_TZ.mdf] in database [DIP_TZ] (52).  The OS file handle is 0x00000C4C.  The offset of the latest long I/O is: 0x00000046a58000
2014-01-06 06:40:38.08 伺服器         The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2014-01-06 06:41:49.26 spid2s      SQL Server has encountered 4 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\SQLDB\DIP\DIP_TZ.mdf] in database [DIP_TZ] (52).  The OS file handle is 0x00000C4C.  The offset of the latest long I/O is: 0x0000006eb46000
2014-01-06 06:53:12.72 spid2s      SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\SQLDB\DIP\DIP_OZ.mdf] in database [DIP_OZ] (67).  The OS file handle is 0x00000CD0.  The offset of the latest long I/O is: 0x0000000def8000
2014-01-06 06:56:18.63 spid2s      SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\SQLDB\DIP\SkytraxBulletin.mdf] in database [SkytraxBulletin] (73).  The OS file handle is 0x00000D0C.  The offset of the latest long I/O is: 0x0000000e660000
2014-01-06 07:03:08.00 spid2s      SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [F:\SQLDB\HR\EIP_HR.mdf] in database [EIP_HR] (15).  The OS file handle is 0x0000097C.  The offset of the latest long I/O is: 0x00000002328000
2014-01-06 07:13:18.38 spid2s      SQL Server has encountered 27 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [D:\SQLDB\callmsdb_0317_data.mdf] in database [callmsdb_0317] (62).  The OS file handle is 0x00000CB8.  The offset of the latest long I/O is: 0x00000000354000
2014-01-06 07:26:11.13 spid2s      SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [D:\SQLDB\callmsdb_0317_data.mdf] in database [callmsdb_0317] (62).  The OS file handle is 0x00000CB8.  The offset of the latest long I/O is: 0x000001d7e80000
2014-01-06 07:40:38.27 伺服器         The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2014-01-06 07:45:21.33 spid2s      SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\SQLDB\LeftMenu\LeftMenu08.mdf] in database [LeftMenu08] (23).  The OS file handle is 0x00000A3C.  The offset of the latest long I/O is: 0x000000867ca000
2014-01-06 07:45:41.33 spid2s      SQL Server has encountered 2 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\SQLDB\OWA\china-airlines.mdf] in database [china-airlines] (66).  The OS file handle is 0x00000CCC.  The offset of the latest long I/O is: 0x00000003e58000
2014-01-06 07:49:58.99 spid2s      SQL Server has encountered 224 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [D:\SQLDB\callmsdb_0317_data.mdf] in database [callmsdb_0317] (62).  The OS file handle is 0x00000CB8.  The offset of the latest long I/O is: 0x00000661280000
2014-01-06 07:51:21.87 spid2s      SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\SQLDB\AP\CHTSMS\chtsms.mdf] in database [chtsms] (35).  The OS file handle is 0x00000B7C.  The offset of the latest long I/O is: 0x000000253b4000
2014-01-06 07:58:54.90 spid2s      SQL Server has encountered 3 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\SQLDB\SOP\SOP_NEW.mdf] in database [SOP_NEW] (38).  The OS file handle is 0x00000BAC.  The offset of the latest long I/O is: 0x00000259362000
2014-01-06 08:03:05.90 spid2s      SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\SQLDB\LeftMenu\LeftMenu08.mdf] in database [LeftMenu08] (23).  The OS file handle is 0x00000A3C.  The offset of the latest long I/O is: 0x00000222c86000
2014-01-06 08:04:08.18 spid2s      SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\SQLDB\DIP\DIP_SS.mdf] in database [DIP_SS] (68).  The OS file handle is 0x00000CE0.  The offset of the latest long I/O is: 0x00000043230000
2014-01-06 08:05:31.65 spid2s      SQL Server has encountered 501 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [D:\SQLDB\callmsdb_0317_data.mdf] in database [callmsdb_0317] (62).  The OS file handle is 0x00000CB8.  The offset of the latest long I/O is: 0x00002746b60000
2014-01-06 08:11:32.47 spid2s      SQL Server has encountered 36 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [D:\SQLDB\callmsdb_0317_data.mdf] in database [callmsdb_0317] (62).  The OS file handle is 0x00000CB8.  The offset of the latest long I/O is: 0x0000279da9a000
2014-01-06 08:13:56.96 spid2s      SQL Server has encountered 2 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\OWA_HR.mdf] in database [OWA_HR] (74).  The OS file handle is 0x00000D48.  The offset of the latest long I/O is: 0x000000000ae000
2014-01-06 08:14:57.57 spid2s      SQL Server has encountered 5 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\SQLDB\DIP\DIP_TZ.mdf] in database [DIP_TZ] (52).  The OS file handle is 0x00000C4C.  The offset of the latest long I/O is: 0x00000000396000
2014-01-06 08:15:58.33 spid2s      SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\SQLDB\AP\CHTSMS\chtsms.mdf] in database [chtsms] (35).  The OS file handle is 0x00000B7C.  The offset of the latest long I/O is: 0x0000015a75e000
2014-01-06 08:17:23.77 spid2s      SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [D:\SQLDB\callmsdb_0317_data.mdf] in database [callmsdb_0317] (62).  The OS file handle is 0x00000CB8.  The offset of the latest long I/O is: 0x0000353c5f0000
2014-01-06 08:25:06.97 spid2s      SQL Server has encountered 49 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [D:\SQLDB\callmsdb_0317_data.mdf] in database [callmsdb_0317] (62).  The OS file handle is 0x00000CB8.  The offset of the latest long I/O is: 0x0000205cf40000
2014-01-06 08:25:58.68 spid2s      SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\SQLDB\LeftMenu\LeftMenu07.mdf] in database [LeftMenu07] (25).  The OS file handle is 0x00000A70.  The offset of the latest long I/O is: 0x0000005d220000
2014-01-06 08:33:57.95 spid2s      SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\SQLDB\LeftMenu\LeftMenu08.mdf] in database [LeftMenu08] (23).  The OS file handle is 0x00000A3C.  The offset of the latest long I/O is: 0x0000017a036000
2014-01-06 08:36:30.91 spid2s      SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [F:\SQLDB\HR\EIP_HR.mdf] in database [EIP_HR] (15).  The OS file handle is 0x0000097C.  The offset of the latest long I/O is: 0x00000004272000
2014-01-06 08:40:28.70 spid2s      SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\SQLDB\SOP\SOP_NEW.mdf] in database [SOP_NEW] (38).  The OS file handle is 0x00000BAC.  The offset of the latest long I/O is: 0x00000260de6000
2014-01-06 08:48:35.59 伺服器         The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2014-01-06 09:03:07.15 spid2s      SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\SQLDB\LeftMenu\LeftMenu07.mdf] in database [LeftMenu07] (25).  The OS file handle is 0x00000A70.  The offset of the latest long I/O is: 0x0000001b116000
2014-01-06 09:04:09.23 spid2s      SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [D:\SQLDB\callmsdb_3_log.LDF] in database [callmsdb_0317] (62).  The OS file handle is 0x00000C84.  The offset of the latest long I/O is: 0x0000001684a400
2014-01-06 09:04:09.23 spid2s      SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\SQLDB\LeftMenu\LeftMenu03.mdf] in database [LeftMenu03] (14).  The OS file handle is 0x000007A8.  The offset of the latest long I/O is: 0x000000a25c4000
2014-01-06 09:16:18.41 spid2s      SQL Server has encountered 2 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [D:\SQLDB\callmsdb_0317_data.mdf] in database [callmsdb_0317] (62).  The OS file handle is 0x00000CB8.  The offset of the latest long I/O is: 0x0000296a6b4000
2014-01-06 09:21:01.38 spid2s      SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\SQLDB\SOP\SOP_NEW.mdf] in database [SOP_NEW] (38).  The OS file handle is 0x00000BAC.  The offset of the latest long I/O is: 0x0000025bb62000
2014-01-06 09:21:12.22 spid2s      SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\SQLDB\DIP\DIP_IZ.mdf] in database [DIP_IZ] (34).  The OS file handle is 0x00000B68.  The offset of the latest long I/O is: 0x000000418e2000
2014-01-06 09:32:30.42 spid2s      SQL Server has encountered 2 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\SQLDB\SOP\SOP_NEW.mdf] in database [SOP_NEW] (38).  The OS file handle is 0x00000BAC.  The offset of the latest long I/O is: 0x0000025b7e2000
2014-01-06 09:32:40.53 spid2s      SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\SQLDB\LeftMenu\LeftMenu03.mdf] in database [LeftMenu03] (14).  The OS file handle is 0x000007A8.  The offset of the latest long I/O is: 0x00000134fa0000
2014-01-06 09:33:31.85 spid2s      SQL Server has encountered 2 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [D:\SQLDB\callmsdb_0317_data.mdf] in database [callmsdb_0317] (62).  The OS file handle is 0x00000CB8.  The offset of the latest long I/O is: 0x00002c5332c000
2014-01-06 09:34:03.10 spid2s      SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [F:\SQLDB\HR\EIP_LOG.mdf] in database [EIP_LOG] (17).  The OS file handle is 0x00000FD8.  The offset of the latest long I/O is: 0x0000003bb70000
2014-01-06 09:36:57.16 spid2s      SQL Server has encountered 13 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\SQLDB\TEMPDB\tempdb.mdf] in database [tempdb] (2).  The OS file handle is 0x000007A0.  The offset of the latest long I/O is: 0x00000449c1a000
2014-01-06 09:41:03.66 spid2s      SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\SQLDB\LeftMenu\LeftMenu08.mdf] in database [LeftMenu08] (23).  The OS file handle is 0x00000A3C.  The offset of the latest long I/O is: 0x000001ee6c4000
2014-01-06 09:41:24.64 spid2s      SQL Server has encountered 77 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [D:\SQLDB\callmsdb_0317_data.mdf] in database [callmsdb_0317] (62).  The OS file handle is 0x00000CB8.  The offset of the latest long I/O is: 0x00002a98630000
2014-01-06 09:42:14.78 spid2s      SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\SQLDB\SOP\SOP_NEW.mdf] in database [SOP_NEW] (38).  The OS file handle is 0x00000BAC.  The offset of the latest long I/O is: 0x0000008ed7e000
2014-01-06 09:51:12.02 spid2s      SQL Server has encountered 2 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\SQLDB\DIP\DIP_BZ.mdf] in database [DIP_BZ] (44).  The OS file handle is 0x00000BF8.  The offset of the latest long I/O is: 0x0000004a0f4000
2014-01-06 09:56:17.87 spid2s      SQL Server has encountered 210 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [D:\SQLDB\callmsdb_0317_data.mdf] in database [callmsdb_0317] (62).  The OS file handle is 0x00000CB8.  The offset of the latest long I/O is: 0x0000111f3c2000
2014-01-06 09:56:37.73 伺服器         The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2014-01-06 10:02:24.51 spid2s      SQL Server has encountered 3 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [D:\SQLDB\callmsdb_0317_data.mdf] in database [callmsdb_0317] (62).  The OS file handle is 0x00000CB8.  The offset of the latest long I/O is: 0x0000123bfa0000
2014-01-06 10:07:24.62 spid2s      SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\SQLDB\TEMPDB\tempdb.mdf] in database [tempdb] (2).  The OS file handle is 0x000007A0.  The offset of the latest long I/O is: 0x0000043ef70000
2014-01-06 10:12:54.55 spid2s      SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\SQLDB\LeftMenu\LeftMenu03.mdf] in database [LeftMenu03] (14).  The OS file handle is 0x000007A8.  The offset of the latest long I/O is: 0x00000167602000
2014-01-06 10:13:05.25 spid2s      SQL Server has encountered 127 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [D:\SQLDB\callmsdb_0317_data.mdf] in database [callmsdb_0317] (62).  The OS file handle is 0x00000CB8.  The offset of the latest long I/O is: 0x000028c1dac000
2014-01-06 10:13:15.34 spid2s      SQL Server has encountered 2 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\SQLDB\SOP\SOP_NEW.mdf] in database [SOP_NEW] (38).  The OS file handle is 0x00000BAC.  The offset of the latest long I/O is: 0x0000025eae4000
2014-01-06 10:14:17.08 spid2s      SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\SQLDB\LeftMenu\LeftMenu07.mdf] in database [LeftMenu07] (25).  The OS file handle is 0x00000A70.  The offset of the latest long I/O is: 0x00000001db0000
2014-01-06 10:18:46.14 spid2s      SQL Server has encountered 36 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [D:\SQLDB\callmsdb_0317_data.mdf] in database [callmsdb_0317] (62).  The OS file handle is 0x00000CB8.  The offset of the latest long I/O is: 0x00002fa4c7a000
2014-01-06 10:19:17.99 spid2s      SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\SQLDB\LeftMenu\LeftMenu03.mdf] in database [LeftMenu03] (14).  The OS file handle is 0x000007A8.  The offset of the latest long I/O is: 0x0000014f7b2000
2014-01-06 10:23:24.95 spid2s      SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\SQLDB\DIP\DIP_KZ.mdf] in database [DIP_KZ] (49).  The OS file handle is 0x00000C18.  The offset of the latest long I/O is: 0x00000124ace000
2014-01-06 10:23:35.90 spid2s      SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [F:\SQLDB\HR\EIP_LOG.mdf] in database [EIP_LOG] (17).  The OS file handle is 0x00000FD8.  The offset of the latest long I/O is: 0x0000000c956000
2014-01-06 10:24:17.87 spid2s      SQL Server has encountered 52 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [D:\SQLDB\callmsdb_0317_data.mdf] in database [callmsdb_0317] (62).  The OS file handle is 0x00000CB8.  The offset of the latest long I/O is: 0x00003395c8a000
2014-01-06 10:24:38.56 spid2s      SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\SQLDB\SOP\SOP_NEW.mdf] in database [SOP_NEW] (38).  The OS file handle is 0x00000BAC.  The offset of the latest long I/O is: 0x00000259162000
2014-01-06 10:25:10.38 spid2s      SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\SQLDB\DIP\SkytraxBulletin.mdf] in database [SkytraxBulletin] (73).  The OS file handle is 0x00000D0C.  The offset of the latest long I/O is: 0x00000010cae000
2014-01-06 10:29:19.12 spid2s      SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\SQLDB\DIP\DIP_IZ.mdf] in database [DIP_IZ] (34).  The OS file handle is 0x00000B68.  The offset of the latest long I/O is: 0x000000658f0000
2014-01-06 10:29:40.01 spid2s      SQL Server has encountered 42 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [D:\SQLDB\callmsdb_0317_data.mdf] in database [callmsdb_0317] (62).  The OS file handle is 0x00000CB8.  The offset of the latest long I/O is: 0x00003412840000
2014-01-06 10:31:13.12 spid2s      SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\SQLDB\LeftMenu\LeftMenu08.mdf] in database [LeftMenu08] (23).  The OS file handle is 0x00000A3C.  The offset of the latest long I/O is: 0x000000f81ae000
2014-01-06 10:37:35.37 spid2s      SQL Server has encountered 2 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\SQLDB\LeftMenu\LeftMenu08.mdf] in database [LeftMenu08] (23).  The OS file handle is 0x00000A3C.  The offset of the latest long I/O is: 0x0000021ff4a000
2014-01-06 10:37:55.49 spid2s      SQL Server has encountered 446 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [D:\SQLDB\callmsdb_0317_data.mdf] in database [callmsdb_0317] (62).  The OS file handle is 0x00000CB8.  The offset of the latest long I/O is: 0x000008a79a2000
2014-01-06 10:44:51.22 spid2s      SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\SQLDB\SOP\SOP_NEW.mdf] in database [SOP_NEW] (38).  The OS file handle is 0x00000BAC.  The offset of the latest long I/O is: 0x0000025d864000
2014-01-06 10:45:43.63 spid2s      SQL Server has encountered 3 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [D:\SQLDB\callmsdb_0317_data.mdf] in database [callmsdb_0317] (62).  The OS file handle is 0x00000CB8.  The offset of the latest long I/O is: 0x000019a78d0000
2014-01-06 10:50:01.95 spid2s      SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\SQLDB\AP\CHTSMS\chtsms.mdf] in database [chtsms] (35).  The OS file handle is 0x00000B7C.  The offset of the latest long I/O is: 0x00000100920000
2014-01-06 10:51:04.54 spid2s      SQL Server has encountered 8 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [F:\SQLDB\AP\CAS2000\CAS2000.mdf] in database [CAS2000] (26).  The OS file handle is 0x00000AE0.  The offset of the latest long I/O is: 0x00000000fca000
2014-01-06 10:52:17.55 spid2s      SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\SQLDB\DIP\DIP_OZ.mdf] in database [DIP_OZ] (67).  The OS file handle is 0x00000CD0.  The offset of the latest long I/O is: 0x0000043d680000
2014-01-06 10:53:40.52 spid2s      SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [D:\SQLDB\callmsdb_0317_data.mdf] in database [callmsdb_0317] (62).  The OS file handle is 0x00000CB8.  The offset of the latest long I/O is: 0x00002427588000
2014-01-06 10:56:41.53 伺服器         The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2014-01-06 11:00:04.63 spid2s      SQL Server has encountered 2 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [D:\SQLDB\callmsdb_0317_data.mdf] in database [callmsdb_0317] (62).  The OS file handle is 0x00000CB8.  The offset of the latest long I/O is: 0x000030cd0dc000
2014-01-06 11:00:15.14 spid2s      SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\SQLDB\LeftMenu\LeftMenu03.mdf] in database [LeftMenu03] (14).  The OS file handle is 0x000007A8.  The offset of the latest long I/O is: 0x0000016e4c4000
2014-01-06 11:02:18.35 spid2s      SQL Server has encountered 4 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\SQLDB\DIP\DIP_PZ.mdf] in database [DIP_PZ] (27).  The OS file handle is 0x00000AE8.  The offset of the latest long I/O is: 0x00000000678000
2014-01-06 11:04:00.87 spid2s      SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\SQLDB\LeftMenu\LeftMenu07.mdf] in database [LeftMenu07] (25).  The OS file handle is 0x00000A70.  The offset of the latest long I/O is: 0x0000001ff50000
2014-01-06 11:04:51.56 spid2s      SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\SQLDB\SOP\SOP_NEW.mdf] in database [SOP_NEW] (38).  The OS file handle is 0x00000BAC.  The offset of the latest long I/O is: 0x000002602e6000
2014-01-06 11:05:12.34 spid2s      SQL Server has encountered 410 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [D:\SQLDB\callmsdb_0317_data.mdf] in database [callmsdb_0317] (62).  The OS file handle is 0x00000CB8.  The offset of the latest long I/O is: 0x00003144584000
2014-01-06 11:10:01.12 spid2s      SQL Server has encountered 4 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\SQLDB\DIP\DIP_PZ.mdf] in database [DIP_PZ] (27).  The OS file handle is 0x00000AE8.  The offset of the latest long I/O is: 0x00000019f3a000
2014-01-06 11:14:31.00 spid2s      SQL Server has encountered 105 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [D:\SQLDB\callmsdb_0317_data.mdf] in database [callmsdb_0317] (62).  The OS file handle is 0x00000CB8.  The offset of the latest long I/O is: 0x00001cf7ca0000
2014-01-06 11:24:10.28 spid2s      SQL Server has encountered 19 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [D:\SQLDB\callmsdb_0317_data.mdf] in database [callmsdb_0317] (62).  The OS file handle is 0x00000CB8.  The offset of the latest long I/O is: 0x00001f70822000
2014-01-06 11:28:51.29 spid2s      SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\SQLDB\LeftMenu\LeftMenu08.mdf] in database [LeftMenu08] (23).  The OS file handle is 0x00000A3C.  The offset of the latest long I/O is: 0x0000021e850000
2014-01-06 11:30:04.95 spid2s      SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\SQLDB\LeftMenu\LeftMenu07.mdf] in database [LeftMenu07] (25).  The OS file handle is 0x00000A70.  The offset of the latest long I/O is: 0x000000016b0000
2014-01-06 11:33:00.89 spid2s      SQL Server has encountered 15 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [D:\SQLDB\callmsdb_0317_data.mdf] in database [callmsdb_0317] (62).  The OS file handle is 0x00000CB8.  The offset of the latest long I/O is: 0x00001d12af0000
2014-01-06 11:33:21.67 spid2s      SQL Server has encountered 4 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\SQLDB\SOP\SOP_NEW.mdf] in database [SOP_NEW] (38).  The OS file handle is 0x00000BAC.  The offset of the latest long I/O is: 0x00000256e60000
2014-01-06 11:38:00.79 spid2s      SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\SQLDB\LeftMenu\LeftMenu03.mdf] in database [LeftMenu03] (14).  The OS file handle is 0x000007A8.  The offset of the latest long I/O is: 0x00000153166000
2014-01-06 11:39:22.26 spid2s      SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\SQLDB\LeftMenu\LeftMenu07.mdf] in database [LeftMenu07] (25).  The OS file handle is 0x00000A70.  The offset of the latest long I/O is: 0x0000009f9d2000
2014-01-06 11:41:58.08 spid2s      SQL Server has encountered 13 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\SQLDB\SOP\SOP_NEW.mdf] in database [SOP_NEW] (38).  The OS file handle is 0x00000BAC.  The offset of the latest long I/O is: 0x000002587e2000
2014-01-06 11:47:51.19 spid2s      SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\SQLDB\AP\CHTSMS\chtsms.mdf] in database [chtsms] (35).  The OS file handle is 0x00000B7C.  The offset of the latest long I/O is: 0x0000004f130000
2014-01-06 11:48:32.73 spid2s      SQL Server has encountered 151 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [D:\SQLDB\callmsdb_0317_data.mdf] in database [callmsdb_0317] (62).  The OS file handle is 0x00000CB8.  The offset of the latest long I/O is: 0x00001b50a16000
2014-01-06 11:51:39.41 spid2s      SQL Server has encountered 2 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\SQLDB\DIP\DIP_EZ.mdf] in database [DIP_EZ] (30).  The OS file handle is 0x00000B24.  The offset of the latest long I/O is: 0x00000136d68000
2014-01-06 11:52:52.01 spid2s      SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\SQLDB\LeftMenu\LeftMenu08.mdf] in database [LeftMenu08] (23).  The OS file handle is 0x00000A3C.  The offset of the latest long I/O is: 0x000002240ba000
2014-01-06 11:54:13.98 spid2s      SQL Server has encountered 2 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [D:\SQLDB\callmsdb_0317_data.mdf] in database [callmsdb_0317] (62).  The OS file handle is 0x00000CB8.  The offset of the latest long I/O is: 0x000031c2d1e000
2014-01-06 11:54:44.63 spid2s      SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\SQLDB\DIP\DIP_OZ.mdf] in database [DIP_OZ] (67).  The OS file handle is 0x00000CD0.  The offset of the latest long I/O is: 0x0000040ddf4000
2014-01-06 12:04:17.64 spid2s      SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\SQLDB\LeftMenu\LeftMenu07.mdf] in database [LeftMenu07] (25).  The OS file handle is 0x00000A70.  The offset of the latest long I/O is: 0x000000a19f8000
2014-01-06 12:04:43.20 伺服器         The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2014-01-06 12:05:50.38 spid2s      SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\SQLDB\TEMPDB\tempdb.mdf] in database [tempdb] (2).  The OS file handle is 0x000007A0.  The offset of the latest long I/O is: 0x00000480bf0000
2014-01-06 12:08:25.76 spid2s      SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\SQLDB\DIP\DIP_EZ.mdf] in database [DIP_EZ] (30).  The OS file handle is 0x00000B24.  The offset of the latest long I/O is: 0x00000121cee000
2014-01-06 12:13:19.16 Server      Using 'dbghelp.dll' version '4.0.5'
2014-01-06 12:13:19.22 Server      **Dump thread - spid = 0, PSS = 0x00000000, EC = 0x00000000
2014-01-06 12:13:19.22 Server      ***Stack Dump being sent to C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\SQLDump0019.txt
2014-01-06 12:13:19.22 Server      * *******************************************************************************
2014-01-06 12:13:19.22 Server      *
2014-01-06 12:13:19.22 Server      * BEGIN STACK DUMP:
2014-01-06 12:13:19.22 Server      *   01/06/14 12:13:19 spid 0
2014-01-06 12:13:19.22 Server      *
2014-01-06 12:13:19.22 Server      * Non-yielding IOCP Listener
2014-01-06 12:13:19.22 Server      *
2014-01-06 12:13:19.22 Server      * *******************************************************************************
2014-01-06 12:13:19.22 Server      * -------------------------------------------------------------------------------
2014-01-06 12:13:19.22 Server      * Short Stack Dump
2014-01-06 12:13:20.50 Server      Stack Signature for the dump is 0x000002FE
2014-01-06 12:13:41.78 Server      Timeout waiting for external dump process 4220.

We've been getting occasional 701 errors (SQL Server 2012 SP1 standard edition) 64 bit. This instance has 64 GB max server memory on a server with 128 GB of RAM. I'm trying to decode the errorlog output and have a couple of questions.

1) General Question -  I see output such as:

---------------------------------------- ----------
VM Reserved                                       0
VM Committed                                      0
Locked Pages Allocated                            0
SM Reserved                                       0
SM Committed                                      0
Pages Allocated                           20452920
2014-01-02 07:31:49.73 spid29s    
MEMORYCLERK_SQLOPTIMIZER (node 0)                KB
---------------------------------------- ----------
VM Reserved                                       0
VM Committed                                      0
Locked Pages Allocated                            0
SM Reserved                                       0
SM Committed                                      0
Pages Allocated                               5896
2014-01-02 07:31:49.73 spid29s    
MEMORYCLERK_SQLOPTIMIZER (node 1)                KB
---------------------------------------- ----------
VM Reserved                                       0
VM Committed                                      0
Locked Pages Allocated                            0
SM Reserved                                       0
SM Committed                                      0
Pages Allocated                                664
2014-01-02 07:31:49.73 spid29s    
MEMORYCLERK_SQLOPTIMIZER (Total)                 KB
---------------------------------------- ----------

What is this saying exactly: If Node 0 has 20452920 KB allocated to this clerk and Node 1 has  5896 KB allocated. Why does the entry regarding(total) say this clerk has 664 allocated? Does total mean something else here?

Question 2.

If I see entries as below, does this mean that the query attempting to get memory diagnostics has itself failed and so the diagnostic info is suspect?

---------------------------------------- ----------

VM Reserved                                 3366240
VM Committed                                 131072
Locked Pages Allocated                      1761712
SM Reserved                                       0
SM Committed                                      0
Pages Allocated                            38606944
2014-01-02 07:31:49.73 spid130     Error: 701, Severity: 17, State: 123.
2014-01-02 07:31:49.73 spid130     There is insufficient system memory in resource pool 'internal' to run this query.
2014-01-02 07:31:49.73 spid149     Error: 701, Severity: 17, State: 123.
2014-01-02 07:31:49.73 spid149     There is insufficient system memory in resource pool 'internal' to run this query.
2014-01-02 07:31:49.73 spid130     Error: 701, Severity: 17, State: 123.
2014-01-02 07:31:49.73 spid130     There is insufficient system memory in resource pool 'internal' to run this query.
2014-01-02 07:31:49.73 spid242     Error: 701, Severity: 17, State: 123.
2014-01-02 07:31:49.73 spid242     There is insufficient system memory in resource pool 'internal' to run this query.
2014-01-02 07:31:49.73 spid29s    
MEMORYCLERK_SQLQUERYEXEC (node 0)     

---------------------------------------- ----------

best regards

K

Ken Eng

Im keeping an eye on the Transaction log for a database that I am cleaning up.  There is a 3rd party tool that is supposedly doing Transaction log backups.  However, I have been tracking the file space for this database over the last few months and the free space for the log has gradually been declining.  When a Tlog backup is done, wont this reclaim the space?

However, after reading up a bit on this, there are factors that can prevent the log space from being reclaimed...

http://msdn.microsoft.com/en-us/library/ms189085.aspx

http://msdn.microsoft.com/en-us/library/ms345414.aspx

What the heck will hang around in a log file after months of use, to the point of STILL taking up 20-50 MB of a 3 GB Log file?

Does someone know if ATA-over-Ethernet kind of storage supported to put SQL Server data/log files on it? I am looking for some official document from MS. I know about iSCSCI and FC supportability... and also know AoE is a protocol, not native to MS. However, the title question remains the same :)

Any additional info like perf, scalability etc would also be helpful.

Thanks in anticipation!

This posting is provided “AS IS” with no warranties, and confers no rights.

Server: Windows Server 2012, Windows Firewall: Off, SQL Server Database Engines: ON, SQL Browser Service: ON

Client: Windows 7 Home Premium (Local Area Network Computer)

Issue:

From server, I can use Microsoft SQL Server Management Studio to connect to any SQL Server database engine (Primary or named) on the server.

From Client, I can use a remote desktop connection and within the remote desktop connection I can start Microsoft SQL Server Management Studio on the server and connect to any SQL Server database engine (Primary or named).

From Client, I can start Microsoft SQL Server Management Studio but attempts to connect to the Server’s instances of SQL Server result in the following:

Primary SQL Server instance:

Windows Authentication or SQL Server Authentication (Same Error)

===================================

Cannot connect to XXXX-SERVER12.

===================================

Connection Timeout Expired.  The timeout period elapsed while attempting to consume the pre-login handshake acknowledgement. This could be because the pre-login handshake failed or the server was unable to respond back in time. The duration spent while attempting to connect to this server was - [Pre-Login] initialization=22290; handshake=36; (.Net SqlClient Data Provider)

------------------------------

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&EvtSrc=MSSQLServer&EvtID=-2&LinkId=20476

------------------------------

Server Name: XXXX-SERVER12

Error Number: -2

Severity: 11

State: 0

------------------------------

Program Location:

   at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)

   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)

   at System.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject stateObj, UInt32 error)

   at System.Data.SqlClient.TdsParserStateObject.ReadSniSyncOverAsync()

   at System.Data.SqlClient.TdsParserStateObject.TryReadNetworkPacket()

   at System.Data.SqlClient.TdsParser.ConsumePreLoginHandshake(Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, Boolean& marsCapable)

   at System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, Boolean withFailover)

   at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean ignoreSniOpenTimeout, TimeoutTimer timeout, Boolean withFailover)

   at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString connectionOptions, SqlCredential credential, TimeoutTimer timeout)

   at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(TimeoutTimer timeout, SqlConnectionString connectionOptions, SqlCredential credential, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance)

   at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, SqlCredential credential, Object providerInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString userConnectionOptions, SessionData reconnectSessionData)

   at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, DbConnectionPoolKey poolKey, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions userOptions)

   at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup, DbConnectionOptions userOptions)

   at System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection)

   at System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)

   at System.Data.ProviderBase.DbConnectionClosed.TryOpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)

   at System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource`1 retry)

   at System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry)

   at System.Data.SqlClient.SqlConnection.Open()

   at Microsoft.SqlServer.Management.SqlStudio.Explorer.ObjectExplorerService.ValidateConnection(UIConnectionInfo ci, IServerType server)

   at Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()

===================================

The wait operation timed out

XXXXXXXXXXXXXXXXXXXXXXXXXXX

Named SQL Server instances:

Windows Authentication or SQL Server Authentication (Same Error)

===================================

Cannot connect to XXXX-SERVER12\XXXXSQLSERVER.

===================================

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (.Net SqlClient Data Provider)

------------------------------

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&EvtSrc=MSSQLServer&EvtID=-1&LinkId=20476

------------------------------

Error Number: -1

Severity: 20

State: 0

------------------------------

Program Location:

   at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)

   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)

   at System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, Boolean withFailover)

   at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean ignoreSniOpenTimeout, TimeoutTimer timeout, Boolean withFailover)

   at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString connectionOptions, SqlCredential credential, TimeoutTimer timeout)

   at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(TimeoutTimer timeout, SqlConnectionString connectionOptions, SqlCredential credential, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance)

   at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, SqlCredential credential, Object providerInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString userConnectionOptions, SessionData reconnectSessionData)

   at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, DbConnectionPoolKey poolKey, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions userOptions)

   at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup, DbConnectionOptions userOptions)

   at System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection)

   at System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)

   at System.Data.ProviderBase.DbConnectionClosed.TryOpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)

   at System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource`1 retry)

   at System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry)

   at System.Data.SqlClient.SqlConnection.Open()

   at Microsoft.SqlServer.Management.SqlStudio.Explorer.ObjectExplorerService.ValidateConnection(UIConnectionInfo ci, IServerType server)

   at Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()

Additional: All SQL Services (Except SQL Server Agent (primary and instances)) are running, all protocols are enabled and SQL Server Log shows no failed logon attempts.

I don't know if this has been posted before. I have look around and could not find any similar question.

I am written a stored proc that will do a bulk load using bulk insert command. But I am getting an error msg 4861. below is my full error msg and my code. Can someone advice what I am doing wrong. The sql server engine is on a total different server from my text file. But they are all on the same network.

I am trying to create a Transaction Log Backup for a database in SQL Server 2008R2, but it does not appear in the drop down list when I choose Tasks==>Backup. It only offers Full and Differential, any ideas why this may be occurring?

Any help is appreciated

There is an existing job which handles Backups for a given DB.  The command being run is

BACKUP DATABASE MyDBHere TO SomeNameHere WITH INIT, NOSKIP

The end result is some files on a drive with a .DAT extension being written to.

Also, the name SomeNameHere...is not the same as the actual file name, or else this isnt exactly whats happening.

Im familiar with .BAK files but not backing up to something with a .DAT extension.
Now Ive read it doesnt really matter what the file extension is for the backup file, but for this database, there is NO backup device defined when I select Tasks > Backup

So, how how can the above command function correctly, if there is no backup device defined, only these .DAT files?

Im building a report file and when I preview the report, it fails because my account cant access the master database.

My dataset is just calling xp_readerrorlog, which is in master.

I can call it just fine in a query window, but not from BIDS, using a connection with windows security.

I can however, preview the dataset ok, but when I open the RDL file from SSMS under custom reports, I get an login error.

However, if I preview the report...it fails and says the login failed, login failed for user mydomain\myuser ....

From time to time, SQL is 'randomly' shutting itself down - a production server, so very frustrating. Any help to find the cause, would be appreciated. Having read other threads on a similar theme, I am trying to include all of the information that I have seen asked for...<o:p></o:p>

*** SQL Dump File ***<o:p></o:p>

This file is generated by Microsoft SQL Server
version 10.50.4000.0
upon detection of fatal unexpected error. Please return this file,
the query or program that produced the bugcheck, the database and
the error log, and any other pertinent information with a Service Request.


Computer type is Intel(R) Xeon(R) CPU X5650 @ 2.67GHz.
Bios Version is VRTUAL - 3000919
BIOS Date: 03/19/09 22:51:32 Ver: 09.00.04
4 X64 level 8664, 10 Mhz processor (s).
Windows NT 6.1 Build 7601 CSD Service Pack 1.

Memory
MemoryLoad = 25%
Total Physical = 15999 MB
Available Physical = 11957 MB
Total Page File = 31997 MB
Available Page File = 26166 MB
Total Virtual = 8388607 MB
Available Virtual = 8364196 MB <o:p></o:p>

*** Dump Summary ***<o:p></o:p>

Dump File:      SQLDump0023.mdmp : C:\Users\sanderson\Desktop\SQLDump0023.mdmp
Last Write Time:          09/01/2014 16:15:38
Process Name:           sqlservr.exe : D:\SQLServer\MSSQL10_50.DECRI\MSSQL\Binn\sqlservr.exe
Process Architecture:  x64
Exception Code:          0x80000003
Exception Information:           A breakpoint was encountered.
Heap Information:       Not Present

System Information
------------------
OS Version:      6.1.7601
CLR Version(s):           2.0.50727.5472

Modules
-------
Module Name   Module Path     Module Version
-----------          -----------         --------------
sqlservr.exe     D:\SQLServer\MSSQL10_50.DECRI\MSSQL\Binn\sqlservr.exe  2009.100.4000.0
ntdll.dllC:\Windows\System32\ntdll.dll           6.1.7601.17725
kernel32.dll      C:\Windows\System32\kernel32.dll    6.1.7601.18015
KERNELBASE.dll           C:\Windows\System32\KERNELBASE.dll          6.1.7601.18015
advapi32.dll      C:\Windows\System32\advapi32.dll    6.1.7600.16385
msvcrt.dll         C:\Windows\System32\msvcrt.dll       7.0.7601.17744
sechost.dll       C:\Windows\System32\sechost.dll     6.1.7600.16385
rpcrt4.dll          C:\Windows\System32\rpcrt4.dll        6.1.7601.17514
msvcr80.dll           C:\Windows\winsxs\amd64_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4940_none_88df89932faf0bf6\msvcr80.dll           8.0.50727.4940
msvcp80.dll           C:\Windows\winsxs\amd64_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4940_none_88df89932faf0bf6\msvcp80.dll           8.0.50727.4940
sqlos.dll           D:\SQLServer\MSSQL10_50.DECRI\MSSQL\Binn\sqlos.dll        2009.100.4000.0
secur32.dll       C:\Windows\System32\secur32.dll     6.1.7601.17725
sspicli.dll          C:\Windows\System32\sspicli.dll        6.1.7601.17725
pdh.dll  C:\Windows\System32\pdh.dll6.1.7601.17514
shlwapi.dll        C:\Windows\System32\shlwapi.dll      6.1.7601.17514
gdi32.dll           C:\Windows\System32\gdi32.dll         6.1.7601.17514
user32.dll         C:\Windows\System32\user32.dll       6.1.7601.17514
lpk.dll   C:\Windows\System32\lpk.dll  6.1.7600.16385
usp10.dll          C:\Windows\System32\usp10.dll        1.626.7601.18009
userenv.dll       C:\Windows\System32\userenv.dll     6.1.7601.17514
profapi.dll         C:\Windows\System32\profapi.dll       6.1.7600.16385
winmm.dll        C:\Windows\System32\winmm.dll      6.1.7600.16385
IPHLPAPI.DLL    C:\Windows\System32\IPHLPAPI.DLL  6.1.7601.17514
nsi.dll   C:\Windows\System32\nsi.dll  6.1.7600.16385
winnsi.dll          C:\Windows\System32\winnsi.dll        6.1.7600.16385
opends60.dll    D:\SQLServer\MSSQL10_50.DECRI\MSSQL\Binn\opends60.dll 2009.100.1600.1
netapi32.dll      C:\Windows\System32\netapi32.dll    6.1.7601.17887
netutils.dll        C:\Windows\System32\netutils.dll      6.1.7601.17514
srvcli.dll           C:\Windows\System32\srvcli.dll          6.1.7601.17514
wkscli.dll          C:\Windows\System32\wkscli.dll        6.1.7601.17514
logoncli.dll        C:\Windows\System32\logoncli.dll      6.1.7601.17514
samcli.dll          C:\Windows\System32\samcli.dll        6.1.7601.17514
BatchParser.dllD:\SQLServer\MSSQL10_50.DECRI\MSSQL\Binn\BatchParser.dll          2009.100.1600.1
imm32.dll        C:\Windows\System32\imm32.dll      6.1.7600.16385
msctf.dll           C:\Windows\System32\msctf.dll         6.1.7600.16385
psapi.dll           C:\Windows\System32\psapi.dll         6.1.7600.16385
instapi10.dll     C:\Program Files\Microsoft SQL Server\100\Shared\instapi10.dll        2009.100.1600.1
cscapi.dll          C:\Windows\System32\cscapi.dll        6.1.7601.17514
sqlevn70.rll      D:\SQLServer\MSSQL10_50.DECRI\MSSQL\Binn\Resources\1033\sqlevn70.rll2009.100.4000.0
cryptsp.dll        C:\Windows\System32\cryptsp.dll      6.1.7600.16385
rsaenh.dll         C:\Windows\System32\rsaenh.dll       6.1.7600.16385
CRYPTBASE.dll  C:\Windows\System32\CRYPTBASE.dll6.1.7600.16385
browcli.dll         C:\Windows\System32\browcli.dll       6.1.7601.17887
authz.dll           C:\Windows\System32\authz.dll         6.1.7600.16385
mscoree.dll      C:\Windows\System32\mscoree.dll    4.0.40305.0
ole32.dll           C:\Windows\System32\ole32.dll         6.1.7601.17514
credssp.dll       C:\Windows\System32\credssp.dll     6.1.7601.17514
msv1_0.dll       C:\Windows\System32\msv1_0.dll     6.1.7601.17514
cryptdll.dll        C:\Windows\System32\cryptdll.dll      6.1.7600.16385
kerberos.dll      C:\Windows\System32\kerberos.dll    6.1.7601.17926
msasn1.dll       C:\Windows\System32\msasn1.dll     6.1.7601.17514
schannel.dll      C:\Windows\System32\schannel.dll    6.1.7601.17940
crypt32.dll        C:\Windows\System32\crypt32.dll      6.1.7601.18151
security.dll       C:\Windows\System32\security.dll     6.1.7600.16385
ws2_32.dll       C:\Windows\System32\ws2_32.dll     6.1.7601.17514
shell32.dll        C:\Windows\System32\shell32.dll      6.1.7601.18103
oleaut32.dll      C:\Windows\System32\oleaut32.dll    6.1.7601.17676
ncrypt.dll          C:\Windows\System32\ncrypt.dll        6.1.7601.18007
bcrypt.dll          C:\Windows\System32\bcrypt.dll        6.1.7600.16385
mswsock.dll     C:\Windows\System32\mswsock.dll   6.1.7601.17514
wship6.dll         C:\Windows\System32\wship6.dll       6.1.7600.16385
WSHTCPIP.DLL  C:\Windows\System32\WSHTCPIP.DLL6.1.7600.16385
ntmarta.dll       C:\Windows\System32\ntmarta.dll     6.1.7600.16385
Wldap32.dll      C:\Windows\System32\Wldap32.dll    6.1.7601.17514
ntdsapi.dll        C:\Windows\System32\ntdsapi.dll      6.1.7600.16385
dnsapi.dll         C:\Windows\System32\dnsapi.dll       6.1.7601.17570
rasadhlp.dll      C:\Windows\System32\rasadhlp.dll    6.1.7600.16385
FWPUCLNT.DLLC:\Windows\System32\FWPUCLNT.DLL           6.1.7600.16385
bcryptprimitives.dll      C:\Windows\System32\bcryptprimitives.dll    6.1.7601.17514
clbcatq.dll        C:\Windows\System32\clbcatq.dll      2001.12.8530.16385
sqlncli10.dll      C:\Windows\System32\sqlncli10.dll    2009.100.4000.0
version.dll        C:\Windows\System32\version.dll      6.1.7600.16385
comctl32.dll     C:\Windows\winsxs\amd64_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.17514_none_a4d6a923711520a9\comctl32.dll      5.82.7601.17514
comdlg32.dll    C:\Windows\System32\comdlg32.dll  6.1.7601.17514
SQLNCLIR10.RLL          C:\Windows\System32\1033\SQLNCLIR10.RLL           2009.100.1600.1
apphelp.dll       C:\Windows\System32\apphelp.dll     6.1.7601.17514
XPStar.DLL       D:\SQLServer\MSSQL10_50.DECRI\MSSQL\Binn\XPStar.DLL    2009.100.1600.1
sqlscm.dll        D:\SQLServer\MSSQL10_50.DECRI\MSSQL\Binn\sqlscm.dll     2009.100.1600.1
odbc32.dll        C:\Windows\System32\odbc32.dll      6.1.7601.17514
ATL80.dll           C:\Windows\winsxs\amd64_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.4053_none_8a1a02152edb659b\ATL80.dll           8.0.50727.4053
odbcint.dll        C:\Windows\System32\odbcint.dll      6.1.7600.16385
clusapi.dll         C:\Windows\System32\clusapi.dll       6.1.7601.17514
resutils.dll        C:\Windows\System32\resutils.dll      6.1.7600.16385
XPStar.RLL        D:\SQLServer\MSSQL10_50.DECRI\MSSQL\Binn\Resources\1033\XPStar.RLL 2009.100.1600.1
oledb32.dll       C:\Program Files\Common Files\System\Ole DB\oledb32.dll  6.1.7601.17514
msdart.dll        C:\Windows\System32\msdart.dll      6.1.7600.16385
comctl32.dll     C:\Windows\winsxs\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_fa396087175ac9ac\comctl32.dll          6.10.7601.17514
oledb32r.dll      C:\Program Files\Common Files\System\Ole DB\oledb32r.dll 6.1.7600.16385
comsvcs.dll      C:\Windows\System32\comsvcs.dll    2001.12.8530.16385
cnxoledbprov.dll          C:\Windows\System32\cnxoledbprov.dll        11.0.0.10084
Connx32.dll      C:\Windows\System32\Connx32.dll    11.0.0.10084
mpr.dllC:\Windows\System32\mpr.dll           6.1.7600.16385
CNXSIS.dll        C:\Windows\System32\CNXSIS.dll      11.0.0.10084
winspool.drv    C:\Windows\System32\winspool.drv  6.1.7601.17514
icudt36.dll        C:\Windows\System32\icudt36.dll      3.6.0.0
inetmib1.dll      C:\Windows\System32\inetmib1.dll    6.1.7601.17514
snmpapi.dll      C:\Windows\System32\snmpapi.dll    6.1.7600.16385
DBGHELP.DLL   D:\SQLServer\MSSQL10_50.DECRI\MSSQL\Binn\DBGHELP.DLL6.8.4.0
odbccp32.dll    C:\Windows\System32\odbccp32.dll  6.1.7601.17632
CNXSQLITE.DLL           C:\Windows\System32\CNXSQLITE.DLL          11.0.0.10084
oleacc.dll          C:\Windows\System32\oleacc.dll        7.0.0.0
RpcRtRemote.dll          C:\Windows\System32\RpcRtRemote.dll        6.1.7601.17514
nlaapi.dll           C:\Windows\System32\nlaapi.dll         6.1.7601.17964
NapiNSP.dll       C:\Windows\System32\NapiNSP.dll     6.1.7600.16385
winrnr.dll          C:\Windows\System32\winrnr.dll        6.1.7600.16385
xpsqlbot.dll      D:\SQLServer\MSSQL10_50.DECRI\MSSQL\Binn\xpsqlbot.dll   2009.100.1600.1
xplog70.dll       D:\SQLServer\MSSQL10_50.DECRI\MSSQL\Binn\xplog70.dll    2009.100.1600.1
xplog70.rll        D:\SQLServer\MSSQL10_50.DECRI\MSSQL\Binn\Resources\1033\xplog70.rll  2009.100.1600.1
mscorwks.dll    C:\Windows\Microsoft.NET\Framework64\v2.0.50727\mscorwks.dll   2.0.50727.5472
mscorlib.ni.dll           C:\Windows\assembly\NativeImages_v2.0.50727_64\mscorlib\88744044294787b99dd4a8704ab75a79\mscorlib.ni.dll           2.0.50727.5472
mscorsec.dll    C:\Windows\Microsoft.NET\Framework64\v2.0.50727\mscorsec.dll   2.0.50727.4927
wintrust.dll       C:\Windows\System32\wintrust.dll     6.1.7601.17940
imagehlp.dll     C:\Windows\System32\imagehlp.dll   6.1.7601.17787
gpapi.dll           C:\Windows\System32\gpapi.dll         6.1.7600.16385
cryptnet.dll      C:\Windows\System32\cryptnet.dll    6.1.7601.18151
SensApi.dll       C:\Windows\System32\SensApi.dll     6.1.7600.16385
SqlAccess.dll    D:\SQLServer\MSSQL10_50.DECRI\MSSQL\Binn\SqlAccess.dll 2009.100.4000.0
mscorjit.dll       C:\Windows\Microsoft.NET\Framework64\v2.0.50727\mscorjit.dll      2.0.50727.5467
System.Data.dll           C:\Windows\assembly\GAC_64\System.Data\2.0.0.0__b77a5c561934e089\System.Data.dll           2.0.50727.5420
System.ni.dll           C:\Windows\assembly\NativeImages_v2.0.50727_64\System\6fa18e5d118c3aaffe0e379bf4b8eb08\System.ni.dll           2.0.50727.5467
System.Transactions.dll           C:\Windows\assembly\GAC_64\System.Transactions\2.0.0.0__b77a5c561934e089\System.Transactions.dll           2.0.50727.4927
System.Security.ni.dll           C:\Windows\assembly\NativeImages_v2.0.50727_64\System.Security\a9fcf4414d435ae305d2edd1d90f7597\System.Security.ni.dll           2.0.50727.5469
System.dll        C:\Windows\assembly\GAC_MSIL\System\2.0.0.0__b77a5c561934e089\System.dll 2.0.50727.5467
System.Security.dll           C:\Windows\assembly\GAC_MSIL\System.Security\2.0.0.0__b03f5f7f11d50a3a\System.Security.dll           2.0.50727.5469
System.Xml.dllC:\Windows\assembly\GAC_MSIL\System.Xml\2.0.0.0__b77a5c561934e089\System.Xml.dll           2.0.50727.5473
System.Configuration.dll           C:\Windows\assembly\GAC_MSIL\System.Configuration\2.0.0.0__b03f5f7f11d50a3a\System.Configuration.dll           2.0.50727.5473
GdiPlus.dll           C:\Windows\winsxs\amd64_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.18120_none_2b25b14c71ebf230\GdiPlus.dll           6.1.7601.18120
WindowsCodecs.dll      C:\Windows\System32\WindowsCodecs.dll    6.2.9200.16583
dsrole.dll          C:\Windows\System32\dsrole.dll        6.1.7600.16385
dbghelp.dll       C:\Program Files\Microsoft SQL Server\100\Shared\dbghelp.dll          6.8.4.0<o:p></o:p>

I've found several similar questions in this forum, but none of the answers have resolved my problem: I have a SQL Server 2012 DB using simple recovery model.  The MDF file is 12 GB and the LDF file is 10 GB.  I'm trying to shrink the size of the LDF file.  I've read that for simple recovery model DBs there are reasons for delaying log file shrinking, but I still can't find a solution based on these reasons.

When I try to shrink it using this command:

DBCC SHRINKFILE(MyDB_log, 1000000)

I get these results, and no change of file size:

DbId	FileId	CurrentSize	MinimumSize	UsedPages	EstimatedPages
8	2	1241328	128	1241328	128

The same results running this:

DBCC SHRINKFILE(MyDB_log, 1000000, TRUNCATEONLY)

There doesn't appear to be any open transactions:

DBCC OPENTRAN()
No active open transactions.
DBCC execution completed. If DBCC printed error messages, contact your system administrator.

And this returns NOTHING:

SELECT name, database_id, log_reuse_wait_desc FROM sys.databases WHERE database_id = DB_ID()
name	database_id	log_reuse_wait_desc
MyDB	8	NOTHING

I've also tried running the following, but nothing useful is returned:

SELECT * FROM sys.dm_tran_database_transactions
SELECT * FROM sys.dm_exec_requests WHERE database_id=DB_ID()
SELECT * FROM sys.dm_tran_locks WHERE resource_database_id=DB_ID()

Any other suggestions of what I can do to shrink this log file?  Or perhaps someone can justify its enormous size?

David Collacott

alter database [test-db] set single_user with rollback immediate;   --This sql is run using test-db
use master;restore database [test-db] from database_snapshot = 'snapshot_test-db';
alter database [test-db] set multi_user;

After switching the test-db to single user mode some 4-5 background processes of Taskmanager jump in for the test-db kicking off the session that application has taken over in single user mode . These background process are deadlocked between them selves. Please refer to the output of sp_who2 below at link.

http://social.microsoft.com/Forums/getfile/200625

and following is the deadlock XML.

NOTE: SPIDs in deadlock XML may differ from the output of sp_who2 as spids keeps on changing for these processes.

<deadlock-list><deadlock victim="process4bbfc78"><process-list><process id="process4bbfc78" taskpriority="0" logused="10000" waitresource="DATABASE: 5 " waittime="705" schedulerid="1" kpid="1648" status="background" spid="22" sbid="0" ecid="0" priority="0" trancount="0"><executionStack/><inputbuf></inputbuf></process><process id="process6d44388" taskpriority="0" logused="10000" waitresource="DATABASE: 5 " waittime="419" schedulerid="1" kpid="5796" status="background" spid="30" sbid="0" ecid="0" priority="0" trancount="0"><executionStack/><inputbuf></inputbuf></process><process id="process6d44718" taskpriority="0" logused="10000" waitresource="DATABASE: 5 " waittime="109" schedulerid="1" kpid="3908" status="background" spid="16" sbid="0" ecid="0" priority="0" trancount="0"><executionStack/><inputbuf></inputbuf></process><process id="process4bbee38" taskpriority="0" logused="10000" waitresource="DATABASE: 5 " waittime="313" schedulerid="1" kpid="2656" status="background" spid="15" sbid="0" ecid="0" priority="0" trancount="0"><executionStack/><inputbuf></inputbuf></process></process-list><resource-list><databaselock subresource="FULL" dbid="5" dbname="unknown" id="lock4671600" mode="S"><owner-list><owner id="process6d44718" mode="S"/><owner id="process4bbee38" mode="S"/></owner-list><waiter-list><waiter id="process4bbfc78" mode="X" requestType="wait"/></waiter-list></databaselock><databaselock subresource="FULL" dbid="5" dbname="unknown" id="lock4671600" mode="S"><owner-list><owner id="process4bbfc78" mode="S"/></owner-list><waiter-list><waiter id="process6d44388" mode="X" requestType="wait"/></waiter-list></databaselock><databaselock subresource="FULL" dbid="5" dbname="unknown" id="lock4671600" mode="S"><owner-list><owner id="process4bbfc78" mode="S"/></owner-list><waiter-list><waiter id="process6d44718" mode="X" requestType="wait"/></waiter-list></databaselock><databaselock subresource="FULL" dbid="5" dbname="unknown" id="lock4671600" mode="S"><owner-list><owner id="process4bbfc78" mode="S"/></owner-list><waiter-list><waiter id="process4bbee38" mode="X" requestType="wait"/></waiter-list></databaselock></resource-list></deadlock></deadlock-list>

I also made sure that SQL Server Agent is not running. The SQL services running on server are SQL server, SQL Server Browser and SQL Server VSS Writer.

Any help will be appreciated as this is a blocker problem.

Thanks,

Hi,

When I unpack a Data Tier Application (dacpac) I receive the error message “DACPAC version 2.5 is not supported”.

The dacpac I’m using is being built by Team Found Server 12 (build 12.0.21005.1) which is a RTM version. This problem was experienced in the CTP release of TFS but this should have been fixed in the RTM. Does anyone know how to resolve this?

Information on the CTP problem is detailed here:

http://social.msdn.microsoft.com/Forums/sqlserver/en-US/25d25081-f99a-4952-a803-36fca782bebc/dacpac-version-25-is-not-supported?forum=ssdt

Thanks

Scenario: SQL Server 2005 is installed on server SQLSERV.  SQL Server Management Studio is installed on REMSUPP.  When I attempt to log in to server SQLSERV from host REMSUPP, everything works and I can navigate around in my database.  However, when I attempt to open a table, I receive the dreaded "A network-related or instance-specific error occurred while establishing a connection to SQL Server.  The server was not found or was not accessible ... (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)".

I don't understand the part where it says "The server was not found or was not accessible".  Clearly it is network accessible, or I wouldn't have been able to log into it.  On the server, remote connections are allowed, the database is up and operational, and when I log onto SQLSERV and attempt to open the same table, it opens. 

I've spent the morning researching this but getting nowhere, including reading existing articles on MS support site and following them step-by-step.  I've compared and contrasted settings on another SQL-server/support-host instance, and everything looks like it is configured the same.  "sqlcmd -L" run on REMSUPP lists the server I am having the problem with.  Firewalls are disabled, as this is an internal network with no Internet access. 

Can someone suggest what else I should be looking for?  Thanks in advance.