Re: After installing SP3 on Cluster Permission denied

From: Dan Guzman (danguzman@nospam-earthlink.net)
Date: 01/30/03 

From: "Dan Guzman" <danguzman@nospam-earthlink.net>
Date: Thu, 30 Jan 2003 06:25:17 -0600

It's difficult to say without more information but perhaps you need to
configure cross-database ownership chaining. This is necessary when an
object (stored procedure, view, function, trigger) references an object
in another database and permissions haven't been granted on the
referenced object.

You can turn on cross-database ownership chaining for individual user
databases with the 'DB chaining' database option. Alternatively, you
can do this at the server level with the 'Cross DB Ownership Chaining'
server option for backward compatibility. See the sp3readme.htm
included with SP3 for details. 

-- 
Hope this helps.
Dan Guzman
SQL Server MVP
-----------------------
SQL FAQ links (courtesy  Neil Pike):
http://www.ntfaq.com/Articles/Index.cfm?DepartmentID=800
http://www.sqlserverfaq.com
http://www.mssqlserver.com/faq
-----------------------
"Jörg Pfeifer" <no_spam_joerg.m.pfeifer@web.de> wrote in message
news:b1avtk$d4$01$1@news.t-online.com...
> Hi,
>
> Not accomplished after the installation of the SP3 some actions any
longer,
> there allegedly the rights for update, insert etc. to be missing. It
> concerns however an application, which runs for one year. Is this a
> well-known problem and as is the solution (The rights are also really
> missing and had again to be set )?
>
> Greetings
> --
> Jörg
>
>

Relevant Pages

  • Re: Invalid authorization specification
    ... One possibility is that you were using cross-database ownership chaining ... which SP3 disables by default because it's a security hole. ... > 2) I have SQL Server 2000 running on my local machine and> I recently upgraded it SP 3. ...
    (microsoft.public.sqlserver.security)
  • Re: Invalid authorization specification
    ... ownership chaining has to do with accessing a database on ... on server from a database on another server. ... remote SQL Server 6.5 that is completely independent of my ...
    (microsoft.public.sqlserver.security)
  • Re: After installing SP3 on Cluster Permission denied
    ... > configure cross-database ownership chaining. ... > databases with the 'DB chaining' database option. ... > can do this at the server level with the 'Cross DB Ownership Chaining' ...
    (microsoft.public.sqlserver.security)
  • Re: Cross DB ownership chaining problem
    ... is that the owner of database D is different than the other databases. ... you don't need to turn on cross-database chaining at the server ... level (sp_configure 'Cross DB Ownership Chaining') unless you want the ...
    (microsoft.public.sqlserver.security)
  • Re: Viewing object owner in SQL 2005 - ownership chaining
    ... The server principal "HFDB_2_0_readonly" is not able to access the database "Hotfix_data" under the current security context. ... To add on to Erland's response, the user needs a security context in both databases, even if no permissions are granted. ... I'm trying to set up Ownership Chaining. ... When I set up both a table and view from one logon and granted permissions to the view it didn't work, evidently because "creating user" is not equivalent to OWNER. ...
    (microsoft.public.sqlserver.security)
Quantcast