Viewing 15 posts - 37,291 through 37,305 (of 59,098 total)
Alain Rastoul (8/17/2010)
Here you'll find 3 papers from E.F.Codd ,
A Relational Model of Data for Large Shared Data Banks
http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.98.5286&rep=rep1&type=pdf
Extending the Database Relational Model to Capture More Meaning
http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.84.9469&rep=rep1&type=pdf
RELATIONAL COMPLETENESS OF...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 17, 2010 at 8:13 am
gary.bland (8/16/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
August 16, 2010 at 8:20 pm
dma-669038 (8/16/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
August 16, 2010 at 8:13 pm
Steve Jones - Editor (8/16/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
August 16, 2010 at 7:58 pm
mtillman-921105 (8/16/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
August 16, 2010 at 7:46 pm
Does anyone know what's up with the upcoming SQL Saturday in Minnesota? I see no speakers and no sessions. I've sent emails asking what's up and have gotten...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 16, 2010 at 7:02 am
Jack Corbett (8/16/2010)
GilaMonster (8/16/2010)
Jeff Moden (8/14/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
August 16, 2010 at 6:59 am
Perfect and well said. I had one job where I quite literally did just about everything for the company from learning how to run a letter folding machine to...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 15, 2010 at 10:08 pm
vrkn82 (8/15/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
August 15, 2010 at 9:43 pm
bitbucket-25253 (8/15/2010)
CREATE TABLE #T(C1 INT, C2 INT, C3 INT, C4 INT, C5 INT)
INSERT INTO #T
SELECT 1,1,1,1,0 UNION ALL
SELECT 1,1,1,0,1 UNION ALL
SELECT 1,1,0,1,1 UNION ALL
SELECT 1,0,1,1,1 UNION...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 15, 2010 at 9:41 pm
jeff.mason (8/9/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
August 15, 2010 at 9:36 pm
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
Viewing 15 posts - 37,291 through 37,305 (of 59,098 total)