Viewing 15 posts - 37,051 through 37,065 (of 59,098 total)
AnthonyR (8/30/2010)
I just thought I'd share a head-smacking moment with you. It's been touched-on previously in this thread, but I don't think anyone's come right out and demonstrated it.
Thanks for...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 30, 2010 at 6:28 pm
aykut canturk (8/29/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
August 30, 2010 at 7:57 am
Agreed. If the date mustn't change, then storing it in a variable is definitely the way to go just to be on the safe side.
--Jeff Moden
Change is inevitable... Change for the better is not.
August 30, 2010 at 7:23 am
Don't use @@IDENTITY for this. It could cause the wrong number to be returned if certain things happen to the database in the future. Use SCOPE_IDENTITY() instead. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 30, 2010 at 7:20 am
nithiyanandam-447806 (8/30/2010)
but we can't bulk insert the table..it expects status columns.
Obviously, you've correctly identified the problem. You'll need to change something about that. My recommendation is to NEVER...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 30, 2010 at 7:17 am
Karl-452938 (8/26/2010)
Let's keep it simple
We have one table Files, which has 2 fields we need here
-FileID...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 30, 2010 at 7:03 am
steve.robson 58295 (8/26/2010)
1 - It always depends, but you should try to adopt a standard approach, some general guidelines...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 29, 2010 at 7:20 am
On the flip side of all this, people make a huge difference either way. A great job can suddenly become a major PITA based on a change in someone's...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 29, 2010 at 7:09 am
aykut canturk (8/28/2010)
Product Col1...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 29, 2010 at 7:03 am
j.venugr (8/28/2010)
i got architecture from your forum, but i need brief explanation about sql sever architecture to understand very clearly, so please send the explanation, my mail ID is j.venugr@gmail.com
It's...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 29, 2010 at 6:57 am
thava,
Does that answer your question for you?
--Jeff Moden
Change is inevitable... Change for the better is not.
August 29, 2010 at 6:45 am
To anyone else reading this particular thread...
The method Wayne used is affectionately known as the "Quirky Update" or the "Running Total Solution". It has rules that you MUST follow...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 29, 2010 at 6:42 am
Wayne,
I was looking at your previous row calculation on the 3 part update thinking to myself "Cool... he even thought of the forced RN change when EMID changes just...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 29, 2010 at 6:34 am
Aye... that's the ticket, matey!
--Jeff Moden
Change is inevitable... Change for the better is not.
August 29, 2010 at 6:10 am
Funny that you mention The Flash, Wayne... I'm always hungry like he is after a good run... especially after I quit smoking (finally).
--Jeff Moden
Change is inevitable... Change for the better is not.
August 29, 2010 at 5:43 am
Viewing 15 posts - 37,051 through 37,065 (of 59,098 total)