Viewing 15 posts - 49,171 through 49,185 (of 59,093 total)
Ian Scarlett (7/17/2008)
ISQL/W is actually Query Analyzer.ISQL is the earlier command line interface for doing the same thing as Query Analyser (i.e running queries and getting back results)
Not true... ISQL...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 17, 2008 at 7:46 pm
Its real hard to troubleshoot a problem without any code or data examples... please see the link in my signature line below.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 17, 2008 at 7:41 pm
A calendar table is good to have. Or, you can do it with a simple formula and then subtract the holidays listed in a Holiday table. The following...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 17, 2008 at 7:30 pm
Very nicely done! The 1st and 2nd articles take a lot of the mystery out of this task and really make it simple. I've not had to do...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 17, 2008 at 6:39 pm
What if you boss asked you to work on your "soft" skills.
I'd take the nice Oak bat home and bring in a nice "soft" Pine bat 😛
I'm a teacher at...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 17, 2008 at 2:29 pm
blandry (7/17/2008)
If there is not enough cache on hand and both will eventually hit TempDB - is the only advantage that Table variables dont hit it explicitly to start?
Not quite...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 17, 2008 at 2:15 pm
If you're really going to consider performance and storage, then stop thinking Cursors or While loops and stop thinking about a 5 million row temp table. Make a permanent...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 17, 2008 at 1:38 pm
ALI (7/17/2008)
Thanks for your comments.I did solve above issue and got stuck with other. As I have tight production deadlines, I am going for cursor in a stored procedure.
See...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 17, 2008 at 12:15 pm
karthikeyan (7/17/2008)
What size column do you thing NAME = '' will make?
Jeff,
Thanks for highlighting this area.
I have executed my previous code.
select distinct ID, Name =''
into #t1
from T
update #t1
set #t1.Name...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 17, 2008 at 12:11 pm
tony.sawyer (7/17/2008)
The solution provided used a case statement where the...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 17, 2008 at 12:08 pm
I'm in the process of writing an article about Crosstabs and Pivots... hope to finish it soon but one of the things I'm finding out in testing is that, except...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 17, 2008 at 6:04 am
Jeff Moden (7/16/2008)
karthikeyan (7/16/2008)
Jeff,how about my code ?
What size column do you thing NAME = '' will make? Also, look at the update... which NAME shall it use to...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 17, 2008 at 5:54 am
The best thing for this is a "Crosstab Report"... and it's easier than the PIVOT operator...
--===== Create and populate a test table
-- THIS IS NOT...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 16, 2008 at 9:17 pm
This is right on the border line of me thinking this is some type of homework... please post a decent try!
I will give you a hint, though... lookup GROUP BY.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 16, 2008 at 5:35 pm
karthikeyan (7/16/2008)
which one is good when we think performance ?
Try it... let us know...
--===== Create and populate a 1,000,000 row test table.
-- Column "RowNum" has...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 16, 2008 at 8:45 am
Viewing 15 posts - 49,171 through 49,185 (of 59,093 total)