Viewing 15 posts - 14,911 through 14,925 (of 59,063 total)
June 4, 2017 at 12:06 am
Heh... obviously, by the link you posted, you know some of the reasons why I avoid it. Add to that that I have no need for the extended early dates...
June 3, 2017 at 11:48 pm
June 3, 2017 at 9:51 pm
Can't test it because I'm no where near a 2016 box just now but if all the dates in your JSON are in the DMY format, then just add the...
June 3, 2017 at 9:37 pm
It's easy. Just rename (re-alias) the column names and limit the rows with a WHERE clause. Like this.
SELECT year1 = year3
,count1 = count3
June 3, 2017 at 9:16 pm
By the same token, you can have a fire breathing monster of a server on a network with speeds that we could only dream of and still run into performance...
June 3, 2017 at 10:24 am
Nice article. It would, however, be helpful if you would attach sample data in the "Resources" section so that people can "play" with your good code for additional learning through...
June 3, 2017 at 9:14 am
Just to establish some warm fuzzies that a concurrent update won't ever interfere with the correct calculation (unique sequential number) of the MatCodeID, I would add a WITH (TABLOCKX) to the...
June 3, 2017 at 9:08 am
June 3, 2017 at 8:48 am
Eirikur Eiriksson (1/4/2016)
June 3, 2017 at 8:44 am
June 2, 2017 at 9:58 pm
Yes. A "fact table" is a duplication of data that must be separately maintained. It would probably be better to create what is known as a "Partitioned View" and reference that...
June 1, 2017 at 6:03 pm
I see a claim of working against 1.7 million rows. What does the data actually look like and what is the structure of the table that you're using for the...
June 1, 2017 at 5:39 pm
June 1, 2017 at 8:35 am
Viewing 15 posts - 14,911 through 14,925 (of 59,063 total)