One thing to watch out for, though: if you have foriegn key constraints that are dependent on the IDENTITY key, then you will have to DROP the constraints before you...

AHA, now I see what you were trying to do...

Your best bet is to just create a new table that is a duplicate of your old table, then COPY the...

Thanks, Frank. Cheers.

Use the IDENTITY attribute in the ALTER/CREATE TABLE statement to specify the increment value. Look in BooksOnLine, "ALTER TABLE", or "IDENTITY" for more information. BTW, the table is...

SELECT 

  'Announcement'

, ItemID

, ModuleID

, CreatedByUser

, CreatedByDate

FROM Announcements

WHERE 

DATEADD(d, 0, DATEDIFF(d, 0, CreateDate)) >= DATEADD(d, -7, DATEDIFF(d, 0, GETDATE())

UNION

SELECT 

  'Document'

, ItemID

, ModuleID

, CreatedByUser

,...

quote:

---

Well, that is not helpful . I ended up changing to "IF..Then" but seems like there should be...

-- Be sure to declare variables output in

-- the execute line of the batch...

declare @input1 varchar(10)

declare @input2 varchar(10)

declare @output1 varchar(10)

declare @output2 varchar(10)

--

execute myProc @input1, @input2, @output1...

declare @seconds int

--

set @seconds = 124

--

select convert(varchar(2), floor(@seconds/60)) + ':' + right('0' + convert(varchar(2), (@seconds%60)), 2)

select top 100 so.name, sc.text 

from sysobjects so

  inner join syscomments sc 

    on so.id = sc.id

where so.xtype = 'P' 

and patindex('%TableName%',...

CASE should go in a SELECT statement. In other words, either change your statement to a SELECT, or change your case statements to an IF block. Remember, CASE...

DECLARE @LockDateBegin SMALLDATETIME

SELECT @LockDateBegin =

CASE

WHEN (DATEPART(dw, GETDATE() = 3

AND DATEPART(hh, GETDATE() >= 16) THEN

...

Books Online suggests putting the database into single-user mode for the during of the operation causing this error, if possible. Also, since you are using TRUNCATE TABLE, it is...

BTW, what version of SQL Server are you running?

Really not quite sure. Unless you can identify some sort of patterns as to when the job fails, I'm not sure why the proc would return that error, particularly...

When do you run such a procedure, and how often? There doesn't seem to anything particularly unusual about the procedure, unless the tables in question are enormous and the...