Viewing 15 posts - 43,051 through 43,065 (of 59,063 total)
I don't use any prefexies in my production databases. The reason is that a table could be changed to a view or vice versa and having a prefix would...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 7, 2009 at 9:28 am
GSquared (7/7/2009)
Ian Scarlett (7/7/2009)
select id, forename, case when forename = 'Kim' then 1 else 2...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 7, 2009 at 9:26 am
Bur@ir (7/5/2009)
Now i dont want to have so many rows linked to 1 customer.
Why not? It's what databases do. The other methods will require the additional headaches of...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 7, 2009 at 9:17 am
Paul,
Very cool. The additional sequence table prevents the need for a SELECT or comparison in the code at all and that's important for both concurrency and the prevention...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 7, 2009 at 6:06 am
BWAA-HAA!!! Well, at least now you know why I'm so opposed to any form of "ID Reservation" or "Sequence" table. While it's possible to make such a thing...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 6, 2009 at 9:45 pm
Idea understood... but that's a sequence table and that's even worse that what's trying to be done for updates unless you're very, very, very careful and you use a 3...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 6, 2009 at 9:11 pm
Heh... dang it... I had the right thread after all. That code above is slow. Where all the other methods take something less than 16 ms to split...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 6, 2009 at 9:02 pm
Sorry... wrong thread.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 6, 2009 at 8:50 pm
Digs (7/5/2009)
I havent built it yet. Because what comes first the chicken or the egg,...
By the way... the answer to that question is the "egg" because a chicken can only...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 6, 2009 at 8:30 pm
Where'd Digs go? He owes us a post with his solution...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 6, 2009 at 8:26 pm
wesigler (7/6/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
July 6, 2009 at 8:24 pm
There may be even a better way to avoid deadlocks on this. Combine the Insert with the Select... I believe you'd still need the TABLOCKX because you're needing to...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 6, 2009 at 8:12 pm
smunson (7/6/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
July 6, 2009 at 8:06 pm
smunson (7/6/2009)
"SERIALIZABLE
Specifies the following:
Statements cannot read data that has been modified but not yet committed by other transactions.
No other transactions can modify...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 6, 2009 at 7:52 pm
smunson (7/6/2009)
Jeff Moden: I'd really appreciate your input on this...
It might not be what you expect... my input is that in this modern day of computers and other new fangled...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 6, 2009 at 7:44 pm
Viewing 15 posts - 43,051 through 43,065 (of 59,063 total)