Viewing 15 posts - 41,566 through 41,580 (of 59,102 total)
Thanks for the offer, Seth, but in light of the other posts, there's no need unless you can remember the exception you're thinking of. It also seems to me...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 12, 2009 at 7:39 pm
Great points, George... thanks.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 12, 2009 at 6:46 pm
Use Lutz's fine example as a derived table and do a join between that and your other column sources. Don't add extra columns to the GROUP BY that are...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 12, 2009 at 6:39 pm
Garadin (10/12/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
October 12, 2009 at 6:33 pm
newbie2009 (10/9/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
October 12, 2009 at 6:31 pm
giri,
If you'd share the business reason behind this requirement (I'm always curious), I believe I may have a way to pull it off.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 12, 2009 at 3:03 pm
Some reads are actually logical reads from cached data in memory while others are physical reads. I've found that reducing the number of reads usually results in more efficient...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 12, 2009 at 2:55 pm
Sorry folks... I lost track of this one...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 11, 2009 at 9:11 am
@Jorge
From the blog...
First day of class will start on Monday, September 28th
How do we find these classes? I don't see them on the blog.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 10, 2009 at 11:45 pm
You don't need a CLR for this...
http://www.sqlservercentral.com/articles/T-SQL/63003/
--Jeff Moden
Change is inevitable... Change for the better is not.
October 10, 2009 at 11:36 pm
Thanks for the offer. I appreciate it. Of course, I'll definitely throw the bone in the right direction on that.
By the way... thanks... I lost track of that...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 10, 2009 at 11:22 pm
Cool... can you post it? I'd love to see it.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 10, 2009 at 1:53 pm
arun.sas (9/9/2009)
neo_pom (9/9/2009)
If a column keeps email address look like thesep@hotmail.com;a@hotmail.com
I'd like count '@' in the column
How can I write TSQL just only one statement(without loop) to do that ?
Hi,
Suppose...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 10, 2009 at 10:18 am
PaulB-TheOneAndOnly (9/22/2009)
pandeharsh (9/12/2009)
Also,I read here that,we should avoid cursor as much as possible.
This is not correct. Is like saying you should avoid surgery as much as possible - why if...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 10, 2009 at 10:05 am
I've not testest this particular code but it should be close. It's a copy of the code above with a few "speed" tricks added...
DECLARE @emp VARCHAR(MAX)
SELECT ...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 10, 2009 at 10:01 am
Viewing 15 posts - 41,566 through 41,580 (of 59,102 total)