ken.trock (5/3/2012)

---

I'm with CrankyRat on this one. Maybe not the Glenn Beck part 🙂 In the last 10-12 years here in the USA we've seen internet bubbles, mortgage meltdowns, and...

RobertYoung (5/3/2012)

---

If you've ever been in sales/marketing, or know well someone who is, then you know their mantra: "any moron can sell a good product, they're just order takers,...

Please post both execution plans. You can upload the sqlplan files using the Attachments options for posts.

drew.allen (5/3/2012)

---

If it's so...

By the looks of this, I'm going to hazard a guess that parameter sniffing is the issue here. You'll want to Bing/Google/whatever "parameter sniffing" in order to get more...

Aha!

Yeah, it's usually some silly little thing like that.

The usual way is have your network people set up an encrypted VPN tunnel between the two servers, and use that for the connection.

They aren't.

On the subject of speeding up the trigger:

Can you provide scripts to create the tables it affects (Blanco_B2, Branches, Kostenplaatsdrager, Locaties)? If so, I can test this. Also,...

On the original question about firing a trigger once for multiple updates: Yes.

In SQL Server, a trigger only fires one time for any given Update/Insert/Delete statement, no matter how...

Have you looked at the execution plans and compared them?

drew.allen (5/3/2012)

---

How do you know who wrote it? I don't...

The correct response in an interview, if you don't know the answer to a question, is "I don't know. I'd have to research that. Should be easy enough...

I've been using XML in various database-related solutions for several years. Started with SQL 2005, really.

The main problem I've run into with it has been very, very poor documentation....

Are you going from the table to a flat file?

If so, then it's less likely to be truncation and more likely to be an incompatible file format. Are you...