Post reply

Cross Database Query Prevention

  • June 26, 2012 at 4:03 am

    #262774

    Hi Guys

    I have a bit of an odd problem. I have set up snapshot replication to copy a reporting database up to a server. When the agent job executes it fires a stored procedure that adds all objects that are not currently replicated to be published.

    My problem is that when I gave this to our report writers to test, they broke it immediately by writing a view that references a database that is not on the destination server.

    Is there a way of preventing a report writer from accessing certain DB's(or only allowing access to) from within another DB?

    The problem is they still need access to all the other DB's for other work.

    Or maybe there may be something in the replication process that could help?

    Thanks in advance

  • June 26, 2012 at 8:13 am

    #1505595

    Issuing separate logins for separate responsibilities to the report writers would allow you to cordon off certain DBs for certain logins they are issued.

    Or you could tell them to stop breaking things 🙂

    There are no special teachers of virtue, because virtue is taught by the whole community.
    --Plato

  • June 26, 2012 at 8:43 am

    #1505618

    Thanks for the reply...

    That's an option that we may take if I can't find an alternative that allows windows authentication...

    Thanks

Viewing 3 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply