I just re-read it and I think you're right. *I'm* working with 2 way synchronization between a mobile device/server so I think I jumped to that conclusion a bit...

This is true. It will depend on your actual situation as to which is the more efficient method. It might be that copying a few extra rows that...

If you don't need to know the time the record changed, you just need to know *that* it changed, a timestamp column will serve the same purpose without the trigger.

If you decide to go the Dynamic SQL Route (which is the easiest to implement from where you are now), make sure you keep injection in mind and code accordingly.

Check out the COLLATE keyword in BOL.

Also, you don't have any criteria linking these tables, so you're performaing a multi server cross join. Sounds dangerous.

Looks like a permissions issue to me. Is the directory/user/etc you used when the script executed successfully the same as the ones you used when it failed?

This script will allow you to add a user to all the stored procedures that you choose at once:

USE YourDatabase

DECLARE @Namevarchar(150),

@sqlvarchar(500)

DECLARE Perm_Cursor CURSOR FOR

SELECT [Name]

FROM sysobjects

WHERE xtype ='P' AND...

I'm curious as to how you pulled up a 17 month old post. Doing a little housecleaning on the subscriptions?

Did you ever figure this one out George?

Thousands... but not more than 2500 depending on versions and OS. (See my post above)

In my standard comment headers I tend to add a specific phrase (like 'Not yet Optimized' or 'Needs Rewrite') when I'm not happy with how something works, or the method...

Awesome idea. I actually have LinqPad already, but I never considered using it for that. I mostly used it to try...

I didn't even mention that the Object Explorer Details tab has another bug with multiple monitors where it puts your right click menu on your primary screen regardless of which...

:crying:

This is one of the old ways of doing things:

DECLARE @Errorint

--YourCode

SET @Error = @@ERROR

IF @Error = 0

BEGIN

--Success Code

END

ELSE

BEGIN

--Fail Code

END

It is very important that you set @Error after every single statement...