Ok, so the example wasn't quite correct then? (no variables in there)

Must confess that I lost the thread a bit here.. Can you...

I see the commit and rollback, but where is the BEGIN....?

/Kenneth

Well, this looks very much like the two databases have different collations, therefore the server can't tell how to compare old.id against new.id.

The COLLATE syntax posted earlier will 'fix' it,...

Again, if you use dynamic SQL, you must grant permissions on the base tables. It is not enough with permissions on just the view or procedure. In effect, the view...

Can you post an example of your 'copy-code'?

ie what does the complete SQL statement look like?

Also, the complete actual error message might be informative as well.

/Kenneth

Check the two databases collation settings (in EM right click db icon => properties) is one way to check. It may also be that certain columns in your copied tables...

>>Now the SpecialCharacters table could be modified to have a type search where not all of the s/r would be done at the same time (if need be).

That is one...

The thread with Remi's 'magic' function is called "stripping out quotes"

A possible drawback with the solution may be that it relies on a...

sysprocesses is a good place to do 'ligthweight' tracking (do it myself in a similar way to gather usage stats in a simple quick & dirty fashion)

However, it's only good for taking...

How do you execute the bulk insert?

When I try it, I get this very clear errormessage:

Server: Msg 4860, Level 16, State 1, Line 1

Could not bulk insert. File 'c:\sdfjasdjflasjf.txt' does not...

Here's another way - it will also list names of db's not having the proc in question so you can see if some db's may have been missed..

Have you checked if your situation fulfills everything that the kb speaks about? If you suspect that it may be that bug, seems like the only way to verify that...

Let me just start off by saying that I haven't done this myself, so I can't offer any hard real-life advices, just some thoughts on the subject...

Nope, not there and not anywhere else either. SQL Server does not maintain that kind of information.

If you absolutely need such info, I'm afraid you must gather it yourself with...

I'd actually recommend against using 'auto_fix' - ever..

Use the 'REPORT' option instead, and after eventual results, use 'UPDATE_ONE' for each login you need...