This is still helpful in 2019.

I experienced the same error messages. It was determined to be a vulnerability scanner at work.

This blog entry may be helpful:

http://sqlstack.wordpress.com/2011/01/31/repercussions-of-non-trusted-foreign-keys-sql-server-2008-r2/

Suggest to your developers that they load in batches. This will help to keep your log file to a more reasonable size.

Regards.

I ended up creating a view of the Oracle table using the TO_CHAR function on the problem columns that were defined as VARCHAR2. I then just use a linked...

Did you ever resolve this issue with the linked server to Oracle?

opc.three. Would you be so kind as to implement your statement, ' In SQL 2012 we have the ability to define a default schema for a Database User based...

You may find this link helpful.

[/url]