SQL 2012 SSISDB catalog - read permission on folder, but still can't see it
Hello, I've set up the SSISDB catalog, created a folder X, granted all the permissions to a specific login (windows group) - read, modify etc. Didn't make it a member of the ssis_admin role though (I want that login to have full control just for that folder). The problem is, members of that windows group can't even see folder X in SSMS or via catalog.folders view. Any ideas? Thanks.
June 15th, 2012 6:04pm

You should Create the user in SSISDB database, and then add that user in permission list of folder, take a look at images below http://www.rad.pasfu.com
Free Windows Admin Tool Kit Click here and download it now
June 15th, 2012 8:06pm

That login is already a user in SSISDB database and has read (and others) permission on the folder. OK, I tried this scenario: Gave the user db_owner and ssis_admin roles in SSISDB database.Connected to the server with that user, gave "myself" (that is, the user I was connected with) all the permissions on the folder inside SSISDB catalog.Removed "myself" from ssis_admin role in SSISDB database.Refreshed the SSISDB catalog note in SSMS. And behold, can't see the folder anymore... Two things to consider (don't know if they matter...): The login is a Windows group.Grantor for permissions on folder in my case is "public", not "dbo". Why? And does it matter? (I granted those permissions using a db_owner user, as described above).
June 16th, 2012 3:35pm

Anyone?
Free Windows Admin Tool Kit Click here and download it now
June 20th, 2012 9:52am

I have a similar situation where I can grant access by user not by a group. I think your first item under "Two things to consider..." could be the issue. Unfortunately, I don't know how to fix it.
July 12th, 2012 2:39pm

I'm stumped by this problem. How about that "guaranteed 2 business day response" for MSDN subscribers? It's only been 3 months now... I don't know if I'm doing something wrong, or this is actually a bug. So, let me repeat: My goal with SSISDB catalog's folder permissions is to limit users to only a certain folder, but inside that folder they're essentially admins. I don't want them to have any permissions whatsoever on other folders. Seems easily doable via folder permissions, right? Try these steps: Let's say we have folder X in SSISDB catalog.User is a member of a Windows group that has all permissions for X (read, modify...).PROBLEM: User can't see folder X in SSMS's object explorer unless his group is also a member of ssis_admin role on SSISDB database. So, either he's admin for all folders or he can't see any folders. Hope that is sufficient info to reproduce the problem. PS: I did find a similar connect issue, but it got flagged as a duplicate of an issue that (seems to me) is not really the above situation. Thanks.
Free Windows Admin Tool Kit Click here and download it now
September 15th, 2012 11:05pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics