Viewing 15 posts - 16 through 30 (of 60 total)
Wow, didn't know the article was going to generate a fire-storm on TSQL syntax. The original purpose was to see if there was a difference getting max/min value of a...
December 17, 2018 at 9:47 am
Actually all the suggestions made are good ones, and as most have pointed out all is very environment sensitive. 90% of the DelFlag column are marked 'N' and the others...
June 6, 2018 at 7:35 am
Index work had already been accomplished -- hence the index + key lookup. The query returns every column in the table, and I am just opposed to creating a non-clustered...
June 5, 2018 at 12:44 pm
Same query plan, same cost, same IO, same cpu time. No change defining it as a variable first.
June 4, 2018 at 10:18 am
From the estimated query plan. Statistics were up to date, so estimated rows were close to actual rows.
May 15, 2018 at 10:39 am
I noticed that also when using a columnstore index as a clustered index and a non-clustered Hash Primary Key (for in-memory tables). When using dm_db_xtp_hash_index_stats I get one row...
July 25, 2016 at 1:38 pm
Hmmm, you finally put in writing (and script) what I have been doing for years. Yeah! Great work!
June 16, 2014 at 9:34 am
Interesting topic. After retiring from the Air Force I started in management and eventually ended up as a CTO for an insurance company here in Texas. After a...
August 5, 2011 at 6:14 am
I was an early user of SQL LiteSpeed. Yes you are correct, the less IOs offerred by compression resulted in tremendously less backup and restore times. Although depending...
July 26, 2011 at 6:49 am
Makes it even more interesting if you add following:
insert into @test-2 values ( NULL )
Answer is still 6.
June 21, 2011 at 7:19 am
Data presentation -- still an art, definitely not a science. The Challenger accident is a significant occurrence where we had the data, but was never presented in a way...
April 18, 2011 at 8:42 am
Well written for what it covered, but my initial expectation before reading the article was that you would touch more on techniques for handling transaction log growth and also handling...
March 24, 2011 at 9:58 am
Just to make sure we are all on same page, the way I've heard the Microsoft CAT engineers explain for row and page compression that the data is compressed both...
January 13, 2011 at 3:05 pm
Unfortunately I do not have before and after data size numbers fro the row compression on our production OLTP database. But I did use (as documented in the script)...
January 13, 2011 at 12:30 pm
You are correct; compressing small lookup tables actually may increase the overall size. That is why I exclude any tables less than 8 pages in my script. I...
January 13, 2011 at 6:34 am