connectivityloginspermissionssql server
I tried creating a user with all privileges but I am getting this error:
Microsoft SQL Server Management Studio
Create failed for User 'Hru'. (Microsoft.SqlServer.Smo)
Additional information:
An exception occurred while executing a Transact-SQL statement or batch.
(Microsoft.SqlServer.ConnectionInfo)'Hru' is not a valid login or you do not have permission. (Microsoft SQL Server, Error: 15007)
Can anybody help me solve this?
If you have many jobs and do not know which job is owned by this login, this query will tell you the name of jobs owned by them:
SELECT j.name
FROM msdb.dbo.sysjobs AS j
INNER JOIN sys.syslogins AS l ON j.owner_sid = l.sid
WHERE l.name = 'loginYouWantToDelete'
Once you have found the job, you can delete it using: sp_delete_job: (From MSDN)
EXEC msdb.dbo.sp_delete_job
@job_name = N'JobToDelete';
I would try scripting out the operation instead of running whatever Management Studio is doing "for" you. You shouldn't need to use xp_fileexist (assuming you can validate that the files actually exist in the place the script says). Using 2012 SSMS, I am restoring to a point in time that does not coincide directly with a log backup:
The resulting script in my case was:
BACKUP LOG ... WITH NOFORMAT, NOINIT, NOSKIP, NOREWIND, NOUNLOAD, NORECOVERY
RESTORE DATABASE ... WITH FILE = 1, NORECOVERY, NOUNLOAD
RESTORE LOG ... WITH FILE = 1, NORECOVERY, NOUNLOAD
...
RESTORE LOG ... FROM DISK = [...path from line 1...] WITH NOUNLOAD, STOPAT = <time>
Best Answer
The error message is stating that SQL Server cannot locate a login named
Hiru, or you do not have the privilege required to create a user.The SQL Server security model consists1 of a server-level login that provides access at the instance level. Logins are then associated to a user inside each database. The user typically has the same name as the login, although that is not required.
Creating a login and user is easy to do with T-SQL, as in:
Using a T-SQL script provides more direct control over the process, and allows better troubleshooting.
1 - unless you're using the contained database security model