Hi

I had noticed a really strangle thing. INT calculation is 2-3-5 times slower in SQL server running in VMware than on physical machines. From VMware side, I had eliminated all possible things: balooning, CPU overconsumption, "ready" time etc. INT CPU tests (link 'Pi' digits calculation programs) show the same performance, while SQL server math operations are MUCH slower. 

Please check the test of few results on different machines. I am DBA for >20y, but I am really puzzled.

Test is simple, no parallelism, no IO, limited memory use (L2,L3 caching is irrelevant)

Results

create function dbo.isPrime (@n bigint)
returns int
as
  begin
  if @n = 1 return 0
  if @n = 2 return 1
  if @n = 3 return 1
  if @n % 2 = 0 return 0
  declare @sq int
  set @sq = sqrt(@n)+1 -- check odds up to sqrt
  declare @dv int = 1
  while @dv < @sq 
    begin
	set @dv=@dv+2
	if @n % @dv = 0 return 0
	end
  return 1
  end
GO
declare @dt datetime set @dt=getdate()
select dbo.isPrime(1000000000000037)
select datediff(ms,@dt,getdate()) as ms
GO

Hi we run 2017 std. I didn't know whether to post this in the ssis forum or here. The bottom line is that my test service acct has permissions to read on my sql server after we added it to the appropriate nt group. We proved this by having a dba with sa execute as 'domain\newacct' select...

The acct's creds originate in a 3rd party scheduling product.  The scheduler executes a powershell script on a different server.  That script executes a proc on sql server a which runs some ssis on sql server a that (amongst other things) contacts sql server b.  we see from the log on b that the login was as nt authority\anonymous logon.  the login failed because token-based server access validation failed with an infrastructure error.

Can someone explain what is happening and if there is a low footprint way to get around this?  there are actually 12 servers that the ssis on server a tries to connect to.

Its as if i'm getting at most 1 sql hop retaining my service acct's creds before they "get lost".  I wouldn't really want to store the acct's creds in ssis but I suppose if that's a last resort and ssis has a fool proof way of doing that, maybe it would work.

I can say this.  The ssis errors show that ssis knew the service acct was who ssis was running as.   

from a connection standpoint, the powershell script specifies nothing more than sql server a's name and the database where the proc is to be run from.

All,

I tried to create an External Data Source against another SQLServer (2016) from a SQLServer 2019 server but I get the below error:

<<External access operation failed because the location URI is invalid. Revise the URI and try again.>>

NYCSQL10.nydomain.net is a SQLServer 2016 server

Configure PolyBase to access external data in SQL Server

What am I missing?

Thanks,

rgn

I have a scenarios whereby a checkdb on an 800GB database was cancelled and 3 days later, there is sessions stuck in "killed/rollback" state.

I ran 

select blocking_session_id, wait_time,wait_type, last_wait_type, open_transaction_count, percent_complete,estimated_completion_time, cpu_time,total_elapsed_time, reads, writes, granted_query_memory, parallel_worker_count
FROM SYS.DM_EXEC_REQUESTS
where session_id in (66)

and i see the wait type is EXECSYNC,  percent complete 10,05694 and doesnt change, estimated completion time is rising, cpu_time is not changing, reads and writes are not changing either.   

I dont want to restart the Instance as i am afraid the database will go into recovery and it will take the same time to recover and users will not be able to access, for now, at least users can access but it is extremely slow. 

Will it eventually complete? or its hung ?

Any advice ? 

ilikefondue

I use 64-bit OS with two CPUs (each of them makes 7 logical processors) and with total number of logical processors equal to 14.

When I run this code I get 2048

SELECT max_workers_count FROM sys.dm_os_sys_info

On the other way, when I use the formula below I get totally different number which is 672

Can you explain to me why I get different numbers? I tested it on another server and got exact same numbers for both cases.

Hello,

       I have configured a SQL always on 2 Node cluster. I have a database which is functioning properly when its on Primary replica, but when the AG is on secondary replica it's stop working.

       Databases are available on both Node, but when I click show dashboard on Primary replica it says Availability group state ishealthy, but in secondary replica it says No data available on secondary replica.

       I have no idea to fix this issue, can someone help me with the details troubleshooting guide with some article reference.  

On SQL Server 2017 I have a cascading delete that always seeks the value from the secondary table unless the key value from the primary table is out of bounds of the histogram.  I thought in these cases the optimizer would utilize the density vector to determine % of unique values to determine if a scan or seek will occur.  If I write a direct delete statement from the secondary table it seeks.  I am 99% sure this is a bug.  I am at a total loss for why this would scan instead of seek (but just on out-of-bounds data, i.e. hot or cold data).  I also see this behavior with indexed views but have not had any luck finding an answer for that either.  I would appreciate any insight into why the cascade delete results in a scan for out-of-bounds key values.

Here are the query plans that result:  https://www.brentozar.com/pastetheplan/?id=BJz2-KjyI

Here is some SQL I wrote to quickly replicate the issue I am having in production:

What is TechNet Guru Competition?

Each month the TechNet Wiki council organizes a contest of the best articles posted that month. This is your chance to be announced as MICROSOFT TECHNOLOGY GURU OF THE MONTH!

One winner in each category will be selected each month for glory and adoration by the MSDN/TechNet Ninjas and community as a whole. Winners will be announced in dedicated blog post that will be published in Microsoft Wiki Ninjas blog, a tweet from the Wiki Ninjas Twitter account, links will be published at Microsoft TNWiki group on Facebook, and other acknowledgement from the community will follow.

Some of our biggest community voices and many MVPs have passed through these halls on their way to fame and fortune.

If you have already made a contribution in the forums or gallery or you published a nice blog, then you can simply convert it into a shared wiki article, reference the original post, and register the article for the TechNet Guru Competition. The articles must be written in January 2020 and must be in English. However, the original blog or forum content can be from beforeJanuary 2020.

Come and see who is making waves in all your favorite technologies. Maybe it will be you!

Who can join the Competition?

Anyone who has basic knowledge and the desire to share the knowledge is welcome. Articles can appeal to beginners or discusse advanced topics. All you have to do is to add your article to TechNet Wiki from your own specialty category.

How can you win?

1. Please copy/Write over your Microsoft technical solutions and revelations to TechNetWiki.
2. Add a link to your new article on THIS WIKI COMPETITION PAGE (so we know you've contributed)
3. (Optional but recommended) Add a link to your article at the TechNetWiki group on Facebook. The group is very active and people love to help, you can get feedback and even direct improvements in the article before the contest starts.

Do you have any question or want more information?

Feel free to ask any questions below, or Join us at the official MicrosoftTechNet Wiki groups on facebook. Read More about TechNet Guru Awards.

If you win, people will sing your praises online and your name will be raised as Guru of the Month.

Thanks,
Kamlesh Kumar

If my reply is helpful please mark as Answeror vote as Helpful.

My blog | Twitter | LinkedIn

I am trying to access CosmosDB document from SQL Server using PolyBase functionality with no success. Is anyone came across the issue.

--Successfully created the data source -- CREATE EXTERNAL DATA SOURCE Cosmosdb_odbc WITH ( LOCATION = 'odbc://WIN-ALO32Q0SFC2',        CONNECTION_OPTIONS = DocumentDB ODBC Driver}; DSN =cosmosdb''DRIVER={Microsoft Azure       )

--Successfully created External Table --

CREATE EXTERNAL TABLE Cosmosdb_odbc_test ( [Data_value]            BIGINT, [Group]                    NVARCHAR(255) COLLATE SQL_Latin1_General_CP1_CI_AS, [MAGNTUDE]                BIGINT, [Period]                FLOAT(53) ) WITH ( LOCATION='cosmosuatdb.ToDoList', DATA_SOURCE = Cosmosdb_odbc )

Getting the following error on accessing the external table in SSMS, the same error is recorded in the ODBC logs

Cannot execute the query "Remote Query" against OLE DB provider "SQLNCLI11" for linked server "(null)". 105082;Generic ODBC error: [Microsoft][DocumentDB] (10) Schema map entry for Table ToDoList could not be found. Check query syntax and schema map definition and try again .

ODBC Log Info

The 64-bit odbc driver for Cosmos db is installed, configured and able to access the document from SSMS using OpenRowSet

Hello,

Password required when adding database to availability group, take.ms/QC9FA

This database is encrypted by database master key, you need to provide valid password when adding it to the availability group.

But "SELECT * FROM sys.dm_database_encryption_keys" shows nothing about it.

How is that possible?

Thanks.

Любовь долготерпит, ...

Hi Everybody,

How can we track linked server usage?  We have users' adhoc queries, SSRS reports, SSIS queries, and stored procedures that use linked servers and we'd like to audit that activity to determine which linked servers can be eliminated.

Thanks,
Eric

Hello

I am trying to find out if there is a way to calculate the percentage of uptime for a given SQL Instance. I understand that there are queries to find out when SQL Server was started and for how long, but I am looking for a percentage calculation for how long the SQL Server was up in a given time window. I see one post here with a query supposed to do that, but the query fails with syntax errors.

https://forum.red-gate.com/discussion/78955/query-for-sql-uptime

Please assist.

Hi,

we have installed sql server 2016 standard edition.
developers want to debug the stored procedure. In the management studio we didn't see 'Debug' option at all. I tried add remove button but nothing working. Please help me to add the debug option in sql server 2016 management studio.

Thanks,
Jo

pols

Warm regards MeVs

Hi

we have serverA (windows 2019 , sql 2016 ent) as publication ,

server B (windows 2019 , sql 2016 ent ) subscriber 1, 

server c (windows 2016 , sql 2016 std) subscriber 2, 

now we are going to migrate sql 2019 for all servers.  

• how to accomplish this ? 
• In-place upgrade ? possible?
• Replication need to stop or remove before migration?
  

Hi we run 2017 std. sometimes I want a pk to be an identity column and with frequent truncates would prefer automatically rolling the column (say back to 1) when the max value is hit. Rather than setting the col's characteristic to bigint. Is there such a feature available in sql server?

I wouldn't want to give the service acct permission to reseed values.

SQL 2008 Standard edition, roughly 250 databases on the server (though this problem has occurred with all but one offline)

A client's SQL server is logging Non-yielding Scheduler errors and generating a minidump around the same times daily.  These are logged repeatedly and the kernel time increases slightly each time.  There is no noticable spike in CPU/memory load, however, and the only hardware bottleneck we were seeing at the time was disk IO on the log drive (SAN).   Those drives were upgraded and the iops, % disk time and disk queue length have dropped to reasonable levels, but the non-yielding errors persist.  These errors also correspond with intermittent connection issues, which log errors like "The client was unable to reuse a session with SPID 153, which had been reset for connection pooling",  that usually persist for about an hour and clear up on their own.  

The things I've read on the error point to log IO issues but I cant confirm thats the case based on any stats in perfmon or on the SAN itself.  We have not been able to consistently replicate the problem and it doesn't always happen each day, but the times are consistent between occurrances.  I've ruled out any SQL jobs running at these times, and in the example below the only thing happening before hand was a CheckDB job.  I have little visibility into what the application is doing when this occurs and I'm not entirely sure what to even look for for a cause from that end. 

Examples from the log are included below.  Has anyone run into this before that can offer any suggestions for a possible cause?

2011-01-11 00:00:04.25 spid21s     This instance of SQL Server has been using a process ID of 2068 since 1/10/2011 10:17:43 PM (local) 1/11/2011 3:17:43 AM (UTC). This is an informational message only; no user action is required.

2011-01-11 00:00:20.18 spid181     DBCC CHECKDB (dbname1) WITH physical_only executed by DOMAIN\UserA found 0 errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 33 seconds.  Internal database snapshot has split point LSN = 0004f06e:0000007e:0001 and first LSN = 0004f06e:0000007d:0001.

2011-01-11 00:00:39.57 spid181     DBCC CHECKDB (dbname2) WITH physical_only executed by DOMAIN\UserA found 0 errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 12 seconds.  Internal database snapshot has split point LSN = 000008da:00000022:0001 and first LSN = 000008da:00000021:0001.

2011-01-11 00:00:51.49 spid181     6 transactions rolled forward in database 'dbname' (10). This is an informational message only. No user action is required.

2011-01-11 00:00:51.56 spid181     0 transactions rolled back in database 'dbname' (10). This is an informational message only. No user action is required.

2011-01-11 00:01:12.21 Server      Using 'dbghelp.dll' version '4.0.5'

2011-01-11 00:01:12.44 Server      ***Unable to get thread context for spid 0

2011-01-11 00:01:12.44 Server      * *******************************************************************************

2011-01-11 00:01:12.44 Server      *

2011-01-11 00:01:12.44 Server      * BEGIN STACK DUMP:

2011-01-11 00:01:12.44 Server      *   01/11/11 00:01:12 spid 2656

2011-01-11 00:01:12.44 Server      *

2011-01-11 00:01:12.44 Server      * Non-yielding Scheduler

2011-01-11 00:01:12.44 Server      *

2011-01-11 00:01:12.44 Server      * *******************************************************************************

2011-01-11 00:01:12.44 Server      Stack Signature for the dump is 0x00000221

2011-01-11 00:01:15.62 Server      External dump process return code 0x20000001.

External dump process returned no errors.

2011-01-11 00:01:15.62 Server      Process 0:0:0 (0xa68) Worker 0x00EDE0D8 appears to be non-yielding on Scheduler 2. Thread creation time: 12939189420203. Approx Thread CPU Used: kernel 78 ms, user 31 ms. Process Utilization 4%. System Idle 91%. Interval: 70109 ms.

2011-01-11 00:01:36.97 spid181     DBCC CHECKDB (dbname3) WITH physical_only executed by DOMAIN\UserA found 0 errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 49 seconds.  Internal database snapshot has split point LSN = 0007bf21:00000065:0006 and first LSN = 0007bf21:0000005c:0007.

2011-01-11 00:02:01.10 spid181     DBCC CHECKDB (dbname4) WITH physical_only executed by DOMAIN\UserA found 0 errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 16 seconds.  Internal database snapshot has split point LSN = 0000054c:00000028:0001 and first LSN = 0000054c:00000027:0001.

2011-01-11 00:02:15.67 Server      Process 0:0:0 (0xa68) Worker 0x00EDE0D8 appears to be non-yielding on Scheduler 2. Thread creation time: 12939189420203. Approx Thread CPU Used: kernel 93 ms, user 62 ms. Process Utilization 4%. System Idle 93%. Interval: 133625 ms.

2011-01-11 00:02:39.11 spid181     5 transactions rolled forward in database 'dbname6' (10). This is an informational message only. No user action is required.

2011-01-11 00:02:39.12 spid181     0 transactions rolled back in database 'dbname6' (10). This is an informational message only. No user action is required.

2011-01-11 00:03:15.71 Server      Process 0:0:0 (0xa68) Worker 0x00EDE0D8 appears to be non-yielding on Scheduler 2. Thread creation time: 12939189420203. Approx Thread CPU Used: kernel 109 ms, user 62 ms. Process Utilization 4%. System Idle 93%. Interval: 193656 ms.

2011-01-11 00:03:44.50 spid181     DBCC CHECKDB (dbname5) WITH physical_only executed by DOMAIN\UserA found 0 errors and repaired 0 errors. Elapsed time: 0 hours 1 minutes 17 seconds.  Internal database snapshot has split point LSN = 0004ac9c:00000188:000a and first LSN = 0004ac9c:00000182:0004.

2011-01-11 00:04:15.75 Server      Process 0:0:0 (0xa68) Worker 0x00EDE0D8 appears to be non-yielding on Scheduler 2. Thread creation time: 12939189420203. Approx Thread CPU Used: kernel 125 ms, user 78 ms. Process Utilization 4%. System Idle 94%. Interval: 253703 ms.

2011-01-11 00:05:15.79 Server      Process 0:0:0 (0xa68) Worker 0x00EDE0D8 appears to be non-yielding on Scheduler 2. Thread creation time: 12939189420203. Approx Thread CPU Used: kernel 171 ms, user 125 ms. Process Utilization 3%. System Idle 94%. Interval: 313750 ms.

2011-01-11 00:06:15.83 Server      Process 0:0:0 (0xa68) Worker 0x00EDE0D8 appears to be non-yielding on Scheduler 2. Thread creation time: 12939189420203. Approx Thread CPU Used: kernel 203 ms, user 140 ms. Process Utilization 3%. System Idle 95%. Interval: 373781 ms.

2011-01-11 00:06:50.12 spid582     Error: 18056, Severity: 20, State: 29.

2011-01-11 00:06:50.12 spid582     The client was unable to reuse a session with SPID 582, which had been reset for connection pooling. The failure ID is 29. This error may have been caused by an earlier operation failing. Check the error logs for failed operations immediately before this error message.

2011-01-11 00:07:15.87 Server      Process 0:0:0 (0xa68) Worker 0x00EDE0D8 appears to be non-yielding on Scheduler 2. Thread creation time: 12939189420203. Approx Thread CPU Used: kernel 250 ms, user 187 ms. Process Utilization 2%. System Idle 95%. Interval: 433828 ms.

2011-01-11 00:08:15.92 Server      Process 0:0:0 (0xa68) Worker 0x00EDE0D8 appears to be non-yielding on Scheduler 2. Thread creation time: 12939189420203. Approx Thread CPU Used: kernel 250 ms, user 234 ms. Process Utilization 2%. System Idle 96%. Interval: 493875 ms.

2011-01-11 00:09:15.96 Server      Process 0:0:0 (0xa68) Worker 0x00EDE0D8 appears to be non-yielding on Scheduler 2. Thread creation time: 12939189420203. Approx Thread CPU Used: kernel 375 ms, user 328 ms. Process Utilization 2%. System Idle 96%. Interval: 553906 ms.

2011-01-11 00:10:16.00 Server      Process 0:0:0 (0xa68) Worker 0x00EDE0D8 appears to be non-yielding on Scheduler 2. Thread creation time: 12939189420203. Approx Thread CPU Used: kernel 437 ms, user 406 ms. Process Utilization 2%. System Idle 96%. Interval: 613953 ms.

2011-01-11 00:11:16.04 Server      Process 0:0:0 (0xa68) Worker 0x00EDE0D8 appears to be non-yielding on Scheduler 2. Thread creation time: 12939189420203. Approx Thread CPU Used: kernel 515 ms, user 421 ms. Process Utilization 2%. System Idle 96%. Interval: 674000 ms.

2011-01-11 00:12:16.07 Server      Process 0:0:0 (0xa68) Worker 0x00EDE0D8 appears to be non-yielding on Scheduler 2. Thread creation time: 12939189420203. Approx Thread CPU Used: kernel 609 ms, user 437 ms. Process Utilization 2%. System Idle 96%. Interval: 734031 ms.

2011-01-11 00:13:16.12 Server      Process 0:0:0 (0xa68) Worker 0x00EDE0D8 appears to be non-yielding on Scheduler 2. Thread creation time: 12939189420203. Approx Thread CPU Used: kernel 625 ms, user 484 ms. Process Utilization 2%. System Idle 96%. Interval: 794078 ms.

2011-01-11 00:14:16.17 Server      Process 0:0:0 (0xa68) Worker 0x00EDE0D8 appears to be non-yielding on Scheduler 2. Thread creation time: 12939189420203. Approx Thread CPU Used: kernel 687 ms, user 500 ms. Process Utilization 2%. System Idle 96%. Interval: 854125 ms.

2011-01-11 00:15:16.20 Server      Process 0:0:0 (0xa68) Worker 0x00EDE0D8 appears to be non-yielding on Scheduler 2. Thread creation time: 12939189420203. Approx Thread CPU Used: kernel 718 ms, user 531 ms. Process Utilization 2%. System Idle 97%. Interval: 914156 ms.

2011-01-11 00:16:16.25 Server      Process 0:0:0 (0xa68) Worker 0x00EDE0D8 appears to be non-yielding on Scheduler 2. Thread creation time: 12939189420203. Approx Thread CPU Used: kernel 734 ms, user 562 ms. Process Utilization 1%. System Idle 97%. Interval: 974203 ms.

2011-01-11 00:17:16.29 Server      Process 0:0:0 (0xa68) Worker 0x00EDE0D8 appears to be non-yielding on Scheduler 2. Thread creation time: 12939189420203. Approx Thread CPU Used: kernel 734 ms, user 593 ms. Process Utilization 1%. System Idle 97%. Interval: 1034234 ms.

2011-01-11 00:18:16.32 Server      Process 0:0:0 (0xa68) Worker 0x00EDE0D8 appears to be non-yielding on Scheduler 2. Thread creation time: 12939189420203. Approx Thread CPU Used: kernel 765 ms, user 671 ms. Process Utilization 1%. System Idle 97%. Interval: 1094281 ms.

2011-01-11 00:19:16.37 Server      Process 0:0:0 (0xa68) Worker 0x00EDE0D8 appears to be non-yielding on Scheduler 2. Thread creation time: 12939189420203. Approx Thread CPU Used: kernel 796 ms, user 703 ms. Process Utilization 1%. System Idle 97%. Interval: 1154328 ms.

2011-01-11 00:20:16.40 Server      Process 0:0:0 (0xa68) Worker 0x00EDE0D8 appears to be non-yielding on Scheduler 2. Thread creation time: 12939189420203. Approx Thread CPU Used: kernel 890 ms, user 718 ms. Process Utilization 1%. System Idle 97%. Interval: 1214359 ms.

2011-01-11 00:21:16.46 Server      Process 0:0:0 (0xa68) Worker 0x00EDE0D8 appears to be non-yielding on Scheduler 2. Thread creation time: 12939189420203. Approx Thread CPU Used: kernel 953 ms, user 796 ms. Process Utilization 1%. System Idle 97%. Interval: 1274406 ms.

2011-01-11 00:22:16.50 Server      Process 0:0:0 (0xa68) Worker 0x00EDE0D8 appears to be non-yielding on Scheduler 2. Thread creation time: 12939189420203. Approx Thread CPU Used: kernel 1093 ms, user 828 ms. Process Utilization 1%. System Idle 97%. Interval: 1334453 ms.

2011-01-11 00:23:16.54 Server      Process 0:0:0 (0xa68) Worker 0x00EDE0D8 appears to be non-yielding on Scheduler 2. Thread creation time: 12939189420203. Approx Thread CPU Used: kernel 1203 ms, user 875 ms. Process Utilization 1%. System Idle 97%. Interval: 1394500 ms.

2011-01-11 00:24:16.58 Server      Process 0:0:0 (0xa68) Worker 0x00EDE0D8 appears to be non-yielding on Scheduler 2. Thread creation time: 12939189420203. Approx Thread CPU Used: kernel 1265 ms, user 953 ms. Process Utilization 1%. System Idle 97%. Interval: 1454531 ms.

2011-01-11 00:25:16.62 Server      Process 0:0:0 (0xa68) Worker 0x00EDE0D8 appears to be non-yielding on Scheduler 2. Thread creation time: 12939189420203. Approx Thread CPU Used: kernel 1421 ms, user 953 ms. Process Utilization 1%. System Idle 97%. Interval: 1514578 ms.

2011-01-11 00:26:16.67 Server      Process 0:0:0 (0xa68) Worker 0x00EDE0D8 appears to be non-yielding on Scheduler 2. Thread creation time: 12939189420203. Approx Thread CPU Used: kernel 1609 ms, user 1046 ms. Process Utilization 2%. System Idle 97%. Interval: 1574625 ms.

2011-01-11 00:27:16.71 Server      Process 0:0:0 (0xa68) Worker 0x00EDE0D8 appears to be non-yielding on Scheduler 2. Thread creation time: 12939189420203. Approx Thread CPU Used: kernel 1703 ms, user 1093 ms. Process Utilization 2%. System Idle 97%. Interval: 1634671 ms.

2011-01-11 00:28:16.75 Server      Process 0:0:0 (0xa68) Worker 0x00EDE0D8 appears to be non-yielding on Scheduler 2. Thread creation time: 12939189420203. Approx Thread CPU Used: kernel 1750 ms, user 1140 ms. Process Utilization 2%. System Idle 97%. Interval: 1694703 ms.

2011-01-11 00:29:16.79 Server      Process 0:0:0 (0xa68) Worker 0x00EDE0D8 appears to be non-yielding on Scheduler 2. Thread creation time: 12939189420203. Approx Thread CPU Used: kernel 1812 ms, user 1250 ms. Process Utilization 2%. System Idle 96%. Interval: 1754750 ms.

2011-01-11 00:30:16.83 Server      Process 0:0:0 (0xa68) Worker 0x00EDE0D8 appears to be non-yielding on Scheduler 2. Thread creation time: 12939189420203. Approx Thread CPU Used: kernel 1875 ms, user 1281 ms. Process Utilization 2%. System Idle 97%. Interval: 1814796 ms.

2011-01-11 00:31:16.88 Server      Process 0:0:0 (0xa68) Worker 0x00EDE0D8 appears to be non-yielding on Scheduler 2. Thread creation time: 12939189420203. Approx Thread CPU Used: kernel 2000 ms, user 1359 ms. Process Utilization 2%. System Idle 96%. Interval: 1874843 ms.

2011-01-11 00:32:16.92 Server      Process 0:0:0 (0xa68) Worker 0x00EDE0D8 appears to be non-yielding on Scheduler 2. Thread creation time: 12939189420203. Approx Thread CPU Used: kernel 2093 ms, user 1437 ms. Process Utilization 2%. System Idle 96%. Interval: 1934875 ms.

2011-01-11 00:33:16.97 Server      Process 0:0:0 (0xa68) Worker 0x00EDE0D8 appears to be non-yielding on Scheduler 2. Thread creation time: 12939189420203. Approx Thread CPU Used: kernel 2171 ms, user 1484 ms. Process Utilization 2%. System Idle 96%. Interval: 1994921 ms.

2011-01-11 00:34:17.00 Server      Process 0:0:0 (0xa68) Worker 0x00EDE0D8 appears to be non-yielding on Scheduler 2. Thread creation time: 12939189420203. Approx Thread CPU Used: kernel 2359 ms, user 1562 ms. Process Utilization 2%. System Idle 96%. Interval: 2054968 ms.

2011-01-11 00:35:17.05 Server      Process 0:0:0 (0xa68) Worker 0x00EDE0D8 appears to be non-yielding on Scheduler 2. Thread creation time: 12939189420203. Approx Thread CPU Used: kernel 2531 ms, user 1671 ms. Process Utilization 2%. System Idle 96%. Interval: 2115000 ms.

2011-01-11 00:36:17.08 Server      Process 0:0:0 (0xa68) Worker 0x00EDE0D8 appears to be non-yielding on Scheduler 2. Thread creation time: 12939189420203. Approx Thread CPU Used: kernel 2687 ms, user 1718 ms. Process Utilization 2%. System Idle 96%. Interval: 2175046 ms.

2011-01-11 00:37:17.13 Server      Process 0:0:0 (0xa68) Worker 0x00EDE0D8 appears to be non-yielding on Scheduler 2. Thread creation time: 12939189420203. Approx Thread CPU Used: kernel 2734 ms, user 1812 ms. Process Utilization 2%. System Idle 96%. Interval: 2235093 ms.

2011-01-11 00:38:17.17 Server      Process 0:0:0 (0xa68) Worker 0x00EDE0D8 appears to be non-yielding on Scheduler 2. Thread creation time: 12939189420203. Approx Thread CPU Used: kernel 2796 ms, user 1859 ms. Process Utilization 2%. System Idle 96%. Interval: 2295125 ms.

2011-01-11 00:39:17.21 Server      Process 0:0:0 (0xa68) Worker 0x00EDE0D8 appears to be non-yielding on Scheduler 2. Thread creation time: 12939189420203. Approx Thread CPU Used: kernel 2875 ms, user 1906 ms. Process Utilization 2%. System Idle 96%. Interval: 2355171 ms.

2011-01-11 00:40:17.26 Server      Process 0:0:0 (0xa68) Worker 0x00EDE0D8 appears to be non-yielding on Scheduler 2. Thread creation time: 12939189420203. Approx Thread CPU Used: kernel 3000 ms, user 1968 ms. Process Utilization 2%. System Idle 96%. Interval: 2415218 ms.

2011-01-11 00:41:17.31 Server      Process 0:0:0 (0xa68) Worker 0x00EDE0D8 appears to be non-yielding on Scheduler 2. Thread creation time: 12939189420203. Approx Thread CPU Used: kernel 3140 ms, user 2031 ms. Process Utilization 2%. System Idle 96%. Interval: 2475250 ms.

2011-01-11 00:42:17.35 Server      Process 0:0:0 (0xa68) Worker 0x00EDE0D8 appears to be non-yielding on Scheduler 2. Thread creation time: 12939189420203. Approx Thread CPU Used: kernel 3203 ms, user 2109 ms. Process Utilization 2%. System Idle 96%. Interval: 2535296 ms.

2011-01-11 00:42:38.20 spid153     Error: 18056, Severity: 20, State: 29.

2011-01-11 00:42:38.20 spid153     The client was unable to reuse a session with SPID 153, which had been reset for connection pooling. The failure ID is 29. This error may have been caused by an earlier operation failing. Check the error logs for failed operations immediately before this error message.

2011-01-11 00:42:38.20 spid163     Error: 18056, Severity: 20, State: 29.

2011-01-11 00:42:38.20 spid163     The client was unable to reuse a session with SPID 163, which had been reset for connection pooling. The failure ID is 29. This error may have been caused by an earlier operation failing. Check the error logs for failed operations immediately before this error message.

2011-01-11 00:42:38.20 spid268     Error: 18056, Severity: 20, State: 29.

2011-01-11 00:42:38.20 spid268     The client was unable to reuse a session with SPID 268, which had been reset for connection pooling. The failure ID is 29. This error may have been caused by an earlier operation failing. Check the error logs for failed operations immediately before this error message.

2011-01-11 00:42:38.23 spid134     Error: 18056, Severity: 20, State: 29.

2011-01-11 00:42:38.23 spid134     The client was unable to reuse a session with SPID 134, which had been reset for connection pooling. The failure ID is 29. This error may have been caused by an earlier operation failing. Check the error logs for failed operations immediately before this error message.

2011-01-11 00:42:38.23 spid160     Error: 18056, Severity: 20, State: 29.

2011-01-11 00:42:38.23 spid160     The client was unable to reuse a session with SPID 160, which had been reset for connection pooling. The failure ID is 29. This error may have been caused by an earlier operation failing. Check the error logs for failed operations immediately before this error message.

2011-01-11 00:42:38.23 spid166     Error: 18056, Severity: 20, State: 29.

etc...

I'm using SQL Server 2008 R2.  Event ID 4625 is logged on Windows Security logs for every 30 minute but nothing is logged on SQL Server logs.

This is from the General tab of Windows Security logs:

An account failed to log on.

Subject:
 Security ID:  SYSTEM
 Account Name:  TEST$
 Account Domain:  XXX
 Logon ID:  0x3e7

Logon Type:   3

Account For Which Logon Failed:
 Security ID:  NULL SID
 Account Name:  
 Account Domain:  

Failure Information:
 Failure Reason:  The specified user account has expired.
 Status:   0xc0000193
 Sub Status:  0xc0000193

Process Information:
 Caller Process ID: 0xab4
 Caller Process Name: C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\sqlservr.exe

Network Information:
 Workstation Name: TEST
 Source Network Address: -
 Source Port:  -

Detailed Authentication Information:
 Logon Process:  Authz  
 Authentication Package: Kerberos
 Transited Services: -
 Package Name (NTLM only): -
 Key Length:  0

This event is generated when a logon request fails. It is generated on the computer where access was attempted.

The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.

The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).

The Process Information fields indicate which account and process on the system requested the logon.

The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.

The authentication information fields provide detailed information about this specific logon request.
 - Transited services indicate which intermediate services have participated in this logon request.
 - Package name indicates which sub-protocol was used among the NTLM protocols.
 - Key length indicates the length of the generated session key. This will be 0 if no session key was requested.

This is from the Details tab of Windows Security logs:

Can this be related to the owner of some databases in that instance that has expired password?  However, I really doubt that since there is another sql instance which also has some databases owned by the same owner and there is nothing logged in Windows Security logs for that instance.