Viewing 15 posts - 57,376 through 57,390 (of 59,101 total)
You could use Sp_ExecuteSQL but then you'd still end up with a table variable that cannot be made to use statistics...
If it were me, I'd use a temp table instead...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 24, 2006 at 4:09 pm
Sorry, Remi... that wasn't directed at you... I got so ticked
at the mere suggestion that such a simple data manipulation be done...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 24, 2006 at 7:49 am
Ok... I know... "put up or shut up, Jeff"... fine
Let's see you do it any simpler in an app 
--Jeff Moden
Change is inevitable... Change for the better is not.
October 24, 2006 at 7:20 am
I try to use my memory... but I forget... ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
October 24, 2006 at 6:08 am
Serqiy... You really that old ? ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
October 23, 2006 at 11:35 pm
If there are dupes on a,b, or d... whatcha wanna do? Just grab anything? Not exactly a good database practice
but it helps...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 23, 2006 at 11:33 pm
WHY? The code won't be any simpler there!
--Jeff Moden
Change is inevitable... Change for the better is not.
October 23, 2006 at 11:29 pm
Commando...
First, I gotta share the normal diatribe about your numeric sequence and forgive me while I blast the designer... if you were the designer, sorry, but not sorry... ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
October 23, 2006 at 11:18 pm
Nicely done, Kim.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 23, 2006 at 10:03 pm
No sure what the "Number" parameter in Sybase is but...
There a multiple functions in SQL Server that return info about the current connection... for example... @@SPID returns the SPID of...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 23, 2006 at 6:56 am
create an updateable passthrough view in each target database
I don't see where you said those words, but may that's what you meant... I was talking about just creating...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 23, 2006 at 6:28 am
Yep... I missed that one... guess it's time for some sleep ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
October 22, 2006 at 8:15 pm
Doesn't seem to be "automatically scalable" unless you create the views and the trigger dynamically. Maybe that doesn't matter much... non-dynamic solutions do require some human intervention but they usually run better...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 22, 2006 at 8:12 pm
i had intended using a dynamically constructed sql string - but it failed everytime. i was... |
--Jeff Moden
Change is inevitable... Change for the better is not.
October 22, 2006 at 7:43 pm
Use the other form of case...
, SUM( CASE WHEN r.packagetransmethodid NOT IN (1,2,3,4,5,6,7,8,9) THEN ShipmentQty ELSE 0 END) as "Others"
--Jeff Moden
Change is inevitable... Change for the better is not.
October 22, 2006 at 1:54 pm
Viewing 15 posts - 57,376 through 57,390 (of 59,101 total)