Viewing 15 posts - 121 through 135 (of 163 total)
I doubt, that this will be fast. It does not use an explicit cursor, but practically does the same (or something worser) with its while loop.
If someone really...
June 28, 2017 at 2:58 am
Wouldn't the minimal privileges be the NTFS permissions to delete the ERRORLOG.? files? Sure - you can't replace / modify the current ERRORLOG file (SQL Server holds its tumbs on...
May 22, 2017 at 6:35 am
I wonder, that the only connect item I found for a column based MIN/MAX (similar to Oracle's LEAST()/GREATEST()) got only 4 quotes since last year (https://connect.microsoft.com/SQLServer/Feedback/Details/3085573).
Maybe someone...
May 22, 2017 at 6:21 am
Why do you not use the build in ROUND function?
It takes three parameters:
- the value
- the rounding length (use negative numbers to round to a power...
May 16, 2017 at 2:56 am
my apology for the confusion - I tested it only on SQL 2014 (since I was to lazy to set up a new 2016 server just for testing and did...
May 8, 2017 at 5:55 am
On which version did you run your test? On SQL 2014 SP2 Dev. the query will only return one row (and I stumbled over a few scripts which failed, since...
May 8, 2017 at 2:31 am
Another question.
If I understood it correct, it has to read all segments / pages for the city column, when I execute a SELECT COUNT(*) from customers...
May 8, 2017 at 12:34 am
Thank you very much for the quick answer. I always wondered, how exactly SQL Server does this stuff and your article (plus the answer) makes it a lot more clear...
April 24, 2017 at 10:02 am
any idea, if (and if yes then how) small datatypes as TINYINT (= 1 byte) could be compressed in columnstored indexes?
Its clear, that I will save space...
April 24, 2017 at 8:21 am
You should use an INLINE TABLE VALUE fuction instead of a scalar function - this would save a lot of time when you import many datasets
CREATE...
April 13, 2017 at 4:10 am
Short remark: a FILLFACTOR = 90 on a Identity Column (= auto increment) in a read-only-table (at least no space-growing varchars) makes no sense and wastes 10 % space. Even...
April 5, 2017 at 1:48 am
oh, thanks (I usually use only the deep links in the newsletters and visit the SSC start page only very seldom ...
April 5, 2017 at 1:30 am
Why do you not use a much more short and simple
DECLARE @bd DATE = '19801231', @TD DATE = '20171231'
SELECT DATEDIFF(YEAR,
March 28, 2017 at 3:58 am
beside the "default" (at least before SQL 2016) Trace Flags 1117 / 1118 (Grow all Files in a FileGroup equally / prevent mixted extends) I'm using:
1222 (allows Deadlock monitoring),...
March 17, 2017 at 1:44 am
March 8, 2017 at 8:07 am
Viewing 15 posts - 121 through 135 (of 163 total)