And then as best practise when that dev creates their object they should specify dbo so that their user doesn't become the object owner?

Are they failing? Or just not even trying to run?

To be honest our project outlook means no 2005 migration until last quarter of this year but when we do I'll try and update this!

What reason would you need to "break" replication during the day? Just trying to figure your circumstances.

Intialising a subscription involves a line of code to add the subscriber (can be...

Crazy fool. I talked myself into not being able to use "On Completion" for the deletion steps....but it clearly works.

Thanks anyway, but if anyone has tips on scripting around events...

How much data do your 40 published tables take up? Surely you'd be better off syncing them by BCP'ing out those 40 tables. Transferring them over to the subscriber and...

Network share.

ODBC Driver for the app.

Can they see the server? (ping)

And so forth.

No I can't use completion as some of these steps rely on the others being successful to continue. I just need If Successful --- Go ahead. If failed ---- head...

Interestingly I now have a server displaying alternative behaviour, and giving the same error when passed a date in the so called universal yyyymmdd format.

Everything is set for British UK....

Found it! I had changed the Default Language, but the SQL Service was still running as US English. Switched this, date works...sorted! SILLY!

Thanks all for your help.

Lynn...that worked! Didn't really know about setting the dateformat on the fly until recently. Makes sense that it would fix the issue. Does this then mean that the setting is...

Can anyone expand on this a little? It's most annoying. The developers aren't using yyyymmdd so I have to try and work out why the current environment is displaying this...

Maybe you could expand on that a little to apply DTC to my case?

Thanks for your help

Now I've noticed even when we search this smalldatetime field using "17/04/2008" it returns "The conversion of char data type to smalldatetime data type resulted in an out-of-range smalldatetime value."

If...

Well for years and years and years they have used ddmmyyyy so changing it now would mean a complete rewrite of thousands of stored procs.

I need to work out...