Viewing 15 posts - 55,081 through 55,095 (of 59,072 total)
I'm thinking that your table is a bit denormalized... it should be like this...
EventID Fighter 1 5 1 10 2 ...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 11, 2007 at 6:53 pm
That's a whole lot different than what you asked... but somethin similar to what I posted will still work. Just set some variables in the process. Have you read about...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 11, 2007 at 6:00 pm
Understood... but you have no criteria for the table... that makes a cross-join.
--Jeff Moden
Change is inevitable... Change for the better is not.
September 11, 2007 at 5:55 pm
C'mon Zach... folks helped you out... the least you could do is post your solution ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
September 11, 2007 at 5:52 pm
Thanks Remi!
--Jeff Moden
Change is inevitable... Change for the better is not.
September 11, 2007 at 5:51 pm
Lookup "IF" in Books Online ("Transact-SQL HELP" in Query Analyzer) to find more about the following example (also from Books Online)...
IF (@ErrorSaveVariable <> 0)BEGIN PRINT 'Errors encountered, rolling...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 11, 2007 at 7:27 am
No, I understood that... but typically there is some unique key (column or combination of columns) other than the GUID that would identify the unique row. Need that info to do...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 11, 2007 at 7:20 am
Heh... if that's what he meant by decimal... Me? Guess it's obvious that I don't normally do those kinds of conversions, huh? ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
September 10, 2007 at 9:36 pm
But, doing it that way, it can't be turned back into an IP address, can it? And, theoretically, couldn't there be dupes that way? After all, the OP did say...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 10, 2007 at 9:34 pm
Ah... got it... had to go back and look... Serqiy is correct and I'll throw in that you may not ever want to pass date serial numbers between products... Best...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 10, 2007 at 9:29 pm
Yep... accidental cross join... tell me where the join criteria is for the "sy" table alias...
SELECT D1.stu_sid, D1.stu_id, Min(D1.Entry_Date) as Entry_Date, Case MAX(D2.Exit_Date) When '01/01/2900' then null Else MAX(D2.Exit_Date) end ...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 10, 2007 at 6:15 pm
Ummm... I gotta agree with that... tampering with server settings without knowing the full ramifications of each setting is nearly certain death for the server. I'd get some qualified help...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 10, 2007 at 6:03 pm
It was a spoof, David...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 10, 2007 at 5:56 pm
Cool Kurt... wanna share your SQL code on this? ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
September 10, 2007 at 5:37 pm
You really need to look at a good calendar for the year 2002...
2002-05-03 is a Friday... count 1 day
There are 4 full weeks after that up to 2005-05-31... count...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 10, 2007 at 5:36 pm
Viewing 15 posts - 55,081 through 55,095 (of 59,072 total)