from a string representing a query, it's difficult, just as Grant said; you have to tokenize it in a SQL parser. It's quite a bit of work, i did it...

It's really, really easy to script out a backup and restore,and with just a bit of tweaking and testing, make it fully automated.

For example, I have a job that restores...

i use something like this to generate models of both an insert and an update statement, assuming a staging table of the same name;

does this get you started?

you would...

duplicate post.

original discussion is here, lets keep it all together to prevent fragmentation of replies:

http://www.sqlservercentral.com/Forums/Topic1779526-338-1.aspx

the real question is what is your budget;

the top tools cost money, typically ~1000 per server, with discounts against more and more servers.

is your job going to shell out 100K...

backup and restore would be my first choice too, unless you can come up with a decent reason to avoid it.

if you are really going to script it out,

there's...

something like this should get you started;

select

e.name

...

i believe locking on insert will depend on the PK of your table, and clustered indexes, if any., and how many rows you are inserting.

if you have an identity column...

you should still check what i mentioned.

last run status can still be seen in Job Activity Monitor with a big red X, but the history could be erased.

multi row inserts will insert the same default value form RAND() for all rows in the insert statement.

is that ok? (oops! tip of the hat to Jacob, who noticed the...

check to see how long your history retention is; it could easily have been written, but aged out by the time you look at it.

if it is still a the...

it's been a while on this thread, but i had this occurred to me twice since i last followed up on this;

here's some notes i took about the service broker...

I'm guessing it has something to do with collation.

can you run these commands, and report what the values are?

with that, i could replicate the issue, ib et:

select databasepropertyex(db_name(),'collation')

select databasepropertyex('master','collation')

bgrossnickle are you using the original code fromt eh article, or the updated code from the discussions here?

over the years, we've made a lot of improvements; your example table...

you can also do a shift + Right Click on the item to get a Run As Different User context,w here you can put in the other domain credentials.