Viewing 15 posts - 12,631 through 12,645 (of 18,923 total)
Why not use 2 derived tables and full join on the date?? That way you can always add more columns when needed. Maybe this is just me but...
October 7, 2005 at 11:22 am
The ONLY guarantee is to write them both for the insert and the select.
October 7, 2005 at 10:21 am
Precisely
. I had my head hurt a long time over that one. I found out it was less trouble trying to...
October 7, 2005 at 9:28 am
Some compagnies have go live licenses (where the beta is used in production). I heard a number of ±40 licenses. The release date is November 7th 2K5.
October 7, 2005 at 8:26 am
In theory it would work... but you could lose object to object dependences. But if you're only after the table use then you're alright.
October 7, 2005 at 8:21 am
This is something that would be much easier to solve using a calendar table. Just fill a Tables with dates from 200? to 2020+ with a date column and...
October 7, 2005 at 8:20 am
He is right about that and rschaeferhig's tip is actually a best practice that you should follow all the time. However I don't really see how that could have...
October 7, 2005 at 6:40 am
October 7, 2005 at 6:31 am
The order by can be benificial if you order in the table1 clustered index.
October 6, 2005 at 3:01 pm
The trigger will fire once for each update statement and update every line modified by the query.
October 6, 2005 at 2:25 pm
I think that the answer will lie there. I doubt it's possible to cover 100% over the possible issues here but 99.99% may be possible
October 6, 2005 at 2:00 pm
Just a taught... Could you keep the date (datetime so you have ms precision) of the insert instead and then maybe add an identity column so that you have a...
October 6, 2005 at 1:55 pm
I like it too. As for Keneddy I wasn't born so that one's pretty easy for me. Who's gonna build the queries? How are they building them?
October 6, 2005 at 1:48 pm
Viewing 15 posts - 12,631 through 12,645 (of 18,923 total)