Viewing 15 posts - 50,221 through 50,235 (of 59,091 total)
Matt Miller (5/30/2008)
bcronce (5/30/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
May 30, 2008 at 7:12 pm
Look at the code, guys... column was previously defined as NOT NULL.
Dunno if it'll work because no one provided the code for the rest of the table, but...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 30, 2008 at 6:46 pm
I'd say to never look at the percentage of batch in the execution plan... it lies... a lot...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 30, 2008 at 6:32 pm
First, I think I'd use UNION ALL... considering the source tables, there's probably not much chance of duplication, anyway.
The other thing is that the CPU time is not varying all...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 30, 2008 at 6:29 pm
Tomm,
Your code won't work on SQL Server 2000 (this forum is a 2k forum)... keyword PERSISTED does not exist and the calculated column is considered "non-deterministic" in 2k so the...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 30, 2008 at 6:02 pm
Heh... regular doses of a good Scotch and soda fixed mine... 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
May 30, 2008 at 5:27 pm
jmapledoram (5/30/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
May 30, 2008 at 5:17 pm
Thanks for the feedback, David!
--Jeff Moden
Change is inevitable... Change for the better is not.
May 30, 2008 at 9:14 am
Welcome aboard, Steve! And thanks for the feedback!
--Jeff Moden
Change is inevitable... Change for the better is not.
May 30, 2008 at 9:13 am
OP is passing in Varbinary... I guess I don't understand... what does the input actually look like and what should the output be?
Are you suggesting that the input is in...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 29, 2008 at 9:46 pm
Nightstick recalibration or just a crushing blow to the calcium knob?
--Jeff Moden
Change is inevitable... Change for the better is not.
May 29, 2008 at 9:35 pm
Thanks for the feedback, Bob. Yeah, it's sometimes very difficult to simply ignore such a post... but I should get better at just blowing those types of posts off...
Thanks...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 29, 2008 at 9:31 pm
bcronce (5/29/2008)
select convert(bigint,HashBytes('SHA1', convert(varchar, getdate(),121)+convert(varchar,rand())))this should be a bit unique:cool:
It is, but not if you use it in a single select against a multi-row table to try to generate more...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 29, 2008 at 9:26 pm
Nicely done, Steve... Because of the nature of the CHAR datatype and the fact that the orginal table uses it instead of VARCHAR, you can really shorten the code...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 29, 2008 at 9:09 pm
steveb (5/28/2008)
Tomm Carr (5/27/2008)
An identity column? Why? What purpose does it serve? Under what circumstances would you ever use it?
an Identity column is required for replication, this would...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 29, 2008 at 8:12 pm
Viewing 15 posts - 50,221 through 50,235 (of 59,091 total)