also take a look at KB 832674 (hotfix available !)

If you want to create proc SP_ADD_SCRAP_EXCEPTION_REVIEW2

      from within SP_ADD_SCRAP_EXCEPTION_REVIEW1,

     you'll have to use exec(@sql).

Else

     put a GO before the second create proc statement

end if

Found it !

Define your @sql variable varchar(500).

It is now defined to short !!

  Declare @sql varchar(100)

  Set @repIds = 'Z30'

  Set...

how about :

EXEC master..xp_logininfo @acctname = 'yourdomain\yourgroup',@option = 'members'    

cmd.Parameters.Append cmd.CreateParameter ("@TableName",adChar,adParamInput,3,"Z30")

vs

CREATE Proc LateResponses(@stableName char(3),@idCount int output,@idList varchar(500) output)

should give a unknown parameter.

Because you dynamicaly define the cursor, your users will have...

did you refresh all views that might have used the column with the datatype ?

How about this :

Create Function dbo.udf_Get_Nth_DayNo_After

(  @Start_DateTime AS datetime

 , @End_DateTime AS datetime = '9999-12-31'

 , @SearchDayNr as tinyint  = 1

 , @nth as tinyint = 1

 , @hh_time as char(2)  =...

Lets assume speed is the issue and the FK-cannot be touched over here and

Sheilesh Paliwal cannot wait until the normal maintenance time.

Maybe...

maybe you'll find your answer overhere : http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=8&messageid=127910

Check the connection objects to the server who's sa-pwd you've changed in your dts-packages !

After you altered the sa-password, did you stop/start that server's sqlagent ?

In EM :

Tools / Options / advanced :

you can set : - Login timeout

                   - Query timeout

                   - packet size

Create the PK in line with the create table statement.

create table #tmpMytable (col_id integer not null primary key

                , col2 datetime not null default getdate()

                , .... )

or

create...

Can you have them using a view ?

if yes, provide a view like this :

Create myschema.myview

as

select mycol1,..

  from myschema.mytable (NOLOCK)

This way they will not lock the rows...

as you have noticed NULL <> ' '

If there is no symantic difference for your schema and apps, avoid the NULL.

Thanks for the good advice Offcourse one has to choose a wife who enjoys the bike as well