Hi, I've been working on a program to allow a non-privileged user to start jobs (s)he doesn't own.

With the correct setup, querying the tables in MSDB is possible. I set...

Gail,

Many (somewhat belated) thanks for your response.

Unfortunately I won't convince anyone where I work on recoverability grounds.

We are in the extremely luxurious position of being able to take an extended...

I thought I'd post a follow-up.

It turned out the replication in question was set up as a snapshot replication. I think a predecessor had tried to set up transactional replication,...

Here are the instructions I put together for the unpublish and republish of the databases. I'd be grateful for any comments.

Have I missed anything? For example: do I need to...

Thanks again.

I'll try deleting and redefining the replication.

Thank you both for your responses.

I'm still trying to understand what's going on (or not, as the case might be).

I don't see a log reader job - which is why...

Did you try it?

When I used it on your example above it did indeed stop everything in its tracks

- but didn't even print @@error.

Serqiy's comment about the dangers of letting someone...

Serqiy's comment set me thinking. Why are you letting someone else send you a SQL string instead of a list of values?

Can you not accept a string like the following...

Wise words indeed. A little validation may be desireable.

Apologies, now I understand. I thought you were building the strings.

You could separate the commands. Look at http://www.simple-talk.com/sql/t-sql-programming/the-helper-table-workbench/ for some clever ways of separating a string and putting the...

At the risk of repeating myself

"Execute only returns status information for the last command presented to it. You need to execute each insert statement separately, testing @@error after each."

Try

June 1, 2007 at 2:27 am