Viewing 15 posts - 42,901 through 42,915 (of 59,063 total)
Karthik,
There is nothing in that data nor in the table to establish the order of the rows. You know you cannot rely on such a thing as the "natural...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 19, 2009 at 9:11 pm
So, Jamie... now you have 3 tables to maintain instead of just 2. The real problem is this table...
MakeID Make CategoryIDs
1 Dell 1,2,3
2 Sony 1,2
It's not normalized. Tables...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 19, 2009 at 9:03 pm
srathna77 (7/17/2009)
Can you please let me know how to do in batch process.
Did any of that work for you?
--Jeff Moden
Change is inevitable... Change for the better is not.
July 19, 2009 at 9:00 pm
J-F,
Did you ever figure out how to do this?
--Jeff Moden
Change is inevitable... Change for the better is not.
July 19, 2009 at 8:52 pm
lopes80andre (7/16/2009)
Lowell (7/16/2009)
after you've done the DECLARE @acumul_error varchar(100) or whatever it is, you need to initialize it as an empty string:
SET @acumul_error...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 19, 2009 at 8:44 pm
kevinwinters (7/14/2009)
*every* row of that field is null, I am trying to make every row of that field blank so I can concatenate the field...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 19, 2009 at 8:39 pm
Here's what I'm talking about... the details are in the comments in the code below...
--===== Create and populate a test table to demo with.
-- THIS...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 19, 2009 at 8:29 pm
Doylie (7/15/2009)
This...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 19, 2009 at 7:59 pm
Jez (7/16/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
July 19, 2009 at 7:53 pm
So, Arunkumar ... does that mean you actually have an answer to your problem or are you just posting another bit of problem code.
I know that you think what you...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 19, 2009 at 7:47 pm
ekla_pathik (7/15/2009)
You can use
SELECT COUNT(Customer_ID) FROM Customer
WHERE Customer_Created_Date BETWEEN Sales_Date_1 AND Sales_Date_2
For Sales_Date_1 and 2,...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 19, 2009 at 7:29 pm
kramaswamy (7/17/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
July 19, 2009 at 7:21 pm
It's real simple, Ron... [font="Arial Black"]MIL-TP-41[/font] which stands for "Make It Like The Print For Once". Another way of putting it is "Say what you do and then do...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 19, 2009 at 7:15 pm
If you follow the training kit, you will undoubtably succeed.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 19, 2009 at 4:07 pm
Just my 2 cents... I've never been satisfied with the service of remote DBA's (nor in house DBA's) and I'm trying to kill all such remote contracts.
Pradeep... I've seen your...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 19, 2009 at 4:03 pm
Viewing 15 posts - 42,901 through 42,915 (of 59,063 total)