Viewing 15 posts - 40,741 through 40,755 (of 59,070 total)
Vinay.Gambhir (12/9/2009)
Yes you are rightI was missing the AND in my join...
working fine now.
Thanks
Considering that you wrote the following...
table2.column2 = table2.column2
... I'd recommend you post your code and let's take...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 9, 2009 at 8:54 pm
Dean Jones-454305 (12/8/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
December 9, 2009 at 8:52 pm
As a sidebar, this is one of the reasons why the SA login must never be used, why each DBA should have their own login, and jobs are never associated...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 9, 2009 at 8:44 pm
Hi Fred,
I think you got F1 and F2 mixed up a little in your desired output, but no worries... this will do it...
--===== Create and populate a test table. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 9, 2009 at 8:00 pm
4 weeks later, she comes up with the following:
Heh... or should I say "Ack!" 🙂 I'll probably catch hell from everyone on this forum for saying so, but...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 9, 2009 at 7:30 pm
I agree... if something is actually "urgent", take a little of your own urgent time to make it possible to respond quickly to your post... read the article Lutz pointed...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 9, 2009 at 7:10 pm
qldrobbo (12/9/2009)
Say I have two tables
Trades with column TradeId
MapTraders with columns TradeId, TraderId and Type
In the Trades table say I have 1 row with TradeId 1
In the MapTraders table I...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 9, 2009 at 7:04 pm
We need to make sure that our systems work with the user, that help the user and make their jobs easier.
Heh... I've been preaching that on this forum for years...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 9, 2009 at 6:56 pm
Lynn Pettis (12/9/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
December 9, 2009 at 6:23 pm
Lynn Pettis (12/9/2009)
Bru Medishetty (12/9/2009)
Lynn Pettis (12/9/2009)
Krasavita (12/9/2009)
Microsoft SQL Server 2000 - 8.00.2040 (Intel X86) May 13 2005 18:33:17 Copyright (c)...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 9, 2009 at 6:04 pm
After seeing that code, my immediate recommendtion would be to lookup INSERT/SELECT in Books Online (instead of INSERT/VALUES) so that when someone explains how to fix this, you'll actually understand....
--Jeff Moden
Change is inevitable... Change for the better is not.
December 9, 2009 at 6:02 pm
CirquedeSQLeil (12/9/2009)
Steve Jones - Editor (12/9/2009)
I think crystal balls work better than ouji boards. Especially when you drop them on someone's foot to emphasize a point.
Dropping only provides limited emphasis...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 9, 2009 at 5:45 pm
Jack Corbett (12/9/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
December 9, 2009 at 5:42 pm
Grant Fritchey (12/9/2009)
I always forget this one. How do you flip the "run faster" switch to the on position in SQL Server?
BWAA-HAAA!!! Whenever I get a "make SQL Server...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 9, 2009 at 5:38 pm
Heh.. triply rude on halane's part then. I wonder if halane likes pork chops. 😉 Thanks Gift.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 8, 2009 at 6:20 pm
Viewing 15 posts - 40,741 through 40,755 (of 59,070 total)