Database

Naerling wrote:

"it's easy that all settings are in one table"

Naerling wrote:

"you always know where to find a setting"

Naerling wrote:

"normalizing isn't always a good thing"

Naerling wrote:

Actually there is no key or constraint at this table at all!

Naerling wrote:

There is good news though. It's a very old table which was created with the best of intents at a time that my company did not know very much about SQL Server (migrated from DBF). We only keep it because redesigning this part of our DB (and software) would cost to much time at this moment. My boss does not think the table is good, it's just 'not that bad'

I are Troll

Naerling wrote:

Instead he said I should've made 1 extra (maybe he reads this forum too?)

Naerling wrote:

Don't start about on On Error Resume Next..

I are Troll

select * from TABLE1 t1
 where not exists ( select * from TABLE2 t2 where t1.key = t2.key )
union all
select * from TABLE2 t2
 where not exists ( select * from TABLE1 t1 where t2.key = t1.key )

Msg 205, Level 16, State 1, Line 1<br />
All queries combined using a UNION, INTERSECT or EXCEPT operator must have an equal number of expressions in their target lists.

CREATE TABLE #first
(
	Id INT NOT NULL,
	Name VARCHAR(10) NOT NULL
);

CREATE TABLE #second
(
	Id INT NOT NULL,
	Name VARCHAR(10) NOT NULL
);

INSERT INTO #first (Id, Name) VALUES (1, 'One');
INSERT INTO #first (Id, Name) VALUES (2, 'Two');
INSERT INTO #first (Id, Name) VALUES (3, 'Three');
INSERT INTO #first (Id, Name) VALUES (9, 'Nine');

INSERT INTO #second (Id, Name) VALUES (2, 'Two');
INSERT INTO #second (Id, Name) VALUES (3, 'Three');
INSERT INTO #second (Id, Name) VALUES (5, 'Five');
INSERT INTO #second (Id, Name) VALUES (7, 'Seven');

SELECT f.Id AS fid, 
	f.Name AS fname,
	s.Id AS [sid],
	s.Name AS sname
FROM #first f
	FULL OUTER JOIN #second s
		ON s.Id = f.Id
WHERE s.Id IS NULL OR f.Id IS NULL

DROP TABLE #first;
DROP TABLE #second;

select *
into database.owner.tablename
from table