Database

<code>
-- =============================================
-- Author:		Martin Arapovic
-- Create date: 19.01.2011
-- Description:	....
-- =============================================
CREATE PROCEDURE InsertUserData 
	(
		-- Add the parameters for the stored procedure here
		-- Define needed parameters
		-- Contact Input Data
		@Street VARCHAR(50), 
		@City VARCHAR(50), 
		@State VARCHAR(50), 
		@EmailAddress VARCHAR(50),
		--Users Input Data
		@UserName VARCHAR(25), 
		@Password VARCHAR(25),
		-- User Input Data
		@FirstName varchar(50),
		@LastName varchar(50),
		@Sex varchar(50)
		-- Add other paramas if you have any
	)
AS
BEGIN
	-- SET NOCOUNT ON added to prevent extra result sets from
	-- interfering with SELECT statements.
	SET NOCOUNT ON;

	DECLARE @ContactID INT 
	DECLARE @AuthenticationID INT 
	
	--
	-- Note: This is only skeleton of the proc that you want to implement
	
	--
	-- Do all in one transaction
	
	BEGIN TRANSACTION
	
	--
    -- Insert Contact data and get ContactID
    INSERT INTO [Contact]
           ([Street]
           ,[City]
           ,[State]
           ,[EmailAddress])
     VALUES
           (@Street
           ,@City
           ,@State
           ,@EmailAddress)
           
    -- GET CointactID 
    SET @ContactID = SCOPE_IDENTITY() 
     
    --
    -- Insert Authentication data and get AuthenticationID
    INSERT INTO [Authentication]
           ([UserName]
           ,[Password])
     VALUES
           (@UserName
           ,@Password)
           
    -- GET Authentication 
    SET @AuthenticationID = SCOPE_IDENTITY() 
     
    -- 
    -- Insert Users data into users table.
    INSERT INTO [Users]
           ([FirstName]
           ,[LastName]
           ,[Sex]
           ,[AuthenticationID]
           ,[ContactID])
     VALUES
           (@FirstName
           ,@LastName
           ,@Sex
           ,@AuthenticationID
           ,@ContactID)

     -- Commit
     COMMIT TRANSACTION
     
     -- This is the general example and you need to add error handling and 
     -- other bussines logic if you have any... :)
           	
END
GO
</code>

SELECT D1.[DepartmentID]
      ,D1.[Name]
      ,D1.[GroupName]
      ,D1.[ModifiedDate]
FROM [AdventureWorks].[HumanResources].[Department] D1
LEFT JOIN [AdventureWorks2008R2].[HumanResources].[Department] D2
ON D1.DepartmentID = D2.DepartmentID 
WHERE D2.DepartmentID IS NULL

vanikanc wrote:

Is there a way to compare data of the same table in two different databases?

vanikanc wrote:

Thanks!

Naerling wrote:

the usage of views

Naerling wrote:

One of my boss' arguments was that one table to store 'all' settings is rather handy because it keeps the amount of tables low and you can always find a setting (for whatever) in one table.

Naerling wrote:

I know there are some rules for normalizing and denormalizing, but rules are meant to be broken

I are Troll

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