Posted by chris on 01/29/08 16:26

Alter Table did it.

Create Assembly
and
Create Trigger

Scripts run on the server itself turns out to be the preferred option.
I was just trying to save myself a walk over to the Test_Server, by
deploying directly from Visual Studio.






On Jan 28, 5:44 pm, Erland Sommarskog <esq...@sommarskog.se> wrote:
> chris (chris.cudm...@gmail.com) writes:
> > First attempt:
> > You do not have CREATE Trigger permission.
> > Solution - Walk over to Test_Server, open management studio and give
> > myself CREATE Trigger permission.
>
> > Second Attempt:
> > "Cannot create the trigger 'MyTrigger', because you do not have
> > permission."
> > What it doesn't tell me is what permission is missing.
>
> > I could run this as admin, but I'm going to need to deploy it on
> > Production_Server eventually, so I want to request the minimal
> > permission set possible. (And I won't get admin on Production)
>
> The minimal set would be the permissions CREATE ASSEMBLY, CREATE TRIGGER
> and ALTER on the table in question.
>
> In practice, being member of the database role db_ddladmin, may be an
> easier path.
>
> For the deployment on the production server, I recommend that you build
> a T-SQL script to do it all. Keep in mind that you can specify an
> assembly as a binary string with the CREATE ASSEMBLY statement.
>
> --
> Erland Sommarskog, SQL Server MVP, esq...@sommarskog.se
>
> Books Online for SQL Server 2005 athttp://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books...
> Books Online for SQL Server 2000 athttp://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

[Back to original message]