Reputation
Top tag
Next privilege 200 Rep.
See reduced ads
Badges
7
Newest
 Critic
Impact
~852 people reached

Feb
17
comment SQL server service won’t start after disabling TLS 1.0 and SSL 3.0
@SeanGallardy - Thanks guys.
Feb
17
comment SQL server service won’t start after disabling TLS 1.0 and SSL 3.0
Matt, right you are, I actually rather wanted to link this blog. Still same question to you. Which SQL Server version are you commenting on?
Feb
17
comment SQL server service won’t start after disabling TLS 1.0 and SSL 3.0
@Mat - This resource explicitly says that SQL Server 2008 R2 supports TLS 1.1. Was the "escalation engineer" talking about any specific SQL Server version or generally?
Jun
5
comment Connecting to SQL Server using cached credentials
Thank you for the extra info. We will go the local account way and maybe even buy your book :-)
Jun
5
comment Why do we have SHRINKDATABASE command in SQL Server
And, regarding the bloated LDF file, shrinkdatabase usually doesn't even work alone because of how virtual logs are allocated and rotated. (I found out I had to simulate some "load" while repeatedly shrinking.) technet.microsoft.com/en-us/magazine/2009.02.logging.aspx
Jun
4
comment Connecting to SQL Server using cached credentials
I get that. But you are saying that when AD is online, the service can log on, but no credentials will be cached for later use, because this particular log on is not interactive. Correct?
Jun
4
comment Connecting to SQL Server using cached credentials
This was the key bit of info I was missing. Can you please confirm my understanding? Suppose that I create a domain account that is allowed to log on interactively. Then credential caching will happen as configured when this user logs on as a normal user; but if I try to use the same account as a service logon account, such a service startup or database authentication will never result in caching the credentials in registry. Is that correct?
Jun
4
comment Connecting to SQL Server using cached credentials
@JonSeigel - Unfortunately not. All domain accounts have this problem (NETWORKSERVICE translates to the computer account). In fact we are considering to use a local non-domain account which is obviously a step back from security but a less drastic one than removing the whole system from the domain.