Hi all

The issue looks to be because we use custom security.
Assuming the user does not have access tot he report, we use :-
THROW 51000, 'You do not...

Hi all

Thought I'd resurrect this thread as I'm still struggling with this.
We are using:-
SQL Server 2016
Microsoft SQL Server Reporting Services Version 13.0.5201.2

I've been...

We did have that issue, but we got round it by setting the delimiter to quotes in one of the settings (can't remember which one without checking).

It's working...

We do something similar with one of our imports.
We have to import 160 (or so) files into separate tables.

We set it up so that we build the...

That sounds perfect.
I've looked at the procedure I need users to run and it's currently listed as Execute As Caller.
I can't see an owner for it in the...

Hi Sue

Thanks for that, it's a handy bit of code.
I've just run it and got the following:-
name    permission_name    state_desc    class_desc
RDGH\z1    ALTER ANY LINKED SERVER    GRANT    SERVER
RDGH\z1    CONNECT SQL    GRANT    SERVER

Apologies for...

Thanks Sue

I've just run SELECT has_perms_by_name(null, null, 'alter any linked server') for the relevant user and it's coming back as a zero (which I'm assuming means no permissions).

Hi all

I'm making progress (I think).
I've now got a domain-level user I can use for testing purposes (it's got no privileges on the file-system so I've sorted...

This is a generic procedures where users can specify quite a lot of the parameters for the destination folder, the server, filename and table/view to be exported.
We can't use...

The plot thickens.....

This is what I've done so far (my dodgy notes):-
Login TestUser (created as SQL-only login with password)

Current permissions:-
Server roles - public
msdb...

Thanks for that.
I'm currently looking at alternatives to the full-on "DBO" role if I can figure out just the permissions someone will need to be able to do their...

Never thought of that bit.
I might have to remove DBO permissions from all our current users if I can figure out the correct set of permissions to give instead.

@desnorton - We did think about that but it would be even more work to move the tables, stored procedures and rewrite the stored procedures in both databases.