Viewing 15 posts - 37,021 through 37,035 (of 59,072 total)
The only thing I'm missing is how YOU call the EXEC that sends an email for you. (Trying to give you a complete solution).
--Jeff Moden
Change is inevitable... Change for the better is not.
August 30, 2010 at 9:07 pm
SwePeso (8/30/2010)
SET @CurrencyAmountID = SCOPE_IDENTITY()
instead of
SET @CurrencyAmountID = @@IDENTITY
@@IDENTITY will give you the latest created identity value in the database, no matter which table or user created it....
--Jeff Moden
Change is inevitable... Change for the better is not.
August 30, 2010 at 7:20 pm
Mr.SQL DBA (8/30/2010)
You are absolutely correct. Tuning of Inserts is as Important as Tuning the Selects.
so i want any options or any types or any methods or any scenarios...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 30, 2010 at 7:16 pm
Anthony,
Here's a direct replacement for your sprTablixTest with three very important differences (that you may or may not want)...
1) It creates different data every time you use it instead...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 30, 2010 at 7:09 pm
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
Viewing 15 posts - 37,021 through 37,035 (of 59,072 total)