|
|
|
Grasshopper
      
Group: General Forum Members
Last Login: Wednesday, March 06, 2013 9:03 AM
Points: 20,
Visits: 60
|
|
Hi All
I have 2 tables.
Table 1 MasterDefects
Field1: Department Field2: Process Field3: Type Field4: Defect
Table 2 Results Field1: Department Field2: Process Field3: Type Field4: Defect Field5: ShiftID Field6: SizeID Field7: Amount Field8: ShiftBox
If MasterDefects has 7 rows
Department:::::Process:::::Type:::::::::::Defect Timber::::::::::CrossCut::::Wood Fault::::Fallen Out Knot Timber::::::::::CrossCut::::Wood Fault::::Resin Pocket Timber::::::::::CrossCut::::Wood Fault::::Large Knot Timber::::::::::CrossCut::::Wood Fault::::Wet Timber Timber::::::::::CrossCut::::Wood Fault::::Wood Rott Timber::::::::::CrossCut::::Wood Fault::::Blue Stain Timber::::::::::CrossCut::::Wood Fault::::Chipped Off
And my Results had
Department:::::Process:::::Type:::::::::::Defect::::::::::::ShiftID:::::SizeID:::Amount:::ShiftBox Timber::::::::::CrossCut::::Wood Fault::::Fallen Out Knot:::1ae::::::::1des:::::1::::::::::RTO1 Timber::::::::::CrossCut::::Wood Fault::::Fallen Out Knot:::1ae::::::::1des:::::1::::::::::RTO1 Timber::::::::::CrossCut::::Wood Fault::::Fallen Out Knot:::1ae::::::::1des:::::1::::::::::RTO1 Timber::::::::::CrossCut::::Wood Fault::::Resin Pocket::::::1ae::::::::1des:::::1::::::::::RTO1 Timber::::::::::CrossCut::::Wood Fault::::Resin Pocket::::::1ae::::::::1des:::::1::::::::::RTO1 Timber::::::::::CrossCut::::Wood Fault::::Large Knot::::::::1ae::::::::1des:::::1::::::::::RTO1
How can I combine the 2 table in a query to get
Department:::::Process:::::Type:::::::::::Defect::::::::::::ShiftID:::::SizeID:::Amount:::ShiftBox Timber::::::::::CrossCut::::Wood Fault::::Fallen Out Knot:::1ae::::::::1des:::::3::::::::::RTO1 Timber::::::::::CrossCut::::Wood Fault::::Resin Pocket::::::1ae::::::::1des:::::2::::::::::RTO1 Timber::::::::::CrossCut::::Wood Fault::::Large Knot::::::::1ae::::::::1des:::::1::::::::::RTO1 Timber::::::::::CrossCut::::Wood Fault::::Wet Timber:::::::Null:::::::::Null::::::Null:::::::Null Timber::::::::::CrossCut::::Wood Fault::::Wood Rott::::::::Null:::::::::Null::::::Null:::::::Null Timber::::::::::CrossCut::::Wood Fault::::Blue Stain:::::::::Null:::::::::Null::::::Null:::::::Null Timber::::::::::CrossCut::::Wood Fault::::Chipped Off:::::::Null:::::::::Null::::::Null:::::::Null
I have tried left and right Inner and Outer Joins but I just cant get the query to show the above.
Cheers
DJ
|
|
|
|
|
SSC Veteran
      
Group: General Forum Members
Last Login: Yesterday @ 2:32 AM
Points: 276,
Visits: 797
|
|
Try this:
if object_id('dbo.MasterDefects') is not null drop table dbo.MasterDefects; if object_id('dbo.Results') is not null drop table dbo.Results;
create table dbo.MasterDefects ( Department Varchar(20), Process Varchar(20), Type Varchar(20), Defect Varchar(20) );
insert dbo.MasterDefects values ( 'Timber', 'CrossCut', 'Wood Fault', 'Fallen Out Knot' ); insert dbo.MasterDefects values ( 'Timber', 'CrossCut', 'Wood Fault', 'Resin Pocket' ); insert dbo.MasterDefects values ( 'Timber', 'CrossCut', 'Wood Fault', 'Large Knot' ); insert dbo.MasterDefects values ( 'Timber', 'CrossCut', 'Wood Fault', 'Wet Timber' ); insert dbo.MasterDefects values ( 'Timber', 'CrossCut', 'Wood Fault', 'Wood Rott' ); insert dbo.MasterDefects values ( 'Timber', 'CrossCut', 'Wood Fault', 'Blue Stain' ); insert dbo.MasterDefects values ( 'Timber', 'CrossCut', 'Wood Fault', 'Chipped Off' );
create table dbo.Results ( Department Varchar(20), Process Varchar(20), Type Varchar(20), Defect Varchar(20), ShiftID Varchar(20), SizeID Varchar(20), Amount int, ShiftBox Varchar(20) );
insert dbo.Results values ( 'Timber', 'CrossCut', 'Wood Fault', 'Fallen Out Knot', '1ae', '1des', 1, 'RTO1' ); insert dbo.Results values ( 'Timber', 'CrossCut', 'Wood Fault', 'Fallen Out Knot', '1ae', '1des', 1, 'RTO1' ); insert dbo.Results values ( 'Timber', 'CrossCut', 'Wood Fault', 'Fallen Out Knot', '1ae', '1des', 1, 'RTO1' ); insert dbo.Results values ( 'Timber', 'CrossCut', 'Wood Fault', 'Resin Pocket', '1ae', '1des', 1, 'RTO1' ); insert dbo.Results values ( 'Timber', 'CrossCut', 'Wood Fault', 'Resin Pocket', '1ae', '1des', 1, 'RTO1' ); insert dbo.Results values ( 'Timber', 'CrossCut', 'Wood Fault', 'Large Knot', '1ae', '1des', 1, 'RTO1' );
SELECT M.Department, M.Process, M.Type, M.Defect, R.ShiftID, R.SizeID, SUM(R.Amount) as Amount, R.ShiftBox FROM MasterDefects M LEFT OUTER JOIN Results R ON M.Department=R.Department AND M.Process= R.Process AND M.Type=R.Type AND M.Defect=R.Defect GROUP BY M.Department, M.Process, M.Type, M.Defect, R.ShiftID, R.SizeID, R.ShiftBox;
Edit: Corrected. Results not in the same order - DK if that matters.
If you supply test data in a format that can be run, more people will be likely to help!
|
|
|
|
|
Grasshopper
      
Group: General Forum Members
Last Login: Wednesday, March 06, 2013 9:03 AM
Points: 20,
Visits: 60
|
|
Hi
Both tables are far to large as this is a running system to give a copy, I am just trying to create a query for a report.
Your Select Statement is exactly what I tried, it displays all the information for Masterdefects, includes the columns for results but just gives null values for the result colum set.
Cheers
DJ
|
|
|
|
|
SSC Eights!
      
Group: General Forum Members
Last Login: 2 days ago @ 4:59 PM
Points: 960,
Visits: 1,924
|
|
Both tables are far to large as this is a running system to give a copy, I am just trying to create a query for a report.
That's why you're asked only for sample data . You did posted sample data but Laurie had to code the DDL and the INSERTs to recreate it. As we're all volunteers, we ask you to provide us with the data in this format so we can concentrate in your problem. Read the article linked in my signature for a better explanation.
Luis C. Please don't trust me, test the solutions I give you before using them. Forum Etiquette: How to post data/code on a forum to get the best help
|
|
|
|
|
Grasshopper
      
Group: General Forum Members
Last Login: Wednesday, March 06, 2013 9:03 AM
Points: 20,
Visits: 60
|
|
Hi Laurie
Spent a bit of time on this, this morning. I couldnt figure out why your example worked but my query didnt. Looked through all the data in my tables and realised that there was a space at the end of my process in my results. So I changed my querey slightly to do a RTRIM on the end of the process field.
Everything works perfectly, thanks for the help.
|
|
|
|
|
SSC Veteran
      
Group: General Forum Members
Last Login: Yesterday @ 2:32 AM
Points: 276,
Visits: 797
|
|
No problem
|
|
|
|
|
SSCommitted
      
Group: General Forum Members
Last Login: Tuesday, January 15, 2013 11:11 AM
Points: 1,945,
Visits: 2,782
|
|
I have 2 tables.
Please post DDL, so that people do not have to guess what the keys, constraints, Declarative Referential Integrity, data types, etc. in your schema are. If you know how, follow ISO-11179 data element naming conventions and formatting rules (you don't). Temporal data should use ISO-8601 formats. Code should be in Standard SQL as much as possible and not local dialect.
It is obvious you have never done a data model before, so let's go thru it slowly.
The term “master” was used in tape files and early non-RDBMS systems; it is not part of RDBMS terminology. Likewise, tape file records have fields, but tables have columns; this is not terminology, but fundamental concepts.
The four columns you have should be combined into a single defect code. Have you been to a library and seen the Dewey Decimal Classification? This is a hierarchical encoding system, but there are also vector
Here is a clean up of what you have now. Notice the “<attribute>_<attribute property>” syntax for data element names:
CREATE TABLE Defects (department_name CHAR(10) NOT NULL, process_name CHAR(10) NOT NULL, defect_type CHAR(10) NOT NULL, defect_code CHAR(10) NOT NULL, PRIMARY KEY (department_name, process_name, defect_type, defect_code));
CREATE TABLE Defects (defect_code CHAR(10) NOT NULL PRIMARY KEY CHECK (defect-code LIKE '[0-9][0-9]-[0-9][0-9]-[0-9][0-9][0-9]'), defect_description VARCHAR(100) NOT NULL);
where the defect code is a hierarchy with those components. I have no idea or the specs from which to design that decoding. I gave a dummy to have something to talk about. There is no such thing as a “size_id”; look at your shoes, they have a “shoe_size” because size is a measurement on some scale of the dimension of something in particular, not an entity with an identifier. Amount is usually a dollar figure, but yours look like a count
CREATE TABLE Defect_Reports (defect_code CHAR(10) NOT NULL REFERENCES Defects(defect_code) ON UPDATE CASCADE, shift_id CHAR(5) NOT NULL CHECK (??), foobar_size CHAR(3) NOT NULL, defect_cnt SMALLINT DEFAULT 1 NOT NULL, shiftbox_nbr CHAR(5) NOT NULL, PRIMARY KEY (defect_code, foobar_size, shiftbox_nbr));
It looks like you want a LEFT OUTER JOIN to preserve the defect codes
SELECT D.defect_code, R.foobar_size, R.shiftbox_nbr, SUM (R.defect_cnt) AS defect_cnt_tot FROM Defects AS D LEFT OUTER JOIN Defect_Reports AS R ON D.defect_code = R.defect_code GROUP BY D.defect_code, R.foobar_size, R.shiftbox_nbr;
You might want to get a copy of THINKING IN SETS and read the parts on encoding schemes.
Books in Celko Series for Morgan-Kaufmann Publishing Analytics and OLAP in SQL Data and Databases: Concepts in Practice Data, Measurements and Standards in SQL SQL for Smarties SQL Programming Style SQL Puzzles and Answers Thinking in Sets Trees and Hierarchies in SQL
|
|
|
|
|
SSC-Dedicated
           
Group: General Forum Members
Last Login: Yesterday @ 7:36 PM
Points: 32,931,
Visits: 26,820
|
|
Ok. Now I'm surprised at you, Joe. The first thing I'd do to a Dewey Decimal system is to convert it to Nested Sets so you can more easily query it.
--Jeff Moden "RBAR is pronounced "ree-bar" and is a "Modenism" for "Row-By-Agonizing-Row".
First step towards the paradigm shift of writing Set Based code: Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column."
For better, quicker answers on T-SQL questions, click on the following... http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following... http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
|
|
|
|
|
SSCommitted
      
Group: General Forum Members
Last Login: Tuesday, January 15, 2013 11:11 AM
Points: 1,945,
Visits: 2,782
|
|
Now I'm surprised at you, Joe. The first thing I'd do to a Dewey Decimal system is to convert it to Nested Sets so you can more easily query it.
LOL! There is not much easier than WHERE ddc LIKE '51_.%' for finding math books in one table. This is structure (Dewey) versus relations (org charts) -- maybe there is an article in this.
Books in Celko Series for Morgan-Kaufmann Publishing Analytics and OLAP in SQL Data and Databases: Concepts in Practice Data, Measurements and Standards in SQL SQL for Smarties SQL Programming Style SQL Puzzles and Answers Thinking in Sets Trees and Hierarchies in SQL
|
|
|
|
|
SSC-Dedicated
           
Group: General Forum Members
Last Login: Yesterday @ 7:36 PM
Points: 32,931,
Visits: 26,820
|
|
CELKO (9/29/2012)
Now I'm surprised at you, Joe. The first thing I'd do to a Dewey Decimal system is to convert it to Nested Sets so you can more easily query it. LOL! There is not much easier than WHERE ddc LIKE '51_.%' for finding math books in one table. This is structure (Dewey) versus relations (org charts) -- maybe there is an article in this.
I have to admit, that's one numbering system where that would actually work quite effectively because there's virtually no overlap of subcategories (hierarchical level) that you might want to search on.
--Jeff Moden "RBAR is pronounced "ree-bar" and is a "Modenism" for "Row-By-Agonizing-Row".
First step towards the paradigm shift of writing Set Based code: Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column."
For better, quicker answers on T-SQL questions, click on the following... http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following... http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
|
|
|
|