Viewing 15 posts - 31,246 through 31,260 (of 59,101 total)
johnitech.itech (2/6/2012)
check these about ur problem
I'd recommend NOT using either of those methods because they both employ a "Triangular Join" which will crush your server even for relatively small sets...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 6, 2012 at 7:36 am
Koen Verbeeck (2/5/2012)
Jeff Moden (2/5/2012)
--Jeff Moden
Change is inevitable... Change for the better is not.
February 5, 2012 at 10:53 pm
ssc_san (2/5/2012)
I am using it to populate list of values for my report. And it is not going to change in the future (As per User), So I took...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 5, 2012 at 10:51 pm
weston_086 (2/5/2012)
with cte (id,name,class,rn)as
(select id,name,class,ROW_NUMBER() over (PARTITION by id ,name,class order by ID) from jtdup)
delete from cte
where rn>1;
select * from jtdup
That won't work if the name column is actually...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 5, 2012 at 10:47 pm
I could be wrong but I'm pretty sure it can't be done. Unique columns allow only one NULL. You might be able to pull something off with a...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 5, 2012 at 8:56 pm
quynh012012 (1/6/2012)
quynh012012 (1/3/2012)
I do not agreed with you. Any way, your points of view make me thinking about some thing for my project.
Pls try to keep posting. Tks and best...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 5, 2012 at 7:25 pm
Steve Jones - SSC Editor (2/5/2012)
1. I'm not sure how easy the first item is to fix, but we'll see. Definitely an issue.
2. Again,...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 5, 2012 at 7:04 pm
Phil Factor (2/5/2012)
SELECT yadayada
FROM sometable)--==== This Jeff's 2nd test comment
SELECT *
FROM cteSomeCTE[/font]
Well the poor old prettifier works with...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 5, 2012 at 6:57 pm
Mark-101232 (1/18/2012)
If you can change the INSERT, you don't need the trigger at all
INSERT INTO Customer(CustomerId,Name,Value,Percentage)SELECT CustomerId,Name,Value,dbo.GetPercentage(Value)
FROM CustomerTemp
BWAAA-HAAA!!!! MARK FOR PRESIDENT! :-D;-)
--Jeff Moden
Change is inevitable... Change for the better is not.
February 5, 2012 at 4:50 pm
CELKO (1/17/2012)
Please tell me that you do n ot really use BIT flags in SQL. That mess was 1950's assembly language, before we had high level abstract languages. .
Interesting....
--Jeff Moden
Change is inevitable... Change for the better is not.
February 5, 2012 at 4:45 pm
asm1212 (1/20/2012)
Fields are SSN, Contract_Number, Effective_Date, Term_Date...
Here is the breakdown:
Think of this process as a Contract...For each contract, we have a SSN, the...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 5, 2012 at 4:24 pm
Robert Murphy UK1 (1/20/2012)
--Jeff Moden
Change is inevitable... Change for the better is not.
February 5, 2012 at 4:14 pm
Just checking. Are you all set on this or do you need more help?
--Jeff Moden
Change is inevitable... Change for the better is not.
February 5, 2012 at 4:00 pm
sampathsoft (2/1/2012)
So let me know this method (joinig tables/ outer join) is good for performance ...
Heh... "It Depends". How long does it currently take to run and how big...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 5, 2012 at 3:47 pm
ALZDBA (2/1/2012)
Have a look at sp_addmessage in BOL:
exec sp_addmessage [ @msgnum = ]...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 5, 2012 at 2:58 pm
Viewing 15 posts - 31,246 through 31,260 (of 59,101 total)