Viewing 15 posts - 1 through 15 (of 26 total)
Thank you all for your insightful feedback! Based on this, as well as our internal discussions, we have concluded that the best way to "eat this elephant" is to...
December 6, 2011 at 8:01 am
I did not create the "FALLING SKY" LOL, and "Chicken Little" (aka the person who created this nightmare) already lost their job! I am here to try to rectify...
December 5, 2011 at 8:49 am
The only mod I made was that I had to add DISTINCT to the CTE. It worked flawlessly! Thanks again!
I have posted final version for the...
November 11, 2011 at 11:46 am
Of course, CTE! Why didn't I think of that! (It's been a long week! LOL)
Thanks a million!
Have a great weekend!
KK
November 11, 2011 at 10:24 am
Just Joe Client in the Client table, but both Accounts for Joe in the Acct table. (One Account named "Joe Client", and one named "Joe Client Betelgeuse".) The ClientName...
November 11, 2011 at 10:05 am
Thanks for the replies! And only 3 seconds apart! Amazing! 🙂
@ Corgi: Because it's an example.
I don't know how many records I have in my table table either. LOL...
July 16, 2011 at 9:30 pm
Additional Info: In SSMS on the remote machine that is connected it is displaying "SERVERNAME\SQLNAMEDINSTANCENAME,1433 (SQL Server 9.0.3042 - username)"
On the machine with both instances, the named instance connection...
June 2, 2011 at 7:41 am
For the benefit of future generations, here is what my final product using the table variable solution looks like:
DECLARE @CurrentVDate smalldatetime
DECLARE @bID int
SET @bID = 1
DECLARE @CurDate DateTime
SET @CurDate =...
April 27, 2011 at 7:52 am
I like the table variable idea! Thanks G2
KK
April 26, 2011 at 2:12 pm
Below is the original procedure prior to my attempt at modifying it to use the OUTPUT clause.
P.S.: There is an error in the above code (beyond the obvious) the...
April 26, 2011 at 2:10 pm
I still have not been able to make this work correctly 100% of the time...
Anybody have any ideas?
TIA,
KK
March 22, 2011 at 3:16 pm
Don't you just love "expanding scope"?
I got the query working (Or rather you gurus did!) and now I find out that it needs to be a "conditional" update...
This works GREAT!
UPDATE...
March 15, 2011 at 1:45 pm
ALZDBA,
Thanks for that. I hadn't tried a different JOIN type.
Many Thanks!
KK
March 15, 2011 at 12:33 pm
Lowell,
Thanks for the quick reply. That is close to what I had, except I need to be able to UPDATE #Temp T with the values from A and C.
Here's...
March 15, 2011 at 12:22 pm
SEE! I knew it was simple! Thanks a million! (The data in the length table was a little skewed, and I had some extra commas and parentheses...
March 15, 2011 at 9:10 am
Viewing 15 posts - 1 through 15 (of 26 total)