You may want to read this blog post by Kimberly Tripp. Her blog is one of the ones that I would recommend to anyone who works with sql server.

Since you posted in a 2005 forum I am assuming you are using SQL Server 2005. In SQL Server 2005 you should be using sp_send_dbmail instead of xp_sendmail. ...

You might want to start here.

Here is a search link that may have some results that help.

Here is the first link from that search that may help.

Just to be safe you should read this thread where it is pointed out that IsNumeric can return true in some odd cases like "+" and currency symbols.

I would recommend against doing the cross-server update in a trigger because triggers fire within the scope of the initial transaction so a failed trigger operation rolls back the entire...

What this means is that the job, when scheduled, is running at the same time as another process that is locking the same resources, typically in opposite order, and cannot...

Jeff Moden (3/15/2009)

Heh......

Barry,

Just making sure you noticed, but Goldie said that the CLR is not an option in this case. I had suggested it originally as well.

Jon,

You did not put the connection string in the web.config file correctly. Just copy and paste what i posted and then change what needs to be changed.

Jon,

You actually do not have a connection string created in the web.config. You need to replace this:

<connectionStrings/>

With

<connectionStrings>

<connectionString name="LocalDB" value="Data Source=servername\instancename;Initial Catalog=DataBase;User Id=myUsername;Password=myPassword;

<connectionStrings/>

You can go...

Since it doesn't appear that you will be giving away any sensitive information, why don't you make a copy of the web.config file, rename it to web.txt and attach it...

SQL Server uses memory to allocate locks and if that memory space is full then more locks cannot be taken until space is freed.

Check out this article.

Have you looked at the details of the job execution in the job history?

Have you run the code in that job step in Query Analyzer to see what the error...

Sounds like it should work. Try this instead of using the GUI:

GRANT EXECUTE ON OBJECT::schema.procedurename TO username

Then try the specific stored procedure. You could also try logging into...