When a windowsuser being member of the SQLAgentOperatorRole (and not being sysadmin) creates a job (the owner = the domain account), and he wants takes a look at it afterward, he's not able to modify it !?!?!?
This would mean that when I want a user to be "jobmanager" for a server I need to make him sysadmin !!! ???
Is this a flaw in the system ?
Hi there,
How can I assign a user role of SQLAgentOperatorRole.
I tried with sp_addsrvrolemember but failed.
Thanks
Rahul
I think I might have made my relational database design wrong. As of right now I have three tables.
Users, Posts, Comments.
Users is related to posts, with u_id (primary key in users) being a foreign key in posts.
Posts is related to comments, p_id (primary key in posts) being a foreign key in comments.
Comments is related to users, with u_id (primary key in users) being a foreign key in comments.
As you can see, it creates a circle. The types of relationships are all right, I'm just worried that the diagram looks like the tables are in a circle because of the relationships. Is this ok? I wish I could attach a picture so you could see a diagram of the database.
This procedure has been returning duplicate numbers. (Tested with scripts that called this proc and put value in a table.)
How can it return duplicates? Does the transaction Begin/Commit not guarantee transactional consistency?
CREATE PROCEDURE sp_UpdateOrderNumber @customer int AS
DECLARE @NewOrderId int,
@nSQLError int,
@nRowCount int
BEGIN TRAN
UPDATE CUSTOMERS
SET ORDER_NUMBER=ORDER_NUMBER + 1
WHERE COMPANY_ID=@customer
SELECT@nSQLError = @@error,
@nRowCount = @@rowcount
If @nSQLError != 0 OR @nRowCount != 1 /* Check for Errors */
Begin
Rollback Tran
Return -999
End
SELECTORDER_NUMBER
FROMCUSTOMERS
WHERECOMPANY_ID=@customer
SELECT@nSQLError = @@error,
@nRowCount = @@rowcount
If @nSQLError != 0 OR @nRowCount != 1 /* Check for Errors */
Begin
Rollback Tran
Return -998
End
COMMIT TRAN