I have seen errors like this when I knew there shouldn't be a problem with connectivity. My advice to you is to try executing the task that is failing...

You can use the ALTER TABLE command to disable and enable triggers. Also you can use sp_trigger created by Rodrigo G. Acosta. Its in the SQLServerCentral scripts area...

I like your article. I am constantly trying to learn more VBScript to use in DTS packages.

I ran it in our dev environment after copying some of our most...

I often created my queries and tested them before turning them into stored procedures. I still do this on occassion, however if I know this will be a stored...

I'm glad to know I am not the only one who does development the way I explained in my article.

David.Poole, you have a good point. I failed to mention...

We found a solution that worked for us. We read many posts on other sites and finally found one that told us the attachments could not be sent out...

I have always used the RETURN code to return a number that indicates a status, it doesn't always indicate an error per say but a status of execution.

One example is...

By reading a recent post I learned that there is a time when the RETURN command does not halt the execution of a stored procedure. That is when you...

Forgive me for answering my own question, but I just found the answer and will post it here in case someone else runs into the same problem.

There was an SP...

Good article. I have a question. You gave the SQL to set the sa password. Can you run this while a server only allows NT accounts to...

For those who don't know me. I am Robert Marda. My official job title is SQL Programmer. My tasks at work include many administration tasks on our...

sunjiulu:

When I execute spStaticNoStopOnFirstError in the pubs database on SQL Server 2000. Both statements in the SP execute even though the first query fails because of a constraint on...

As for the non existant table, that was simply the first SP I came across that would stop on encountering the error and so I used it to illustrate a...

I ran the following in Query Analyzer:

CREATE PROCEDURE spTest1

AS

SELECT * FROM NoTable

RETURN 1

GO

DECLARE @v-2 int

exec @v-2 = spTest1

PRINT @v-2

And I got the following error:

Server: Msg 208, Level 16, State 1,...

I am not familiar with alerts. But I do have a notification system for our DTS packages.

I simply schedule each package and then go to the job that executes...