This is the worst way to do it. Why would you choose to do it this way, when you already had two better ways to do it?

You would have to reorder the script so that it creates the objects in the right order.

Sounds like either triggers or encryption.

This is really just a warning. It created the object, but it could not add the dependency records. It OK, everything should still work anyway.

Heh. "Michigan Pork Chops. They're Mmm, mmm, thwapp!" :D:D:D

Jeff Moden (1/14/2009)

---

Actually... I built a "cannon" to fire the potato part of the pork chop dinner. 5 foot barrel with a 5 foot extension (haven't tried the extension,...

Jeff Moden (1/14/2009)

---

Like Gail pointed out to this rubber, this isn't the first time he's been a real jerk about receiving free help... why do you guys to continue to...

You need to check the Initiator's response queue (it's the "other" service that you have to specifiy in the Begin Dialog statement) for error messages from Service Broker.

Also check my...

Thanks, Grant

Actually, I thought that you were very restrained, Grant.

This guy...

Here's a good article on SQL Injection by one of my favorite authors, Michael Coles: http://www.sqlservercentral.com/articles/Security/updatedsqlinjection/2065/

OK, glad I could help.

Ahh, sorry, I missed that.

Getting the column names is easy, no dynamic SQL required:

Select *

From INFORMATION_SCHEMA.COLUMNS

Where TABLE_NAME = 'YourTable'

But if you want to use the column names dynamically in an INSERT statement,...

Hmm, isn't UserName sufficient to correlate it back to the source? You could include that in the OUTPUT clause.