No need to change that setting for the moment.

Did you restart SQL Server after exec sp_configure 'remote access', 1?

If not, do it and it will probably fix the issue.

EXEC master.dbo.sp_MSset_oledb_prop

Check the allow_in_process column. It is 1 for in process, 0 for out of process.

Is there anything else...

Process explorer can help you identifying who is locking the files.

Probably it's SQL Server (sqlservr.exe).

Which server product is the linked server? SQL server?

How is the provider loaded? In process or out of process?

You're welcome.

Glad I could help.

OK, I think I got it.

Sorry for my thick head.

ALTER PROCEDURE [dbo].[sproc_GetPostsByThread](@threadID nvarchar(max))

AS

BEGIN

SET NOCOUNT ON

-- interfering with SELECT statements.

...

Vague question. Language issue I suppose.

I'm sorry, I guess all you can get is a vague answer:

CREATE TABLE #tempTable (

id int NOT NULL identity(1,1),

...

These should get you started:

http://msdn.microsoft.com/en-us/library/ms345108(v=sql.90).aspx

http://www.mssqltips.com/sqlservertip/1836/sql-server-service-broker-example-on-how-to-configure-send-and-receive-messages/

Sorry, try this:

EXECUTE('EXEC database.schema.procedurename') AT linkedservername

I'm sorry, but I'm getting lost. Too much confusion.

Let's start from scratch.

This is your table:

IF OBJECT_ID('TempDB..#mytable','U') IS NOT NULL

DROP TABLE #mytable

CREATE...

Did you try:

EXECUTE database.schema.procedurename AT linkedservername

Doe this work?

This is the results I get.

Level Sequence ...

Then, it's the session that runs the KILL statement, your current session in SSMS.

Issue a "USE master" command and you should be fine.

Nope, I already have done that.

Please, copy your code, paste it in a query window in tempdb and execute it. You will see no output for parameter '3'.

Trigger is on the view in order to allow direct inserts to the table by the service broker procedure.

Stored Procedures calls can work in parallel on the log table, because...