Have you converted the string to a date in your script before putting it in the database field?

1)Input data as a string

2)Create new output column "LastUpdateDateOut" as an output datatype...

Learning TSQL is imperative.  You can't do everything through a GUI, nor would you want to.

MICROSOFT RESPONSE FROM MSDN

This is certainly a bug with handling (or parsing) a certain trigger that you have at your publisher. You may be able to work around this by adding the...

Make sure the database is disabled for replication.

navigate to:

configure publishing, subscribers, distribution

select the "publication databases" tab

"uncheck" the database you want to disable

Are you running this in the published/formerly database?  You should get something like this.  These are only related to replication.

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

drop table conflict_EFile_Merge_EfilePayment

drop table conflict_EFile_Merge_DocumentActivity

drop table conflict_EFile_Merge_WIPXML

drop table conflict_EFile_Merge_MQQueue

drop...

On the subscriber run

      sp_removedbreplication [ @dbname = ] 'dbname'

verify that this worked by running these queries:

Select...

You can connect, you just can't run any queries.  Pretty useless.

DNS Server problems.  From time to time we get the same error.  This is a fun one for your network guys to try and troubleshoot because it doesn't consistently happen.

Here goes nothing!

I would defer to this definition, in addition to being in the DRI camp:

"The quality or condition of being whole or undivided; completeness."

Therefore child/sibling records MUST have...

If we adopt Steve Jones "DBA CODE OF ETHICS", or not it boils down to this question. 

WHO IS RESPONSIBLE FOR THE INTEGRITY OF THE DATA?

If it falls to the...

1. Set up a job to run every xx amount of time to check and see if the merge agent job is running.  If it's not, then send the email...

"Another ooption for turning off the triggers is to use the settings for each article in the replication property pages"

This option is for what schema to generate/apply for replication. ...

Yes, the triggers have the same "not for replication" option.  Just alter your trigger:

FOR  INSERT, UPDATE NOT FOR REPLICATION

Check your ForeignKeys.  There is a "not for replication" option which will prevent this error from occuring. 

Replication does batch inserts, so Parent-Child order doesn't always occur.

Merge Replication

When creating the FOREIGN KEYS, you need to set the "not for replication option".  Merge Replication transports the data in batches, so not all of the data arrives at...