When wrapping the whole thing in a transaction, it works and the CATCH block is reached!

BEGIN TRAN

BEGIN TRY

EXEC LINKSERV.DBNAME.dbo.sprocName

END TRY

BEGIN...

Thank you GSquared, this was very informative.

GSquared (3/14/2008)

---

I would tend to think that the problem is that it's running the called proc on SQL 2000, which doesn't have Try/Catch. But that's just a guess based...

I did the exact same test on the sql 2000 instance - the linked-server instance - and got the same output:

Msg 50000, Level 11, State 2, Procedure test_TRY_CATCH, Line 17

ERROR:...

Matt Miller (3/14/2008)

---

I can't help but think that somehow it's happening in a different context, or that somehow it's raising an error on the "wrong server". There are a...

Come on guys, no takers on this? :w00t:

Todd Engen (2/9/2008)

---

The BOL topic Getting Started with CLR Integration is a good place to begin. That will take you through editing, compiling and deploying a CLR stored procedure.

As...

Steve,

Sorry, I'm missing the point, can you elaborate? What are...

I have worked both with ORACLE and with SQL Server, and I must say, my user experience with ORACLE has been abysmal. I have no beef with the database engine...

demmets (2/28/2008)

---

Hi,

I am a DBA new to CLR and I have a developer who would like to start using CLR. I have started to research CLR but I have...

Sugesh Kumar (2/28/2008)

---

No don't create it in the model database as this acts as a template for user DBs to be created and your procedure will be created in all...

If you are referring to SQL mail - not database mail - then just run xp_startmail.

If SQL mail is working it will simply give you a warning that mail...

While SQL Profiler and Perfmon are and will always be valuable tools, a SQL Server 2005 instance already stores a huge amount of information on its operational details in memory...

SQL ORACLE (2/26/2008)

---

Here is the scenario.

A user is a database owner, but has no access at all to master database. Now, the user would like to execute one stored procedure...

I've had the same error message using Reporting Services:

see Post #449612 (the 2nd post),

http://www.sqlservercentral.com/Forums/Topic449604-147-1.aspx

I haven't been able to resolve this issue yet.