I've never actually done a thorough test to see what all initializing the subscription does. One thing it does is goof up managed identities! So if you are using them...

Create a stored proc that just does an INSERT VALUES statement against the table. Then debug the stored proc in QA. As you step into the SP it will in...

How about something like this...

CREATE PROCEDURE dbo.procAddContactAddress

(

@Contact int,

@Address int,

@ContactAddressPK int = NULL OUTPUT,

@RetCode int=NULL OUTPUT

)

AS

SELECT @ContableAddressPK = tblContactAddressPK

FROM dbo.tblContactAddress

WHERE tblContactFK = @Contact AND tblAddressFK = @Address

IF @ContactAddressPK IS NULL

BEGIN

INSERT INTO...

This is not a trivial thing. If you modify the publication you will likely end up having to re-initalize all your subscriptions. So before setting up this scenario TEST TEST...

Using one sproc to go against 10 different tables means that you would need to use dynamic sql rather than staight sql. This means that the caching of the query...

No it's not possible to do a table as an output parameter. My question is why would you want to? Either use a UDF or simply use a temp table...

The only way I can think of to do this would be to use dynamic sql inside your sp. Even though the user specifies different databases couldn't you still have...

Ahh, but if I remove the articles from the subscription then I have to re-initialize all the subscribers. Due to the way our database is set up that is something...

guardata,

That is a very good work around! I may just have to do that. The previous DBA replicated all my Sprocs with merge replication so I can't actually drop and...

I'm like Steve, most of my scripts do a drop/create with permissions tacked on at the end.

Did you read this KB article?

http://support.microsoft.com/default.aspx?scid=kb;en-us;280106

You could throw something like this in your script and then drop it at the end....

DECLARE @LinkedServerName     sysname

    , @provstr                nvarchar(4000)

    , @ServerName             sysname

-------------------------------------------------------------------------------

-- Change the following to the remote...

Have you tried creating a linked server instead of using the openrowset? It may handle this situation a little differently. I don't currently have a machine to test this with....

Don't I wish! More like 6 days a week!

If you are running WIN2003 then try checking the following.

Open Component Services, Drill down to "My Computer" and right click it. Open the Properties box and click on the MSDTC...