Viewing 15 posts - 37,276 through 37,290 (of 59,072 total)
Dave Hoogendoorn (8/15/2010)
Changing the query to explicit INNER JOINs with ON statements might prevent improper execution plan.
In your current query, their might be a possibility that SQL first joins...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 15, 2010 at 9:25 pm
Rajiv Kumar (8/14/2010)
EmpID Name ManagerID
against each employee, manager id is avaiable and a manager is also an employee...
i need a sql...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 15, 2010 at 9:22 pm
Rajiv Kumar (8/14/2010)
EmpID Name ManagerID
against each employee, manager id is avaiable and a manager is also an employee...
i need a sql...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 15, 2010 at 9:20 pm
To answer your question, "Yes".
To solve your problem, please see the following. Post back if you have questions but try the code first... you can do some amazing stuff...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 15, 2010 at 9:06 pm
robertfolkerts (7/22/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
August 15, 2010 at 9:02 pm
dbuendiab (8/15/2010)
SQLZ (8/13/2010)
The thing I'd like to pick up on, that drew my attention, was your reasons for moving away...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 15, 2010 at 11:55 am
Steve Jones - Editor (7/15/2010)
Just wondering if this has fallen off everyone's radar?
Heh... oh my! Another month has gone by and nothing has happened on the SharePoint site since...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 14, 2010 at 11:49 pm
Heh... Well said, Tom. I LOVE "evil concepts" especially in T-SQL. 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
August 14, 2010 at 1:23 pm
Paul White NZ (8/14/2010)
Jeff Moden (8/13/2010)
Paul White NZ (8/12/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
August 14, 2010 at 1:01 pm
WayneS (8/9/2010)
Jeff Moden (8/8/2010)
drew.allen (8/7/2010)
Here's an example using the Information_Schema.Tables view. WARNING: XML is case sensitive
Thanks, Drew. Rumor has it that it's also pretty touchy about special characters...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 14, 2010 at 12:36 pm
WayneS (8/6/2010)
CirquedeSQLeil (8/6/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
August 14, 2010 at 12:29 pm
David Burrows (8/10/2010)
but this is ...poor design
poor query
poor performance
as will be shown when Jeff catigates me for even dare to post this 😀
Heh... only for the spelling 😛 because, like...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 14, 2010 at 12:23 pm
Ah... sorry, my apologies. I thought I'd posted the 8k splitter code on this thread before. Guess not. So, here it is. It's mostly comments to...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 14, 2010 at 12:09 pm
Ok... here we go with a test for Alex's function. I was right about the CTE still being "Hidden RBAR" even though it uses all variables and is an...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 14, 2010 at 12:00 pm
Alex Grinberg-230981 (8/13/2010)
CREATE FUNCTION [dbo].[StringToTable]
(@RawString nvarchar(4000), @Delimiter nvarchar(10) )
RETURNS
@VList TABLE ...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 14, 2010 at 11:23 am
Viewing 15 posts - 37,276 through 37,290 (of 59,072 total)