I'm a part-time accidental SQL Server 2005 DBA whose full-time job is developing business intelligence solutions, but where the BI intersects with the database, it falls in my 'stack'.
We have a number of scheduled reports that failed when another developer needed to add
SET TRANSACTION ISOLATION LEVEL READ UNCOMMITTED in several stored procedures running against an enterprise application database.
It turns out that the login used by the reporting tool didn't have the correct permissions. It could execute the stored procedures, but not with the
SET TRANSACTION ISOLATION LEVEL added.
I was able to get around it temporarily by adding the
db_owner role to the login properties for the database. It already had
public. But it seems like I should be able to grant a permission that would alleviate the problem without giving the login the
I've read through all the information on
GRANT in the SQL Server books online, but can't find what permission to grant.
Can anyone help me out? If you know of a resource, I'd love to know about it.