So going back to my lookup table example with an ID and Description column I should be better off putting my clustered index on my description column rather than on...

In your C# you define your sqlparameter in exactly the same way as you would any other parameter but parameter.direction =ParameterDirection.Output.

You datatypes match those being submitted to the procedure. ...

So basically the argument against them is that they are entirely artificial values that are independent of the data?

I'm not sure what the argument is against using them in clustered...

If you look at the way that EM does it.

CREATE TABLE dbo.tmp_yourtablename ( the new field list )

IF EXISTS(SELECT * FROM dbo.tmp_yourtablename)

EXEC('INSERT INTO dbo.dbo.tmp_yourtablename (the new field list)

SELECT the...

It is just as valid as

BEGIN

SELECT 0 AS ls_action

END

It is just a different way of writing it.

Hang on, if you put a clustered primary key on a table where the primary key isn't naturally ordered doesn't it increase the page splits?

So although fragmentation per se does...

It depends on the design of your table. Is there something that will identify the updated records?

If so I would be tempted to have some form of loop to...

If you run SELECT System_User it brings back the login name that you are currently logged in as.

You can create a table that maps System_User to region and then do...

I would remove it from MODEL.

I have removed it from MSDB in my environment with no ill effects but I am not doing any complicated development with DTS or SQLServerAgent...

You cannot remove guest from either master or tempdb.

If you remove it from MODEL then it won't appear in any future databases that you add to the system. MODEL...

I start with the assumption that I need a TEMPDB three times the size of my largest table.

If I have to do a large sort or reindex TEMPDB grows...

If you don't specify otherwise a primary key will be clustered. If the columns that you are proposing to become primary keys are not naturally ordered then having them...

Read http://www.sqlservercentral.com/columnists/dpeterson/lookuptablemadness.asp

If you use foreign keys then I can see the potential for performance issues when it comes to deleting records.

If you look at the execution plan of a...

I've reached the age when I time things with a calendar.

There is a great story about one of the old British colonies where the accuracy of the town clock was...

I can't see a better way around the need to have a field per table.

If your database design allows there to be a "common properties" table then your UpdatedDate field...