Re: How to GRANT *all* permissions to *all* users?

I understand you were in a bind and probably didn't mean much by the
following comment, but it disturbs me nevertheless (because I hear it all
the time, which causes problems).

"don't worry, it's just a test environment, not the real thing"

Be careful of this. Whatever security context you code to will be the
security context you will require in production. This is not to say that
you couldn't lock it down after the fact. But, it has been my experience
that locking down a system creates more "issues" than coding to a secured
system to begin with.

The problem is that if you have "God Rights" when you are developing, there
is nothing that forces you to look for alternative solutions. Then when it
comes down to rolling out to production, you do not have "time" to find that
appropriate, secured solution.

In a secured environment, you end up beating your head during the
development process instead of the deployment period, which is where you
should be searching for solutions to begin with.

So, for your personal installation, on your desktop let's say, be a god,
that is how you learn. However, on the shared development/test system, I
would recommend that you secure it just like production. Security, by the
way, is a vector that you need to test as well during the development cycle.

Sorry, but that is my soapbox for today...ok, well, for the last minute
anyway.

Good luck.

Sincerely,


Anthony Thomas


--

<steve.chambers@xxxxxxxxx> wrote in message
news:1170773941.309642.45560@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
In short, I would like to know how to do this i.e. give any user
permission to do anything (e.g. CREATE tables, ALTER tables etc.)

I'm asking because I recently converted from SQL Server 2000 to 2005
and initially the stored procedures couldn't be changed so had a quick
look on the web and found that applying the following 2 lines enabled
most things:

GRANT VIEW ANY DEFINITION TO public
GRANT VIEW SERVER STATE TO public

(http://www.microsoft.com/technet/technetmag/issues/2006/01/
ProtectMetaData/default.aspx)

But I still can't ALTER tables (this option is greyed out). I want to
give anyone working on the databases the ability to do anything (don't
worry, it's just a test environment, not the real thing).

Is there a GRANT or set of GRANT commands that I can apply to give
these permissions?

Thanks to anyone who can help/shed any light on this...

Cheers,
Steve



.

Relevant Pages

  • Re: Linux for Kids
    ... Well, it is not exactly a production server, but I do run my personal ... It's more secure and stable that way. ... > there's no chance of squeaking past the firewall on the same machine. ...
    (comp.os.linux)
  • Re: Auditing Firewalls
    ... Our firewalls are in production, am I supposed to test them from different subnets? ... Need to secure your web apps NOW? ... Best regards. ...
    (Pen-Test)
  • Re: Saving the children from gay penguins
    ... Sure, I'll grant you that. ... Within limits, of course. ... California had a ... production of children, I would be in favor of strongly restricting ...
    (rec.motorcycles)
  • RE: webmail application for production?
    ... I am sure that squirrelmail can be secure ... Not knocking squirrelmail because it is a great ... > Subject: webmail application for production? ... > Which webmail application would be most secure for the ...
    (RedHat)
  • Re: webmail application for production?
    ... > I don't want to take any security risk here, so i really need a secure ... I currently use both Squirrelmail and Horde/IMP in production. ...
    (RedHat)
Loading