« first day (3233 days earlier)      last day (106 days later) » 

7:03 AM
Good Morning
 
7:42 AM
Moaning
 
8:10 AM
Morning
 
8:29 AM
> SQL Server 2019 now has shorter lines for the public toilet.
 
 
1 hour later…
9:31 AM
Morning
 
Morning
 
10:29 AM
It horrifies me every time I see a terrible question on this site that is clearly about stock trading or something else heavily financial. If you care about your data, and therefore money, spend a bit more on your employees and hire the right people?
 
 
2 hours later…
12:40 PM
@Philᵀᴹ And I absolutely love shorties:
0
Q: login not having permission to see sql server properties

venkatI need a login and that login should not view the sql server properties i.e.,login should not have permission to execute command select @@version

that's all there is
 
12:53 PM
Easy: allow no SELECT at all. Even better, allow no access to SQL Server ;)
 
1:04 PM
If they were trying to keep the version secret, they messed up by adding the tag
SQL Server 2012 is quite old, but I'm not sure it's embarrassingly so
 
1:23 PM
I think to me SQL Server 2000 seemed old in 2007 to a greater degree than SQL Server 2012 does now, even though it was the penultimate version at the time, unlike the 2012 now.
 
Hint: 2008 R2
 
Hmm, I'm willing to take the hint but I can't quite get it
 
I thought 2008 R2 was the best SQL Server version out there, and it somehow never seemed to age at the time. Was still going strong until last year (2018).
 
1:46 PM
@Philᵀᴹ They are often offshore "resources" of which the actual client knows nothing.
 
@Philᵀᴹ Allo Allo
 
2:10 PM
@Johnakahot2use Was stuck on 2008R2 in my previous gig
Was no point upgrading it, as we were binning SAP off
 
2:50 PM
@Philᵀᴹ hip-ray, hip-ray, hip-ray
Quick question: Does anybody know of a summary of CUxx for SQL Server 2016 and what they do/did?
I'm still banging around with a database that is (apparently) performing bad since we moved it to SQL Server 2016
Wouldn't you with 97% adhoc plans?
Anyhow, I've seen that the latest CU10 has some fixes regarding performance issues with tables with covering indexes:
> FIX: Poor query performance due to low cardinality estimation in SQL Server 2016 when you use default CE and column is covered by both single and multi-column statistics
Or would I have to search each individual CUxx?
 
 
3 hours later…
6:23 PM
@TomV why did you have to show me that abomination of a question?
I made the mistake of engaging with comments to try to explain why it was a shitty question
I should not have done this
 
 
4 hours later…
10:30 PM
Why are comments even legal
2
 

« first day (3233 days earlier)      last day (106 days later) »