Viewing 9 posts - 91 through 99 (of 99 total)
your problem is that any operation such as dropping a table is causing your trigger to run which is causing your error.
Try dropping the trigger first:
drop
September 13, 2006 at 5:50 am
What about using the script database function in sql server management studio? Right click the DB, script database as, create
September 4, 2006 at 5:38 am
The only way I can think of doing this is to use triggers.
September 4, 2006 at 5:32 am
Could you use a default constraint to generate a new id if one is not supplied?
September 1, 2006 at 5:37 am
I thought that even if Pluto was no longer technicaly a planet under their new clasification system it would retain its planet status for historical reasons.
August 30, 2006 at 2:01 am
It is only auditing the failed attempts .
August 10, 2006 at 2:22 am
Thats what I was looking for, thanks.
August 7, 2006 at 10:19 am
Ah, thank you. There I was thinking alter schema would be for changing properties of the schema.
I see the reason for the change, and for me it is helpful. Just...
June 28, 2006 at 2:28 am
Could you not use two stored procudures instead of that loop and case statment?
E.g.
CREATE PROCEDURE dbo.usp_InsertAnswer
@SurveyID int,
@QuestionNumber int,
@AnswerText text
AS
IF @AnswerText = '' OR @AnswerText IS NULL RETURN
INSERT INTO #Answers_table...
June 12, 2006 at 6:04 am
Viewing 9 posts - 91 through 99 (of 99 total)