Viewing 15 posts - 57,301 through 57,315 (of 59,067 total)
I agree with the others.... the "quick fix" would be to convince folks that an IDENTITY column is the only way to go.
And, just to give you the warm fuzzies......
--Jeff Moden
Change is inevitable... Change for the better is not.
October 29, 2006 at 9:07 pm
I think that someone was barking up the wrong tree when they wrote the requirement
... but, since some folks suggested doing it...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 29, 2006 at 7:46 pm
Only if I absolutely had to put up with the same cruddy requirement that William has obviously been blessed with.
It's simple data...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 29, 2006 at 6:44 pm
As CK suggested... but different...
SELECT UserID,
Category,
PayPeriod,
ISNULL(CAST(DeleteFlag AS VARCHAR(12)),'Literal Null') AS DelFlag
ISNULL(CAST(IntegerTest AS VARCHAR(12)),'Null Integer') AS IntTest
FROM TimeWorked_Temp
--Jeff Moden
Change is inevitable... Change for the better is not.
October 27, 2006 at 6:03 pm
Is first name always guaranteed to be there? If not, what happens to the comma? Is Middle Initial always guaranteed to be there? Can the last name have a space...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 27, 2006 at 5:52 pm
Ah... sir... you have created "Death by SQL"... if two processes fire the trigger at the same time, who will win on the input buffer table you've created. Do the...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 27, 2006 at 5:29 pm
You're welcome and thank you for the feedback...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 27, 2006 at 5:25 pm
Cool... nice work around, Robert.
Stef, I gotta ask... why are you adding a column to a permanent table? Why doesn't the table already have that column? I'm obviously missing something here...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 27, 2006 at 5:25 pm
We're all in this together and I'm pullin' for ya" --Red Green
And, thanks for the feedback, Robert... that's what this is all about.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 27, 2006 at 5:21 pm
Thanks, Commando... I appreciate the feedback...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 27, 2006 at 5:16 pm
Yep... if you try to execute the whole thing... it's a single "batch". During "compile" time, the whole thing is evaluated and since the column doesn't actually exist, yet, the...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 27, 2006 at 7:53 am
If you don't already have one... now is the time to make a "Tally" table... Here's how...
--===== Create and populate the Tally table on the fly
SELECT TOP 11000...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 27, 2006 at 7:49 am
Or... Use OSQL with the -h-1 option. Don't forget to set the -s option to a tab... you can't do THAT from the command prompt... you will need to make...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 27, 2006 at 7:30 am
Not sure Michael is set on this... FULL joins return all rows from both tables 1 time, Cross joins will produce either a partial or full cartesian join (ex. if...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 27, 2006 at 6:59 am
Bingo!... Nice job, CK...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 26, 2006 at 6:07 pm
Viewing 15 posts - 57,301 through 57,315 (of 59,067 total)