Viewing 6 posts - 1 through 7 (of 7 total)
As a further update to this, I can enable the sysadmin account then logon and create server logins/db users manually, but not via the stored procedure it would seem.
I've also...
July 10, 2013 at 10:38 am
Cool, that's fixed the syntax error but not the permissions error:
CREATE LOGIN [test1] WITH PASSWORD = N'wibble',DEFAULT_DATABASE=[Master], CHECK_EXPIRATION=OFF, CHECK_POLICY=OFF;
Msg 15247, Level 16, State 1, Line 1
User does not have permission...
July 10, 2013 at 9:43 am
Have created the superuser but get the following error now :angry:
CREATE LOGIN [test1] WITH PASSWORD = 'password',N' DEFAULT_DATABASE=[Master], CHECK_EXPIRATION=OFF, CHECK_POLICY=OFF;
Msg 105, Level 15, State 1, Line 1
Unclosed quotation mark after...
July 10, 2013 at 9:01 am
Apologies, I forgot to add that Obewan is part of the DB_owner role for the DB, and is a sysadmin as server level.
So do you need to grant explicit perms...
July 10, 2013 at 8:05 am
OK, I've tweaked the elevated perms SP script as follows:
USE [SM_Test]
GO
/****** Object: StoredProcedure [dbo].[pr_CallBoostedSecurityProcess] Script Date: 10/07/2013 14:27:38 ******/
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
ALTER procedure [dbo].[pr_CallBoostedSecurityProcess]( @name...
July 10, 2013 at 7:33 am
Thanks for the reply, I'm not too hot on T-SQL but will read through it and see if I can work it out 🙂
July 9, 2013 at 9:56 am
Viewing 6 posts - 1 through 7 (of 7 total)