Re: Deploying CLR trigger to SQL-Server 2005 -- Permissions Required.
- From: Erland Sommarskog <esquel@xxxxxxxxxxxxx>
- Date: Mon, 28 Jan 2008 22:44:27 +0000 (UTC)
chris (chris.cudmore@xxxxxxxxx) 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, esquel@xxxxxxxxxxxxx
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
.
- Follow-Ups:
- References:
- Prev by Date: Re: multiple numbers in one statement
- Next by Date: Re: multiple numbers in one statement
- Previous by thread: Deploying CLR trigger to SQL-Server 2005 -- Permissions Required.
- Next by thread: Re: Deploying CLR trigger to SQL-Server 2005 -- Permissions Required.
- Index(es):
Relevant Pages
|
