Posted by David Portas on 10/02/14 11:56

imani_technology_spam@yahoo.com wrote:
> Sorry, I guess the new table got cut off. Hopefully, this can help:
>
> CREATE TABLE [dbo].[Sensitivities](
> [SensiID] [smallint] IDENTITY(1,1) NOT NULL,
> [AntibioticID] [smallint] NULL,
> [SourceID] [smallint] NULL,
> [SusceptID] [smallint] NULL,
> [OrganismID] [smallint] NULL,
> [SensiNote] [varchar](255) COLLATE SQL_Latin1_General_CP1_CI_AS NULL,

You call that normalized!? Why make all those columns nullable? What is
the natural key supposed to be?

--
David Portas, SQL Server MVP

Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.

SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--

• Next in forum: Re: Can any one explain this query behavior
• Prev in forum: Re: Normalizing a Crosstab
• Thread view: Re: Normalizing a Crosstab

[Reply to this message]