The default is only used when you don't specify a value.

Delete is a logged operation. Which means it can be pretty easily rolledback if it's an error. A truncate is not logged, therefore faster but cannot be easily...

That's exactly why an experienced dba is invaluable... it's just one of the 100+? gotchas that you'll find in sql server. You just got to learn them and try to...

The real problems comes from this.

Create view vwa

as

Select top 100 percent * from dbo.BigFatTable Order by Col1, Col2

Create Sp b

AS

Select *, (Select SomCol from dbo.vwa A where B.id = A.id)...

You need to add Select top 100 percent ...

in 2000, maybe that's the workaround you need in this case ron k

Finally someone else pointed out the obvious .

Can't answer your question as I avoid cursor like the pest. Good luck... btw I also avoid order by in views. Nice to see best practices pay off...

You still didn't answer the real question. Why the )(&?(*& r u fetching 26k rows in a cursor in a sp. I can't imagine that there's no way...

This is what you need :

The Curse and Blessings of Dynamic SQL

Why r u using a cursor to select 26k rows in a SP?

About the size... that would be a reason against a bad choice of Clustered index... not for a reason not to use it.

Just thaught of another reason... I have a dts package that pumps the data from an error log every 2 minutes. The data is then spread across 4...

The only valid reason I can think of is that the clustered index would need to be updated 10 000s times per minute (let's read extremely often here) and that...

I don't see why they wouldn't,

but I'd go with this :

ALTER TABLE tblAccount ADD

[MailServer] varchar(50) null -- just to make it obvious that the column will accept nulls.

BTW MailServer...

ALTER TABLE TableName ADD

NewColName /*datatype*/int /*null or not null, null is the default*/not null /*only if you need a default value*/ default(0)

GO