Viewing 15 posts - 39,286 through 39,300 (of 59,072 total)
Dehqon D. (3/15/2010)
For me SQL is in learning process, hope can get knowledge soon and help to people like you πP.S: Reposting 3rd time, after waiting after half hour
Ummm... maybe...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 16, 2010 at 8:10 pm
Paul White (3/16/2010)
The tally-table method ... {snip} ... is far, far, superior.Almost as good a a CLR string splitting function in fact.
Heh... keepsake that is right thar...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 16, 2010 at 7:13 pm
GSquared (3/16/2010)
The SessionID is used to group 2 to 30 people who attended the same meeting e.g The attendee will have a ServiceID(PK), Date, Time, Meeting Room, Speaker,...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 16, 2010 at 7:07 pm
GSquared (3/16/2010)
Jeff, it's c. 60M rows per month, because of the prefix. That's probably enough for most business purposes (unless you're Amazon, Google, et al).
Heh... Yep. I forgot...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 16, 2010 at 7:00 pm
The Dixie Flatline (3/16/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 16, 2010 at 7:02 am
sturner (3/12/2010)
sure, shoot me a private message with an email address.
Nah... do here... in the open where everyone can learn.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 15, 2010 at 10:47 pm
I have a requirement to run a stored procedure that does a lot of heavy processing.
I agree with Jeffrey above. I'll add that anytime I see the words "heavy...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 15, 2010 at 10:23 pm
Along with all the other problems people have stated (some having legal impact), the "code" also violates a couple of normal forms because it records 3 different pieces of information...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 15, 2010 at 9:40 pm
15 Hours? It would appear that, in your case, denormalization for reporting puposes is the wrong thing to do. I'd consider a more normalized approach that uses performance...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 15, 2010 at 9:23 pm
jarjarlee (3/15/2010)
You should use a funcation.define a funcation like
CREATE FUNCTION [dbo].[SplittingByDot]
(
@SourceData varchar(255)
)
RETURNS NVARCHAR
AS
BEGIN
......
END
then use the
SELECT dbo.SplittingByDot(OutlineNumber) FROM dbo.Tally
get the result
Other than...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 15, 2010 at 8:58 pm
mister.magoo (3/15/2010)
There is another problem with the previous solution
Which previous solution? π
--Jeff Moden
Change is inevitable... Change for the better is not.
March 15, 2010 at 8:01 pm
monitor89 (3/15/2010)
Got it figured out...Original
substr(h.dob,5,2) || right(h.dob,2) || left(h.dob,4) as Birth_Date,
New
substr(h.dob,5,2) || '/' || right(h.dob,2) || '/' || left(h.dob,4) as Birth_Date,
...pretty easy actually.
How about ...
TO_CHAR(TO_DATE(h.dob,'yyyymmdd'), 'mm/dd/yyyy') AS Birth_Date
π
--Jeff Moden
Change is inevitable... Change for the better is not.
March 15, 2010 at 7:55 pm
Lynn Pettis (3/14/2010)
snowshoes
One Post. π
--Jeff Moden
Change is inevitable... Change for the better is not.
March 15, 2010 at 7:36 pm
Kit G (3/15/2010)
But alas, intelligence is not a pre-requisite for becoming a pirate.
BWAA-HAAA!!!! According to some of the posts I've seen lately, it's not essentially required to be a...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 15, 2010 at 7:35 pm
karthik -450760 (3/15/2010)
Thanks Jeff. I have attached the text file. Below is my create table stmt and Bulk Insert Statement.
Thanks Karthik... I have to ask though... is that an actual...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 15, 2010 at 7:18 pm
Viewing 15 posts - 39,286 through 39,300 (of 59,072 total)