Viewing 15 posts - 8,176 through 8,190 (of 9,720 total)
WHOOHOO!
Found the workaround.
Create a new database called ReportDesign. Give the report writers whatever perms they need on that database.
Give db_datareader and db_denydatawriter on the "source" databases (from which the...
December 8, 2009 at 5:56 am
That link just shows another question. It doesn't actually show what you did for a final solution.
But if you post the final solution in either thread, then reference that solution...
December 8, 2009 at 4:43 am
Julie Breutzmann (12/4/2009)
December 7, 2009 at 5:00 am
Oh, yeah. Steve's line gives me an idea for a whole 'nother story. @=)
December 7, 2009 at 4:54 am
Gift Peddie (12/3/2009)
Your concept of report is what end user tools do not what developers write.
Gift, I'm sorry. I don't understand that sentence at all. Could you rephrase? Because the...
December 4, 2009 at 4:10 am
Gift Peddie (12/3/2009)[hrIf a DBA stops intermediate inserts which are needed in most complex reports the DBA will write the code to create that report because there are reasons why...
December 3, 2009 at 10:27 am
So it's not that Execute perms don't work, but that by the rules you can't use them?
December 3, 2009 at 10:23 am
Could you post some sample code for the resolution so that people who need this in the future can better understand your solution?
December 3, 2009 at 8:58 am
In my experience, the Compliance team (or whatever name the watchdogs have) are not tech people. If a DBA wanted to get away with something, it would be easy to...
December 3, 2009 at 8:51 am
laurav (12/3/2009)
December 3, 2009 at 6:23 am
Grant Fritchey (12/3/2009)
Excellent editorial. The link seems to be missing to the T-Mobile story in the UK. Any chance of posting it?
Sorry about that. This is the same link Steve...
December 3, 2009 at 6:08 am
Seth,
Hate to break the news to you, but if they haven't already figured that trick out, they're either new to being T-SQL writer or they're not a very good one.
That's...
December 2, 2009 at 11:38 am
Actually, we don't allow anybody to write procs in production. We have a Dev environment, Test environment and QC environment to go through before things reach Production. Unfortunately, we're all...
December 2, 2009 at 9:25 am
GSquared (12/2/2009)
December 2, 2009 at 8:34 am
Nope. That did NOT work. I even did a DENY INSERT on schema dbo and had the user's default schema as MySchema and had the proc saved in the schema...
December 2, 2009 at 8:29 am
Viewing 15 posts - 8,176 through 8,190 (of 9,720 total)