Viewing 15 posts - 2,971 through 2,985 (of 3,348 total)
diamondgm (10/16/2009)
diamondgm (10/16/2009)
October 16, 2009 at 3:42 am
david.howell (10/16/2009)
nVarchar can actually use more than 2 bytes for some characters e.g. chinese characters that use 3 bytes.
Do you have a source for that? Both Books Online and every...
October 16, 2009 at 2:09 am
This was a great question. Well done, John! I hope you have more of these in store for us.
diamondgm (10/16/2009)
October 16, 2009 at 1:41 am
Toreador (10/2/2009)
Hugo Kornelis (10/2/2009)
A very unusual pattern, as LIKE is intended to be used with wildcard characters, but syntactically valid.
We use it widely, where searches which can be either on...
October 2, 2009 at 4:33 am
Bhavesh-1094084 (10/2/2009)
Toreador (10/2/2009)
Hugo Kornelis (10/2/2009)
October 2, 2009 at 4:30 am
Toreador (10/2/2009)
Hugo Kornelis (10/2/2009)
October 2, 2009 at 3:01 am
john.arnott (10/1/2009)
October 2, 2009 at 1:16 am
Mighty (10/1/2009)
I'm of the opinion that the answer(s) are incorrect.CUBE and ROLLUP where already available in SQL Server 2005, so they were not introduced with SQL Server 2008.
SQL Server 2005...
October 1, 2009 at 3:30 am
DavidL (9/25/2009)
And no - there is no reason to use ORDER BY every time you use the tally table. There is reason to use ORDER BY every time you expect...
September 25, 2009 at 11:24 am
DavidL (9/25/2009)
In principle, there is no reason for large tally tables to work. If you change your query as I suggested, SQL Server can weed out the high numbers before...
September 25, 2009 at 10:10 am
DavidL (9/25/2009)
September 25, 2009 at 9:49 am
Hi David,
Based on visual inspection of your code, I fail to see any way that this code could cause "gaps" in the tally table. I think what you saw was...
September 24, 2009 at 3:45 pm
DavidL (9/24/2009)
It looks to me that the tally table isn't storing the values I inserted in ascending order (or at least it is not returning them in that order).
No surprise...
September 24, 2009 at 3:20 pm
DavidL (9/24/2009)
--===== Presets
DECLARE @DateStart DATETIME
DECLARE @DateEnd DATETIME
SELECT @DateStart = '2008-01-01 06:00',
...
September 24, 2009 at 3:17 pm
Bummer, missed a point because I overthought the question, figuring something so simple had to be a trick question.
I know of the AUTO_CREATE_STATISTICS settings. But this setting only affects creation...
September 17, 2009 at 2:54 am
Viewing 15 posts - 2,971 through 2,985 (of 3,348 total)