create function dbo.digit ( @n varchar(40))

 returns int

 as

 begin

  declare @result int, @cntr int 

  select  @result = 0, @n = replace(rtrim(ltrim(@n)),'.','')

  set @cntr = len(@n)

  While @cntr > 0

  begin

   set @result...

I personally don't think that you are going to persive a big hit because of that change. I would worry if you were to use those columns for range , ordered...

but even when is being run from a stored proc on sql box you still have to be worry about sql injection and guard really well those parameters!

What Happens is that DBCC DBREINDEX is usually employed with tableName and indexName to pick and choose what to rebuild (you omitted how was this being run 

two choises:

1. Create a separate operator wich has the email address of a distribution list in which you keep the addresses of all those operators

2. Create aq second step on...

Identity is a PROPERTY. Primary Key is a CONSTRAINT.

Therefore only a Primary key or a unique constraint guarantee uniqueness.

 Primary Key also prevents nulls

Please, Do not Double Post. See my point view on this thread:

http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=9&messageid=177164

The error that you get is on the Left function that can't perform well with a money type!

EXEC

(

'SELECT ''' + @TableName + '.' + @ColumnName + ''',