As I said, we've had to take the stance that we're not going to spend more time on it. This was the latest MS response (they think the problem may...

It is a member of other groups with server logins, but none of these are linked to users in the database. The permissions, etc. currently in the database are a...

Just in case someone else stumbles on this thread, I thought I ought to update it. The problem has been escalated through several layers of Microsoft support to no avail....

It also depends on the industry your company is in. Some, such as finance, require a clear separation of duties between those who develop software and those who release it...

You should be able to do what you are trying to do; I've done this myself before. Having created the local temp table in one stored procedure, it will be...

If they're allowed to specify the "from <table> join <some other table>" part, then it's not just the lack of a WHERE clause that you need to worry about. I...

Anyone else feeling a bit sorry for OP? He's just starting out, asks a question and ends up in the middle of an esoteric sh1t-storm!

You don't have #table or @table in your original post so it clearly isn't the whole procedure. Please post the full definition of the stored procedure and the definition of...

Ignore - should have re-read the question!

My guess (based on bitter experience); it is an audit table populated by an AFTER UPDATE trigger and something is updating the source table without a WHERE clause.

Could it have been a before/after test for the addition of a primary key or unique index? It would fail if the table has either.

If your update is not parameterised, the problem could be due to occasional single quote characters in the input, eg.

Update MyTable set Surname = 'O' Connor'

The update statement would terminate...

Why are duplicate companies a problem? I would expect at least a few cases where you have more than one contact at a particular company.

My guess is that they're using some tool to import data. Many of these tools offer the option to disable triggers during import and it's often the default setting.

Chris

If you decide to go ahead with the change, my recommendation would be to build empty databases with the new collation and copy the data across with a tool such...