Posted by Erland Sommarskog on 06/02/05 23:25

md (markydev@gmail.com) writes:
> 2nd sql:- when adding the indentity field to my table I presumed an
> index would be created. This was not the case, so I created this index
> and now the sql works ok.

The only case indexes are created implicitly in SQL Server is when you
define a PRIMARY KEY or UNIQUE constraint. IDENTITY columns or FOREIGN
KEY columns do not come with an index, unless you actually create one.


--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp

• Next in forum: Re: Getting Data from a storeed procedure in a stored procedure
• Prev in forum: Re: One-to-many with a twist
• Thread view: Re: update sql errors using linked server

[Reply to this message]