Viewing 15 posts - 32,416 through 32,430 (of 59,099 total)
Sure... the following code creates a million row "clean" hierarchy in the form of a classic Adjacency List. I have it as a stored procedure so that I can...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 2, 2011 at 12:20 pm
codebyo (9/27/2011)
Day of week would be like this:
SELECT CASE DATEPART(WEEKDAY, '20110901')
...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 2, 2011 at 12:10 pm
CELKO (9/28/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
October 2, 2011 at 12:06 pm
codebyo (9/29/2011)
DECLARE @Size INT = 7;
SELECT
REPLICATE('0', @Size-LEN(CAST(1234 AS VARCHAR(MAX)))) + CAST(1234 AS VARCHAR(MAX)) +
REPLICATE('0', @Size-LEN(CAST(76541 AS...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 2, 2011 at 11:37 am
pespes009 (9/29/2011)
Thanks a lot guys !!!
So, what did you end up with? Two way street here... Please post the code that you ended up using so that others may...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 2, 2011 at 11:31 am
~Dev~ (9/30/2011)
Thus (1=NULL) and (NULL=NULL) are bad operations.
Else, you may override default behavior...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 2, 2011 at 11:26 am
theeggman (9/30/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
October 1, 2011 at 4:02 pm
Gianluca Sartori (9/30/2011)
This great article[/url] by Waye Sheffield will help you.Regards,
Gianluca
Agreed... it's one of the better articles on Table Variable v.s. Temp Tables that I've ever seen.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 1, 2011 at 3:54 pm
BCP with a format file that uses the end of line characters as delimiters (as well as some others).
In actuality, that's not the "best" way... the absolute best way would...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 1, 2011 at 3:51 pm
dastagiri16 (10/1/2011)
case when Profesenalism=1 then count(Profesenalism) end as 'Profesenalismpoor',
case when profesenalism=2 then count (profesenalism) end 'profesenalismavg',
case when Communication=1 then count(Communication) else 0 end 'Communicationpoor',
...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 1, 2011 at 3:48 pm
Mick,
Read the link that BitBucket pointed you to and post your data using the methods therein... you'll get answers much quicker.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 1, 2011 at 3:41 pm
Sorry folks... I've been burning some midnight oil at the job and the answer to the question of how this works is a bit of a long one. To...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 1, 2011 at 1:57 pm
I fully realize that this thread is 3-1/2 years old and the OP probably got a solution a very long time ago. I found this thread totally by accident...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 1, 2011 at 1:33 pm
You bet, Grant. Thank you for taking the time to post some feedback. 🙂
--Jeff Moden
Change is inevitable... Change for the better is not.
September 30, 2011 at 4:58 pm
Mushroom (9/30/2011)
But, I'm wondering why you appear to be generating a recordset with 10000 rows and then limiting that...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 30, 2011 at 6:39 am
Viewing 15 posts - 32,416 through 32,430 (of 59,099 total)