Viewing 15 posts - 31,006 through 31,020 (of 59,101 total)
Heh... I've been thinking about this and have decided that I probably shouldn't post solutions late at night because all the coffee has worn off. I believe that if...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 25, 2012 at 8:35 am
{EDIT} Please see my last coded post on this thread for a better answer.
Ah... got it. Let's rebuild the test using 2,000,000 rows and I'll show you. Read...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 24, 2012 at 11:47 pm
{EDIT} Please see my last coded post on this thread for a better answer.
The real problem is that you don't have the correct indexes on the table. Since the...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 24, 2012 at 9:50 pm
Ray K (2/24/2012)
--Jeff Moden
Change is inevitable... Change for the better is not.
February 24, 2012 at 7:39 pm
dwain.c (2/24/2012)
--Jeff Moden
Change is inevitable... Change for the better is not.
February 24, 2012 at 7:34 pm
mahesh15dec1986 (2/24/2012)
i have a data of year 2012 and table structure is (SN ,Name ,DATE,Error) and i need data according to
1 Jan 2012 to 5 Jan 2012- Week...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 24, 2012 at 7:11 pm
Eugene Elutin (2/24/2012)
Bipinkumar Yadav (2/24/2012)
Try This way..
DECLARE
@start_date DATETIME,
@end_date DATETIME,
@start_date1 DATETIME,
@end_date1 DATETIME
...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 24, 2012 at 7:07 pm
binodbabu (2/24/2012)
i got this error msg when i tried your script. could you please let me know where i am wrong. I am new sql learner.
thanks
Msg 8115, Level 16,...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 24, 2012 at 6:55 pm
raghuveer126 (2/24/2012)
--Jeff Moden
Change is inevitable... Change for the better is not.
February 24, 2012 at 6:49 pm
Cadavre (2/24/2012)
This will generate your 11,881,376 (!!) combinations
SELECT a.alpha+b.alpha+c.alpha+d.alpha+e.alpha
FROM (SELECT SUBSTRING('ABCDEFGHIJKLMNOPQRSTUVWXYZ',N,1) AS alpha
FROM (VALUES(1),(2),(3),(4),(5),(6),(7),(8),
...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 24, 2012 at 6:43 pm
Sorry... double post removed.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 24, 2012 at 6:41 pm
CELKO (2/24/2012)
CREATE VIEW Applicant_LocationsAS
SELECT A.*, L.location_id
FROM Applicants AS A, Locations AS L
WHERE A.postal_code = L.postal_code;
BWAAA-HAAA!!!!! Joe, you really should read the ANSI Standards so that...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 24, 2012 at 6:39 pm
mona770118 (2/19/2012)
Jeffthank you for your reply. I will post sample data tomorrow as I am at home now.
Did you work out an answer?
--Jeff Moden
Change is inevitable... Change for the better is not.
February 24, 2012 at 6:14 pm
sgtmango333 (2/24/2012)
Ummmm...the failure messages.
BWAAA-HAAA!!! Please post the actual code you're using, the failure messages, and anything else that you might be able to provide to help us help you....
--Jeff Moden
Change is inevitable... Change for the better is not.
February 24, 2012 at 5:53 pm
sgtmango333 (2/24/2012)
I used the script provided earlier in this thread. Yes, it was a varchar(max) and the resulting query built out to somewhere between 12k and 13k characters.
So, why...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 24, 2012 at 3:04 pm
Viewing 15 posts - 31,006 through 31,020 (of 59,101 total)