Viewing 15 posts - 46,741 through 46,755 (of 59,095 total)
Yihong (12/7/2008)
Thank you guys, it worked beautifully in my code.
You bet... thanks for the feedback.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 7, 2008 at 9:50 am
Ken Simmons (12/7/2008)
Thanks Jeff.I knew there was a way to do it without the math, I just cound't think of it last night.
S'ok... Heh... not much coffee at night. 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
December 7, 2008 at 9:49 am
Replace the derived table in the from clause with your real table...
SELECT PARSENAME(d.IpAddr,4) As ColA,
PARSENAME(d.IpAddr,3) As ColB,
...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 6, 2008 at 11:44 pm
Are you saying that [font="Arial Black"]all [/font]the TR tables are Truncated before data is added? If so, then, yeah, you could go to SIMPLE recovery mode. Keyword is...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 6, 2008 at 11:40 pm
If you throw in the appropriate partition clause, it get's even simpler...
Declare @t Table(i int)
Insert Into @t
Select 1
Union All
Select 1
Union All
Select 1
Union All
Select 2
Union All
Select 2
Union All
Select 3
Union All
Select 3
Union...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 6, 2008 at 11:31 pm
Very cool... 2 seconds huh? That was going to be my next question. What kind of hardware are you running? I'm running a 6 year old P4...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 6, 2008 at 11:22 pm
Heh... what I'd like to do is to be able to show emoticons AND leave a hanging parenthesis in the same post. None of the emoticons use just a...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 6, 2008 at 9:31 pm
This will fly... even in the face of a million rows...
--===== Create the same test data as before.
-- This is NOT part of...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 6, 2008 at 9:08 pm
Um... I'm thinking that's not what you want. Look at the ACTUAL execution plan for that... tell me where, with only 11 rows in the original table, you come...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 6, 2008 at 7:30 pm
If you didn't use Gail's solution, would you mind posting your solution, please?
--Jeff Moden
Change is inevitable... Change for the better is not.
December 6, 2008 at 7:13 pm
Can't the TEXT column be changed to a VARCHAR(MAX) column?
--Jeff Moden
Change is inevitable... Change for the better is not.
December 6, 2008 at 7:11 pm
Create a temporary stored procedure, instead. You know... one that begins with a "#" sign. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
December 6, 2008 at 7:07 pm
Heh... one religous battle coming up... ready?
NEVER DELETE! NEVER REUSE PK's!
--Jeff Moden
Change is inevitable... Change for the better is not.
December 6, 2008 at 7:02 pm
Sorry... forgot to post the results I got... single P4 1.8Ghz, 1GB RAM, 80GB IDE hard drive, SQL Server 2005 Dev Edition SP2...
(1 row(s) affected)
Table '#Client_____________________________________________________________________________________________________________00000000006E'.
Scan count 1,...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 6, 2008 at 6:57 pm
Actually, I'll take door #3 😛 ... performance is the same as WHERE EXISTS and it's even easier to read especially for newbies that may be on the team...
SET STATISTICS...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 6, 2008 at 6:51 pm
Viewing 15 posts - 46,741 through 46,755 (of 59,095 total)