Hi,
Sorry to post in this group. It seems only few people in SQL 2005 newsgroup now.
I met a problem in SQL SERVER 2005 SEPTEMBER CTP. The option "Cross
Database Ownership Chaining" won't work in SQL 2005 Step CTP. But there is
no problem if I call stored procedure to access a table in the sample database--AdventureWorks. for
example:
use msdb
go
drop proc sp_my_test
go
create proc sp_my_test
as
select * from AdventureWorks.Person.Address
--select * from pubs.dbo.test2
go
grant exec on sp_my_test to wdw
go
"wdw" is a normal account with minimal permission. When I called sp_my_test I got the data return.
But if I try to call a stored procedure to access a table in a new user database I got error: for
example:
use msdb
go
drop proc sp_my_test
go
create proc sp_my_test
as
select * from pubs.dbo.test2
go
grant exec on sp_my_test to wdw
go
"wdw" is the same account with minimal permission. Pubs database and test2 table are created by sa account.
When I call sp_my_test I met permission denied error:
The error is:
Msg 229, Level 14, State 5, Procedure my_test, Line 4
SELECT permission denied on object 'test2', database 'pubs', schema 'dbo'.
I changed the server and database option for Cross Database Ownership
Chaining. Neither works in my database but it DOES work for AdventureWorks. Even I
disable this option at server and database level it still works for AdventureWorks database. Can you do this simple test on your SQL 2005 and post your result?
Thanks for any help!
Bill
In order for the cross-database chain to be unbroken for schema owned by
'dbo' users, the databases need to be owned by the same login. The msdb
system database is owned by 'sa' so I would expect your test to work if you
change the owner of your 'pubs' database to 'sa' and turn on the DB_CHAINING
database option:
ALTER AUTHORIZATION ON DATABASE::pubs
TO sa
ALTER DATABASE pubs
SET DB_CHAINING ON
Hope this helps.
Dan Guzman
SQL Server MVP
"Bill Wang" <wdw2130833@.hotmail.com> wrote in message
news:%23BO$hZ82FHA.3136@.TK2MSFTNGP09.phx.gbl...
Hi,
Sorry to post in this group. It seems only few people in SQL 2005 newsgroup
now.
I met a problem in SQL SERVER 2005 SEPTEMBER CTP. The option "Cross
Database Ownership Chaining" won't work in SQL 2005 Step CTP. But there is
no problem if I call stored procedure to access a table in the sample
database--AdventureWorks. for
example:
use msdb
go
drop proc sp_my_test
go
create proc sp_my_test
as
select * from AdventureWorks.Person.Address
--select * from pubs.dbo.test2
go
grant exec on sp_my_test to wdw
go
"wdw" is a normal account with minimal permission. When I called sp_my_test
I got the data return.
But if I try to call a stored procedure to access a table in a new user
database I got error: for
example:
use msdb
go
drop proc sp_my_test
go
create proc sp_my_test
as
select * from pubs.dbo.test2
go
grant exec on sp_my_test to wdw
go
"wdw" is the same account with minimal permission. Pubs database and test2
table are created by sa account.
When I call sp_my_test I met permission denied error:
The error is:
Msg 229, Level 14, State 5, Procedure my_test, Line 4
SELECT permission denied on object 'test2', database 'pubs', schema 'dbo'.
I changed the server and database option for Cross Database Ownership
Chaining. Neither works in my database but it DOES work for AdventureWorks.
Even I
disable this option at server and database level it still works for
AdventureWorks database. Can you do this simple test on your SQL 2005 and
post your result?
Thanks for any help!
Bill
Showing posts with label chaining. Show all posts
Showing posts with label chaining. Show all posts
Sunday, February 19, 2012
Cross-database Ownership Chaining in SQL 2005
Hi,
Sorry to post in this group. It seems only few people in SQL 2005 newsgroup
now.
I met a problem in SQL SERVER 2005 SEPTEMBER CTP. The option "Cross
Database Ownership Chaining" won't work in SQL 2005 Step CTP. But there is
no problem if I call stored procedure to access a table in the sample databa
se--AdventureWorks. for
example:
use msdb
go
drop proc sp_my_test
go
create proc sp_my_test
as
select * from AdventureWorks.Person.Address
--select * from pubs.dbo.test2
go
grant exec on sp_my_test to wdw
go
"wdw" is a normal account with minimal permission. When I called sp_my_test
I got the data return.
But if I try to call a stored procedure to access a table in a new user data
base I got error: for
example:
use msdb
go
drop proc sp_my_test
go
create proc sp_my_test
as
select * from pubs.dbo.test2
go
grant exec on sp_my_test to wdw
go
"wdw" is the same account with minimal permission. Pubs database and test2 t
able are created by sa account.
When I call sp_my_test I met permission denied error:
The error is:
Msg 229, Level 14, State 5, Procedure my_test, Line 4
SELECT permission denied on object 'test2', database 'pubs', schema 'dbo'.
I changed the server and database option for Cross Database Ownership
Chaining. Neither works in my database but it DOES work for AdventureWorks.
Even I
disable this option at server and database level it still works for Adventur
eWorks database. Can you do this simple test on your SQL 2005 and post your
result?
Thanks for any help!
BillIn order for the cross-database chain to be unbroken for schema owned by
'dbo' users, the databases need to be owned by the same login. The msdb
system database is owned by 'sa' so I would expect your test to work if you
change the owner of your 'pubs' database to 'sa' and turn on the DB_CHAINING
database option:
ALTER AUTHORIZATION ON DATABASE::pubs
TO sa
ALTER DATABASE pubs
SET DB_CHAINING ON
Hope this helps.
Dan Guzman
SQL Server MVP
"Bill Wang" <wdw2130833@.hotmail.com> wrote in message
news:%23BO$hZ82FHA.3136@.TK2MSFTNGP09.phx.gbl...
Hi,
Sorry to post in this group. It seems only few people in SQL 2005 newsgroup
now.
I met a problem in SQL SERVER 2005 SEPTEMBER CTP. The option "Cross
Database Ownership Chaining" won't work in SQL 2005 Step CTP. But there is
no problem if I call stored procedure to access a table in the sample
database--AdventureWorks. for
example:
use msdb
go
drop proc sp_my_test
go
create proc sp_my_test
as
select * from AdventureWorks.Person.Address
--select * from pubs.dbo.test2
go
grant exec on sp_my_test to wdw
go
"wdw" is a normal account with minimal permission. When I called sp_my_test
I got the data return.
But if I try to call a stored procedure to access a table in a new user
database I got error: for
example:
use msdb
go
drop proc sp_my_test
go
create proc sp_my_test
as
select * from pubs.dbo.test2
go
grant exec on sp_my_test to wdw
go
"wdw" is the same account with minimal permission. Pubs database and test2
table are created by sa account.
When I call sp_my_test I met permission denied error:
The error is:
Msg 229, Level 14, State 5, Procedure my_test, Line 4
SELECT permission denied on object 'test2', database 'pubs', schema 'dbo'.
I changed the server and database option for Cross Database Ownership
Chaining. Neither works in my database but it DOES work for AdventureWorks.
Even I
disable this option at server and database level it still works for
AdventureWorks database. Can you do this simple test on your SQL 2005 and
post your result?
Thanks for any help!
Bill
Sorry to post in this group. It seems only few people in SQL 2005 newsgroup
now.
I met a problem in SQL SERVER 2005 SEPTEMBER CTP. The option "Cross
Database Ownership Chaining" won't work in SQL 2005 Step CTP. But there is
no problem if I call stored procedure to access a table in the sample databa
se--AdventureWorks. for
example:
use msdb
go
drop proc sp_my_test
go
create proc sp_my_test
as
select * from AdventureWorks.Person.Address
--select * from pubs.dbo.test2
go
grant exec on sp_my_test to wdw
go
"wdw" is a normal account with minimal permission. When I called sp_my_test
I got the data return.
But if I try to call a stored procedure to access a table in a new user data
base I got error: for
example:
use msdb
go
drop proc sp_my_test
go
create proc sp_my_test
as
select * from pubs.dbo.test2
go
grant exec on sp_my_test to wdw
go
"wdw" is the same account with minimal permission. Pubs database and test2 t
able are created by sa account.
When I call sp_my_test I met permission denied error:
The error is:
Msg 229, Level 14, State 5, Procedure my_test, Line 4
SELECT permission denied on object 'test2', database 'pubs', schema 'dbo'.
I changed the server and database option for Cross Database Ownership
Chaining. Neither works in my database but it DOES work for AdventureWorks.
Even I
disable this option at server and database level it still works for Adventur
eWorks database. Can you do this simple test on your SQL 2005 and post your
result?
Thanks for any help!
BillIn order for the cross-database chain to be unbroken for schema owned by
'dbo' users, the databases need to be owned by the same login. The msdb
system database is owned by 'sa' so I would expect your test to work if you
change the owner of your 'pubs' database to 'sa' and turn on the DB_CHAINING
database option:
ALTER AUTHORIZATION ON DATABASE::pubs
TO sa
ALTER DATABASE pubs
SET DB_CHAINING ON
Hope this helps.
Dan Guzman
SQL Server MVP
"Bill Wang" <wdw2130833@.hotmail.com> wrote in message
news:%23BO$hZ82FHA.3136@.TK2MSFTNGP09.phx.gbl...
Hi,
Sorry to post in this group. It seems only few people in SQL 2005 newsgroup
now.
I met a problem in SQL SERVER 2005 SEPTEMBER CTP. The option "Cross
Database Ownership Chaining" won't work in SQL 2005 Step CTP. But there is
no problem if I call stored procedure to access a table in the sample
database--AdventureWorks. for
example:
use msdb
go
drop proc sp_my_test
go
create proc sp_my_test
as
select * from AdventureWorks.Person.Address
--select * from pubs.dbo.test2
go
grant exec on sp_my_test to wdw
go
"wdw" is a normal account with minimal permission. When I called sp_my_test
I got the data return.
But if I try to call a stored procedure to access a table in a new user
database I got error: for
example:
use msdb
go
drop proc sp_my_test
go
create proc sp_my_test
as
select * from pubs.dbo.test2
go
grant exec on sp_my_test to wdw
go
"wdw" is the same account with minimal permission. Pubs database and test2
table are created by sa account.
When I call sp_my_test I met permission denied error:
The error is:
Msg 229, Level 14, State 5, Procedure my_test, Line 4
SELECT permission denied on object 'test2', database 'pubs', schema 'dbo'.
I changed the server and database option for Cross Database Ownership
Chaining. Neither works in my database but it DOES work for AdventureWorks.
Even I
disable this option at server and database level it still works for
AdventureWorks database. Can you do this simple test on your SQL 2005 and
post your result?
Thanks for any help!
Bill
Cross-database Ownership Chaining in SQL 2005
This is a multi-part message in MIME format.
--=_NextPart_000_0010_01C5DBA4.D8BB4C00
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hi,
Sorry to post in this group. It seems only few people in SQL 2005 = newsgroup now.
I met a problem in SQL SERVER 2005 SEPTEMBER CTP. The option "Cross Database Ownership Chaining" won't work in SQL 2005 Step CTP. But there = is no problem if I call stored procedure to access a table in the sample = database--AdventureWorks. for example:
use msdb
go
drop proc sp_my_test
go
create proc sp_my_test
as
select * from AdventureWorks.Person.Address
--select * from pubs.dbo.test2
go
grant exec on sp_my_test to wdw
go
"wdw" is a normal account with minimal permission. When I called = sp_my_test I got the data return.
But if I try to call a stored procedure to access a table in a new user = database I got error: for example:
use msdb
go
drop proc sp_my_test
go
create proc sp_my_test
as
select * from pubs.dbo.test2
go
grant exec on sp_my_test to wdw
go
"wdw" is the same account with minimal permission. Pubs database and = test2 table are created by sa account.
When I call sp_my_test I met permission denied error:
The error is:
Msg 229, Level 14, State 5, Procedure my_test, Line 4
SELECT permission denied on object 'test2', database 'pubs', schema = 'dbo'.
I changed the server and database option for Cross Database Ownership Chaining. Neither works in my database but it DOES work for = AdventureWorks. Even I disable this option at server and database level it still works for = AdventureWorks database. Can you do this simple test on your SQL 2005 = and post your result?
Thanks for any help!
Bill
--=_NextPart_000_0010_01C5DBA4.D8BB4C00
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
Hi,
Sorry to post in this group. It = seems only few people in SQL 2005 newsgroup now.
I met a problem in SQL SERVER 2005 SEPTEMBER CTP. The option "Cross Database Ownership Chaining" won't work in SQL 2005 Step CTP. But = there is no problem if I call stored procedure to access a table in the = sample database--AdventureWorks. for example:
use msdbgodrop proc = sp_my_testgocreate proc sp_my_testasselect * from = AdventureWorks.Person.Address--select * from pubs.dbo.test2gogrant exec on sp_my_test to = wdwgo
"wdw" is a normal account with minimal permission. When I called sp_my_test I got the data return.But if I try to call a stored procedure to access a table in a new user database I got error: for example:use msdbgodrop proc = sp_my_testgocreate proc sp_my_testasselect * from pubs.dbo.test2gogrant exec on sp_my_test to wdwgo
"wdw" is the same account with = minimal permission. Pubs database and test2 table are created by sa account.
When I call sp_my_test I met permission = denied error:
The error is:Msg 229, Level 14, State 5, Procedure = my_test, Line 4SELECT permission denied on object 'test2', database 'pubs', schema = 'dbo'.I changed the server and database option for Cross = Database Ownership Chaining. Neither works in my database but it DOES = work for AdventureWorks. Even I disable this option at server and = database level it still works for AdventureWorks database. Can you do this simple test = on your SQL 2005 and post your result?Thanks for any = help!Bill
--=_NextPart_000_0010_01C5DBA4.D8BB4C00--In order for the cross-database chain to be unbroken for schema owned by
'dbo' users, the databases need to be owned by the same login. The msdb
system database is owned by 'sa' so I would expect your test to work if you
change the owner of your 'pubs' database to 'sa' and turn on the DB_CHAINING
database option:
ALTER AUTHORIZATION ON DATABASE::pubs
TO sa
ALTER DATABASE pubs
SET DB_CHAINING ON
Hope this helps.
Dan Guzman
SQL Server MVP
"Bill Wang" <wdw2130833@.hotmail.com> wrote in message
news:%23BO$hZ82FHA.3136@.TK2MSFTNGP09.phx.gbl...
Hi,
Sorry to post in this group. It seems only few people in SQL 2005 newsgroup
now.
I met a problem in SQL SERVER 2005 SEPTEMBER CTP. The option "Cross
Database Ownership Chaining" won't work in SQL 2005 Step CTP. But there is
no problem if I call stored procedure to access a table in the sample
database--AdventureWorks. for
example:
use msdb
go
drop proc sp_my_test
go
create proc sp_my_test
as
select * from AdventureWorks.Person.Address
--select * from pubs.dbo.test2
go
grant exec on sp_my_test to wdw
go
"wdw" is a normal account with minimal permission. When I called sp_my_test
I got the data return.
But if I try to call a stored procedure to access a table in a new user
database I got error: for
example:
use msdb
go
drop proc sp_my_test
go
create proc sp_my_test
as
select * from pubs.dbo.test2
go
grant exec on sp_my_test to wdw
go
"wdw" is the same account with minimal permission. Pubs database and test2
table are created by sa account.
When I call sp_my_test I met permission denied error:
The error is:
Msg 229, Level 14, State 5, Procedure my_test, Line 4
SELECT permission denied on object 'test2', database 'pubs', schema 'dbo'.
I changed the server and database option for Cross Database Ownership
Chaining. Neither works in my database but it DOES work for AdventureWorks.
Even I
disable this option at server and database level it still works for
AdventureWorks database. Can you do this simple test on your SQL 2005 and
post your result?
Thanks for any help!
Bill
--=_NextPart_000_0010_01C5DBA4.D8BB4C00
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hi,
Sorry to post in this group. It seems only few people in SQL 2005 = newsgroup now.
I met a problem in SQL SERVER 2005 SEPTEMBER CTP. The option "Cross Database Ownership Chaining" won't work in SQL 2005 Step CTP. But there = is no problem if I call stored procedure to access a table in the sample = database--AdventureWorks. for example:
use msdb
go
drop proc sp_my_test
go
create proc sp_my_test
as
select * from AdventureWorks.Person.Address
--select * from pubs.dbo.test2
go
grant exec on sp_my_test to wdw
go
"wdw" is a normal account with minimal permission. When I called = sp_my_test I got the data return.
But if I try to call a stored procedure to access a table in a new user = database I got error: for example:
use msdb
go
drop proc sp_my_test
go
create proc sp_my_test
as
select * from pubs.dbo.test2
go
grant exec on sp_my_test to wdw
go
"wdw" is the same account with minimal permission. Pubs database and = test2 table are created by sa account.
When I call sp_my_test I met permission denied error:
The error is:
Msg 229, Level 14, State 5, Procedure my_test, Line 4
SELECT permission denied on object 'test2', database 'pubs', schema = 'dbo'.
I changed the server and database option for Cross Database Ownership Chaining. Neither works in my database but it DOES work for = AdventureWorks. Even I disable this option at server and database level it still works for = AdventureWorks database. Can you do this simple test on your SQL 2005 = and post your result?
Thanks for any help!
Bill
--=_NextPart_000_0010_01C5DBA4.D8BB4C00
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
Hi,
Sorry to post in this group. It = seems only few people in SQL 2005 newsgroup now.
I met a problem in SQL SERVER 2005 SEPTEMBER CTP. The option "Cross Database Ownership Chaining" won't work in SQL 2005 Step CTP. But = there is no problem if I call stored procedure to access a table in the = sample database--AdventureWorks. for example:
use msdbgodrop proc = sp_my_testgocreate proc sp_my_testasselect * from = AdventureWorks.Person.Address--select * from pubs.dbo.test2gogrant exec on sp_my_test to = wdwgo
"wdw" is a normal account with minimal permission. When I called sp_my_test I got the data return.But if I try to call a stored procedure to access a table in a new user database I got error: for example:use msdbgodrop proc = sp_my_testgocreate proc sp_my_testasselect * from pubs.dbo.test2gogrant exec on sp_my_test to wdwgo
"wdw" is the same account with = minimal permission. Pubs database and test2 table are created by sa account.
When I call sp_my_test I met permission = denied error:
The error is:Msg 229, Level 14, State 5, Procedure = my_test, Line 4SELECT permission denied on object 'test2', database 'pubs', schema = 'dbo'.I changed the server and database option for Cross = Database Ownership Chaining. Neither works in my database but it DOES = work for AdventureWorks. Even I disable this option at server and = database level it still works for AdventureWorks database. Can you do this simple test = on your SQL 2005 and post your result?Thanks for any = help!Bill
--=_NextPart_000_0010_01C5DBA4.D8BB4C00--In order for the cross-database chain to be unbroken for schema owned by
'dbo' users, the databases need to be owned by the same login. The msdb
system database is owned by 'sa' so I would expect your test to work if you
change the owner of your 'pubs' database to 'sa' and turn on the DB_CHAINING
database option:
ALTER AUTHORIZATION ON DATABASE::pubs
TO sa
ALTER DATABASE pubs
SET DB_CHAINING ON
Hope this helps.
Dan Guzman
SQL Server MVP
"Bill Wang" <wdw2130833@.hotmail.com> wrote in message
news:%23BO$hZ82FHA.3136@.TK2MSFTNGP09.phx.gbl...
Hi,
Sorry to post in this group. It seems only few people in SQL 2005 newsgroup
now.
I met a problem in SQL SERVER 2005 SEPTEMBER CTP. The option "Cross
Database Ownership Chaining" won't work in SQL 2005 Step CTP. But there is
no problem if I call stored procedure to access a table in the sample
database--AdventureWorks. for
example:
use msdb
go
drop proc sp_my_test
go
create proc sp_my_test
as
select * from AdventureWorks.Person.Address
--select * from pubs.dbo.test2
go
grant exec on sp_my_test to wdw
go
"wdw" is a normal account with minimal permission. When I called sp_my_test
I got the data return.
But if I try to call a stored procedure to access a table in a new user
database I got error: for
example:
use msdb
go
drop proc sp_my_test
go
create proc sp_my_test
as
select * from pubs.dbo.test2
go
grant exec on sp_my_test to wdw
go
"wdw" is the same account with minimal permission. Pubs database and test2
table are created by sa account.
When I call sp_my_test I met permission denied error:
The error is:
Msg 229, Level 14, State 5, Procedure my_test, Line 4
SELECT permission denied on object 'test2', database 'pubs', schema 'dbo'.
I changed the server and database option for Cross Database Ownership
Chaining. Neither works in my database but it DOES work for AdventureWorks.
Even I
disable this option at server and database level it still works for
AdventureWorks database. Can you do this simple test on your SQL 2005 and
post your result?
Thanks for any help!
Bill
Cross-Database Ownership Chaining
SQL Server 2000 SP3
Has anyone had any problems with Cross-Database Ownership Chaining in SQL
Server 2000?Can you be more specific ?
--
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Delton Blackwell" <deltonblackwell@.hotmail.com> wrote in message
news:ecGuR0NJFHA.588@.TK2MSFTNGP15.phx.gbl...
> SQL Server 2000 SP3
> Has anyone had any problems with Cross-Database Ownership Chaining in SQL
> Server 2000?
>
Has anyone had any problems with Cross-Database Ownership Chaining in SQL
Server 2000?Can you be more specific ?
--
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Delton Blackwell" <deltonblackwell@.hotmail.com> wrote in message
news:ecGuR0NJFHA.588@.TK2MSFTNGP15.phx.gbl...
> SQL Server 2000 SP3
> Has anyone had any problems with Cross-Database Ownership Chaining in SQL
> Server 2000?
>
Cross-Database Ownership Chaining
I have two databases A and B. Need to see some data on B.
I know I can use Cross-Database Ownership Chaining in order to get
access on B. Are there any alternatives?
In other database systems I did this by setting up an Alias to
database B and specifing the account to use for the connection to B.
thanks,Hi,
Thanks for your post.
To let me better understand this issue, I would like to confirm a
conception from you:
Is the Cross-database Ownership Chaining as you referenced in the form of
"server.database.schema.table"?
SQL Server doesn't support custom database alias to reference the original.
If you use linked server, you can use sp_addlinkedserver to add a linked
server to the current SQL Server and specify the login account in the
remote server.
In addition to the chaining expression "server.database.schema.table", you
can use OPENQUERY or OPENROWSET to access the remote server.
For the usage of OPENQUERY and OPENROWSET, you may refer to SQL Server Book
Online.
If you have any other questions or concerns, please feel free to let me
know. It's my pleasure to be of assistance.
++++++++++++++++++++++++++++++++
Charles Wang
Microsoft Online Partner Support
++++++++++++++++++++++++++++++++
PLEASE NOTE: The partner managed newsgroups are provided
to assist with break/fix issues and simple how to questions.
We also love to hear your product feedback!
Let us know what you think by posting
- from the web interface: Partner Feedback
- from your newsreader:
microsoft.private.directaccess.partnerfeedback.
We look forward to hearing from you!
======================================================When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================This posting is provided "AS IS" with no warranties, a
nd confers no rights.
======================================================
I know I can use Cross-Database Ownership Chaining in order to get
access on B. Are there any alternatives?
In other database systems I did this by setting up an Alias to
database B and specifing the account to use for the connection to B.
thanks,Hi,
Thanks for your post.
To let me better understand this issue, I would like to confirm a
conception from you:
Is the Cross-database Ownership Chaining as you referenced in the form of
"server.database.schema.table"?
SQL Server doesn't support custom database alias to reference the original.
If you use linked server, you can use sp_addlinkedserver to add a linked
server to the current SQL Server and specify the login account in the
remote server.
In addition to the chaining expression "server.database.schema.table", you
can use OPENQUERY or OPENROWSET to access the remote server.
For the usage of OPENQUERY and OPENROWSET, you may refer to SQL Server Book
Online.
If you have any other questions or concerns, please feel free to let me
know. It's my pleasure to be of assistance.
++++++++++++++++++++++++++++++++
Charles Wang
Microsoft Online Partner Support
++++++++++++++++++++++++++++++++
PLEASE NOTE: The partner managed newsgroups are provided
to assist with break/fix issues and simple how to questions.
We also love to hear your product feedback!
Let us know what you think by posting
- from the web interface: Partner Feedback
- from your newsreader:
microsoft.private.directaccess.partnerfeedback.
We look forward to hearing from you!
======================================================When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================This posting is provided "AS IS" with no warranties, a
nd confers no rights.
======================================================
Cross-Database Ownership Chaining
SQL Server 2000 SP3
Has anyone had any problems with Cross-Database Ownership Chaining in SQL
Server 2000?
Can you be more specific ?
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Delton Blackwell" <deltonblackwell@.hotmail.com> wrote in message
news:ecGuR0NJFHA.588@.TK2MSFTNGP15.phx.gbl...
> SQL Server 2000 SP3
> Has anyone had any problems with Cross-Database Ownership Chaining in SQL
> Server 2000?
>
Has anyone had any problems with Cross-Database Ownership Chaining in SQL
Server 2000?
Can you be more specific ?
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Delton Blackwell" <deltonblackwell@.hotmail.com> wrote in message
news:ecGuR0NJFHA.588@.TK2MSFTNGP15.phx.gbl...
> SQL Server 2000 SP3
> Has anyone had any problems with Cross-Database Ownership Chaining in SQL
> Server 2000?
>
Cross-Database Ownership Chaining
SQL Server 2000 SP3
Has anyone had any problems with Cross-Database Ownership Chaining in SQL
Server 2000?Can you be more specific ?
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Delton Blackwell" <deltonblackwell@.hotmail.com> wrote in message
news:ecGuR0NJFHA.588@.TK2MSFTNGP15.phx.gbl...
> SQL Server 2000 SP3
> Has anyone had any problems with Cross-Database Ownership Chaining in SQL
> Server 2000?
>
Has anyone had any problems with Cross-Database Ownership Chaining in SQL
Server 2000?Can you be more specific ?
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Delton Blackwell" <deltonblackwell@.hotmail.com> wrote in message
news:ecGuR0NJFHA.588@.TK2MSFTNGP15.phx.gbl...
> SQL Server 2000 SP3
> Has anyone had any problems with Cross-Database Ownership Chaining in SQL
> Server 2000?
>
Cross-Database Ownership Chaining
I have two databases A and B. Need to see some data on B.
I know I can use Cross-Database Ownership Chaining in order to get
access on B. Are there any alternatives?
In other database systems I did this by setting up an Alias to
database B and specifing the account to use for the connection to B.
thanks,Hi,
Thanks for your post.
To let me better understand this issue, I would like to confirm a
conception from you:
Is the Cross-database Ownership Chaining as you referenced in the form of
"server.database.schema.table"?
SQL Server doesn't support custom database alias to reference the original.
If you use linked server, you can use sp_addlinkedserver to add a linked
server to the current SQL Server and specify the login account in the
remote server.
In addition to the chaining expression "server.database.schema.table", you
can use OPENQUERY or OPENROWSET to access the remote server.
For the usage of OPENQUERY and OPENROWSET, you may refer to SQL Server Book
Online.
If you have any other questions or concerns, please feel free to let me
know. It's my pleasure to be of assistance.
++++++++++++++++++++++++++++++++
Charles Wang
Microsoft Online Partner Support
++++++++++++++++++++++++++++++++
PLEASE NOTE: The partner managed newsgroups are provided
to assist with break/fix issues and simple how to questions.
We also love to hear your product feedback!
Let us know what you think by posting
- from the web interface: Partner Feedback
- from your newsreader:
microsoft.private.directaccess.partnerfeedback.
We look forward to hearing from you!
========================================
==============
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
========================================
==============
This posting is provided "AS IS" with no warranties, a
nd confers no rights.
========================================
==============
I know I can use Cross-Database Ownership Chaining in order to get
access on B. Are there any alternatives?
In other database systems I did this by setting up an Alias to
database B and specifing the account to use for the connection to B.
thanks,Hi,
Thanks for your post.
To let me better understand this issue, I would like to confirm a
conception from you:
Is the Cross-database Ownership Chaining as you referenced in the form of
"server.database.schema.table"?
SQL Server doesn't support custom database alias to reference the original.
If you use linked server, you can use sp_addlinkedserver to add a linked
server to the current SQL Server and specify the login account in the
remote server.
In addition to the chaining expression "server.database.schema.table", you
can use OPENQUERY or OPENROWSET to access the remote server.
For the usage of OPENQUERY and OPENROWSET, you may refer to SQL Server Book
Online.
If you have any other questions or concerns, please feel free to let me
know. It's my pleasure to be of assistance.
++++++++++++++++++++++++++++++++
Charles Wang
Microsoft Online Partner Support
++++++++++++++++++++++++++++++++
PLEASE NOTE: The partner managed newsgroups are provided
to assist with break/fix issues and simple how to questions.
We also love to hear your product feedback!
Let us know what you think by posting
- from the web interface: Partner Feedback
- from your newsreader:
microsoft.private.directaccess.partnerfeedback.
We look forward to hearing from you!
========================================
==============
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
========================================
==============
This posting is provided "AS IS" with no warranties, a
nd confers no rights.
========================================
==============
Tuesday, February 14, 2012
Cross DB ownership chaining
Hello,
I am having trouble setting up cross db ownership chaining. Did I omit
anything?
1. Using SQL Server 2000 SP3a.
2. Login as 'sa'.
3. Create new database A1.
4. Create new database A2.
5. Create TableA in database A2.
6. Create view vTableA in database A1 as select * from A2.dbo.TableA
7. Add UserA to database A1.
8. Grant select permission on vTableA to UserA.
9. Enable cross database ownerchip chaining option in database A1 and A2.
10. All objects are owned by dbo and both databases are owned by 'sa'.
11. Log in as UserA and run Select * from vTableA in database A1, get error
"Server user 'UserA' is not a valid user in database 'A2'.".
Unless I'm missing something, I was expecting the last step to work. Any
help greatly appreciated.
PaulUserA needs a security context in database A2, although no object
permissions need be granted. You can either add the user to database A2 or
enable the guest user in database A2.
Hope this helps.
Dan Guzman
SQL Server MVP
"Paul" <Paul@.discussions.microsoft.com> wrote in message
news:43D9406C-1C28-4A86-BF39-9A2D7E1B2CFB@.microsoft.com...
> Hello,
> I am having trouble setting up cross db ownership chaining. Did I omit
> anything?
> 1. Using SQL Server 2000 SP3a.
> 2. Login as 'sa'.
> 3. Create new database A1.
> 4. Create new database A2.
> 5. Create TableA in database A2.
> 6. Create view vTableA in database A1 as select * from A2.dbo.TableA
> 7. Add UserA to database A1.
> 8. Grant select permission on vTableA to UserA.
> 9. Enable cross database ownerchip chaining option in database A1 and A2.
> 10. All objects are owned by dbo and both databases are owned by 'sa'.
> 11. Log in as UserA and run Select * from vTableA in database A1, get
> error
> "Server user 'UserA' is not a valid user in database 'A2'.".
> Unless I'm missing something, I was expecting the last step to work. Any
> help greatly appreciated.
> Paul|||(thump on head) Thanks Dan, that did it.
"Dan Guzman" wrote:
> UserA needs a security context in database A2, although no object
> permissions need be granted. You can either add the user to database A2 o
r
> enable the guest user in database A2.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Paul" <Paul@.discussions.microsoft.com> wrote in message
> news:43D9406C-1C28-4A86-BF39-9A2D7E1B2CFB@.microsoft.com...
>
>
I am having trouble setting up cross db ownership chaining. Did I omit
anything?
1. Using SQL Server 2000 SP3a.
2. Login as 'sa'.
3. Create new database A1.
4. Create new database A2.
5. Create TableA in database A2.
6. Create view vTableA in database A1 as select * from A2.dbo.TableA
7. Add UserA to database A1.
8. Grant select permission on vTableA to UserA.
9. Enable cross database ownerchip chaining option in database A1 and A2.
10. All objects are owned by dbo and both databases are owned by 'sa'.
11. Log in as UserA and run Select * from vTableA in database A1, get error
"Server user 'UserA' is not a valid user in database 'A2'.".
Unless I'm missing something, I was expecting the last step to work. Any
help greatly appreciated.
PaulUserA needs a security context in database A2, although no object
permissions need be granted. You can either add the user to database A2 or
enable the guest user in database A2.
Hope this helps.
Dan Guzman
SQL Server MVP
"Paul" <Paul@.discussions.microsoft.com> wrote in message
news:43D9406C-1C28-4A86-BF39-9A2D7E1B2CFB@.microsoft.com...
> Hello,
> I am having trouble setting up cross db ownership chaining. Did I omit
> anything?
> 1. Using SQL Server 2000 SP3a.
> 2. Login as 'sa'.
> 3. Create new database A1.
> 4. Create new database A2.
> 5. Create TableA in database A2.
> 6. Create view vTableA in database A1 as select * from A2.dbo.TableA
> 7. Add UserA to database A1.
> 8. Grant select permission on vTableA to UserA.
> 9. Enable cross database ownerchip chaining option in database A1 and A2.
> 10. All objects are owned by dbo and both databases are owned by 'sa'.
> 11. Log in as UserA and run Select * from vTableA in database A1, get
> error
> "Server user 'UserA' is not a valid user in database 'A2'.".
> Unless I'm missing something, I was expecting the last step to work. Any
> help greatly appreciated.
> Paul|||(thump on head) Thanks Dan, that did it.
"Dan Guzman" wrote:
> UserA needs a security context in database A2, although no object
> permissions need be granted. You can either add the user to database A2 o
r
> enable the guest user in database A2.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Paul" <Paul@.discussions.microsoft.com> wrote in message
> news:43D9406C-1C28-4A86-BF39-9A2D7E1B2CFB@.microsoft.com...
>
>
Cross database ownership chaining question
Do we need to worry about the default SP3 service pack upgrade which has
cross database ownership chaining disabled of all our objects on all
databases are owned by dbo.Using SQL 2000The cross-database ownership chaining option is only needed if you have
cross-database object references and users don't have permissions on the
referenced objects. If you have problems after disabling this option, you
can either turn it on selectively in the databases involved or grant direct
permissions on the referenced objects.
Note that your databases are not owned by 'dbo' - databases are owned by
logins (e'g' 'sa'). In order to maintain an unbroken cross-database
ownership chain for dbo-owned objects, the databases involved must be owned
by the same login.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:eG1vClmyDHA.2156@.TK2MSFTNGP09.phx.gbl...
> Do we need to worry about the default SP3 service pack upgrade which has
> cross database ownership chaining disabled of all our objects on all
> databases are owned by dbo.Using SQL 2000
>|||Is there some scripts that I can download to demonstrate this ?
"Dan Guzman" <danguzman@.nospam-earthlink.net> wrote in message
news:e3iiH5myDHA.1744@.TK2MSFTNGP12.phx.gbl...
> The cross-database ownership chaining option is only needed if you have
> cross-database object references and users don't have permissions on the
> referenced objects. If you have problems after disabling this option, you
> can either turn it on selectively in the databases involved or grant
direct
> permissions on the referenced objects.
> Note that your databases are not owned by 'dbo' - databases are owned by
> logins (e'g' 'sa'). In order to maintain an unbroken cross-database
> ownership chain for dbo-owned objects, the databases involved must be
owned
> by the same login.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
>
> "Hassan" <fatima_ja@.hotmail.com> wrote in message
> news:eG1vClmyDHA.2156@.TK2MSFTNGP09.phx.gbl...
> > Do we need to worry about the default SP3 service pack upgrade which has
> > cross database ownership chaining disabled of all our objects on all
> > databases are owned by dbo.Using SQL 2000
> >
> >
>|||This KB article contains some scripts:
http://support.microsoft.com/default.aspx?scid=kb;en-us;272424&Product=sql2k
There is more info about cross db ownership chaining here:
http://support.microsoft.com/default.aspx?scid=kb;en-us;810474&Product=sql2k
--
HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:u6#BmQqyDHA.540@.tk2msftngp13.phx.gbl...
> Is there some scripts that I can download to demonstrate this ?
> "Dan Guzman" <danguzman@.nospam-earthlink.net> wrote in message
> news:e3iiH5myDHA.1744@.TK2MSFTNGP12.phx.gbl...
> > The cross-database ownership chaining option is only needed if you have
> > cross-database object references and users don't have permissions on the
> > referenced objects. If you have problems after disabling this option,
you
> > can either turn it on selectively in the databases involved or grant
> direct
> > permissions on the referenced objects.
> >
> > Note that your databases are not owned by 'dbo' - databases are owned by
> > logins (e'g' 'sa'). In order to maintain an unbroken cross-database
> > ownership chain for dbo-owned objects, the databases involved must be
> owned
> > by the same login.
> >
> > --
> > Hope this helps.
> >
> > Dan Guzman
> > SQL Server MVP
> >
> >
> > "Hassan" <fatima_ja@.hotmail.com> wrote in message
> > news:eG1vClmyDHA.2156@.TK2MSFTNGP09.phx.gbl...
> > > Do we need to worry about the default SP3 service pack upgrade which
has
> > > cross database ownership chaining disabled of all our objects on all
> > > databases are owned by dbo.Using SQL 2000
> > >
> > >
> >
> >
>
cross database ownership chaining disabled of all our objects on all
databases are owned by dbo.Using SQL 2000The cross-database ownership chaining option is only needed if you have
cross-database object references and users don't have permissions on the
referenced objects. If you have problems after disabling this option, you
can either turn it on selectively in the databases involved or grant direct
permissions on the referenced objects.
Note that your databases are not owned by 'dbo' - databases are owned by
logins (e'g' 'sa'). In order to maintain an unbroken cross-database
ownership chain for dbo-owned objects, the databases involved must be owned
by the same login.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:eG1vClmyDHA.2156@.TK2MSFTNGP09.phx.gbl...
> Do we need to worry about the default SP3 service pack upgrade which has
> cross database ownership chaining disabled of all our objects on all
> databases are owned by dbo.Using SQL 2000
>|||Is there some scripts that I can download to demonstrate this ?
"Dan Guzman" <danguzman@.nospam-earthlink.net> wrote in message
news:e3iiH5myDHA.1744@.TK2MSFTNGP12.phx.gbl...
> The cross-database ownership chaining option is only needed if you have
> cross-database object references and users don't have permissions on the
> referenced objects. If you have problems after disabling this option, you
> can either turn it on selectively in the databases involved or grant
direct
> permissions on the referenced objects.
> Note that your databases are not owned by 'dbo' - databases are owned by
> logins (e'g' 'sa'). In order to maintain an unbroken cross-database
> ownership chain for dbo-owned objects, the databases involved must be
owned
> by the same login.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
>
> "Hassan" <fatima_ja@.hotmail.com> wrote in message
> news:eG1vClmyDHA.2156@.TK2MSFTNGP09.phx.gbl...
> > Do we need to worry about the default SP3 service pack upgrade which has
> > cross database ownership chaining disabled of all our objects on all
> > databases are owned by dbo.Using SQL 2000
> >
> >
>|||This KB article contains some scripts:
http://support.microsoft.com/default.aspx?scid=kb;en-us;272424&Product=sql2k
There is more info about cross db ownership chaining here:
http://support.microsoft.com/default.aspx?scid=kb;en-us;810474&Product=sql2k
--
HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:u6#BmQqyDHA.540@.tk2msftngp13.phx.gbl...
> Is there some scripts that I can download to demonstrate this ?
> "Dan Guzman" <danguzman@.nospam-earthlink.net> wrote in message
> news:e3iiH5myDHA.1744@.TK2MSFTNGP12.phx.gbl...
> > The cross-database ownership chaining option is only needed if you have
> > cross-database object references and users don't have permissions on the
> > referenced objects. If you have problems after disabling this option,
you
> > can either turn it on selectively in the databases involved or grant
> direct
> > permissions on the referenced objects.
> >
> > Note that your databases are not owned by 'dbo' - databases are owned by
> > logins (e'g' 'sa'). In order to maintain an unbroken cross-database
> > ownership chain for dbo-owned objects, the databases involved must be
> owned
> > by the same login.
> >
> > --
> > Hope this helps.
> >
> > Dan Guzman
> > SQL Server MVP
> >
> >
> > "Hassan" <fatima_ja@.hotmail.com> wrote in message
> > news:eG1vClmyDHA.2156@.TK2MSFTNGP09.phx.gbl...
> > > Do we need to worry about the default SP3 service pack upgrade which
has
> > > cross database ownership chaining disabled of all our objects on all
> > > databases are owned by dbo.Using SQL 2000
> > >
> > >
> >
> >
>
Cross database ownership chaining
IN Enterpriese manaage on databasse properties tab i see
an option "Allow Cross database ownership chaining"
What is this as i dont find anything in BOL for this
Thanks
SanjayHi Sanjay
Did you update your Books Online for SP3? There is a page about this. Make
sure your BOL title bar says Updated - SP3.
Or you check out this KB article:
http://support.microsoft.com/default.aspx?scid=kb;en-us;810474&Product=sql
--
HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"Sanjay" <sanjayg@.hotmail.com> wrote in message
news:08bb01c3a25b$39d3a080$a101280a@.phx.gbl...
> IN Enterpriese manaage on databasse properties tab i see
> an option "Allow Cross database ownership chaining"
> What is this as i dont find anything in BOL for this
> Thanks
> Sanjay|||It was introduced in sp3. Check out the readme that came with sp3.
--
Tibor Karaszi
"Sanjay" <sanjayg@.hotmail.com> wrote in message
news:08bb01c3a25b$39d3a080$a101280a@.phx.gbl...
> IN Enterpriese manaage on databasse properties tab i see
> an option "Allow Cross database ownership chaining"
> What is this as i dont find anything in BOL for this
> Thanks
> Sanjay|||The title bar only says "SQL server Books online"
It says the same on the server machine also where i am
sure SP3 was installed
Anyways on my PC i found a page on "Ownership Chains"
Apart from that am i suppose to have anythng else in BOL
Thanks
Sanjay
>--Original Message--
>Hi Sanjay
>Did you update your Books Online for SP3? There is a page
about this. Make
>sure your BOL title bar says Updated - SP3.
>Or you check out this KB article:
>http://support.microsoft.com/default.aspx?scid=kb;en-
us;810474&Product=sql
>--
>HTH
>--
>Kalen Delaney
>SQL Server MVP
>www.SolidQualityLearning.com
>
>"Sanjay" <sanjayg@.hotmail.com> wrote in message
>news:08bb01c3a25b$39d3a080$a101280a@.phx.gbl...
>> IN Enterpriese manaage on databasse properties tab i see
>> an option "Allow Cross database ownership chaining"
>> What is this as i dont find anything in BOL for this
>> Thanks
>> Sanjay
>
>.
>|||The sp3 update for Books Online is not installed with sp3. It is a separate
download and install.
--
Tibor Karaszi
"Sanjay" <sanjayg@.hotmail.com> wrote in message
news:085a01c3a260$beaaa380$a301280a@.phx.gbl...
> The title bar only says "SQL server Books online"
> It says the same on the server machine also where i am
> sure SP3 was installed
> Anyways on my PC i found a page on "Ownership Chains"
> Apart from that am i suppose to have anythng else in BOL
> Thanks
> Sanjay
> >--Original Message--
> >Hi Sanjay
> >
> >Did you update your Books Online for SP3? There is a page
> about this. Make
> >sure your BOL title bar says Updated - SP3.
> >Or you check out this KB article:
> >
> >http://support.microsoft.com/default.aspx?scid=kb;en-
> us;810474&Product=sql
> >
> >--
> >HTH
> >--
> >Kalen Delaney
> >SQL Server MVP
> >www.SolidQualityLearning.com
> >
> >
> >"Sanjay" <sanjayg@.hotmail.com> wrote in message
> >news:08bb01c3a25b$39d3a080$a101280a@.phx.gbl...
> >> IN Enterpriese manaage on databasse properties tab i see
> >> an option "Allow Cross database ownership chaining"
> >>
> >> What is this as i dont find anything in BOL for this
> >>
> >> Thanks
> >> Sanjay
> >
> >
> >.
> >
an option "Allow Cross database ownership chaining"
What is this as i dont find anything in BOL for this
Thanks
SanjayHi Sanjay
Did you update your Books Online for SP3? There is a page about this. Make
sure your BOL title bar says Updated - SP3.
Or you check out this KB article:
http://support.microsoft.com/default.aspx?scid=kb;en-us;810474&Product=sql
--
HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"Sanjay" <sanjayg@.hotmail.com> wrote in message
news:08bb01c3a25b$39d3a080$a101280a@.phx.gbl...
> IN Enterpriese manaage on databasse properties tab i see
> an option "Allow Cross database ownership chaining"
> What is this as i dont find anything in BOL for this
> Thanks
> Sanjay|||It was introduced in sp3. Check out the readme that came with sp3.
--
Tibor Karaszi
"Sanjay" <sanjayg@.hotmail.com> wrote in message
news:08bb01c3a25b$39d3a080$a101280a@.phx.gbl...
> IN Enterpriese manaage on databasse properties tab i see
> an option "Allow Cross database ownership chaining"
> What is this as i dont find anything in BOL for this
> Thanks
> Sanjay|||The title bar only says "SQL server Books online"
It says the same on the server machine also where i am
sure SP3 was installed
Anyways on my PC i found a page on "Ownership Chains"
Apart from that am i suppose to have anythng else in BOL
Thanks
Sanjay
>--Original Message--
>Hi Sanjay
>Did you update your Books Online for SP3? There is a page
about this. Make
>sure your BOL title bar says Updated - SP3.
>Or you check out this KB article:
>http://support.microsoft.com/default.aspx?scid=kb;en-
us;810474&Product=sql
>--
>HTH
>--
>Kalen Delaney
>SQL Server MVP
>www.SolidQualityLearning.com
>
>"Sanjay" <sanjayg@.hotmail.com> wrote in message
>news:08bb01c3a25b$39d3a080$a101280a@.phx.gbl...
>> IN Enterpriese manaage on databasse properties tab i see
>> an option "Allow Cross database ownership chaining"
>> What is this as i dont find anything in BOL for this
>> Thanks
>> Sanjay
>
>.
>|||The sp3 update for Books Online is not installed with sp3. It is a separate
download and install.
--
Tibor Karaszi
"Sanjay" <sanjayg@.hotmail.com> wrote in message
news:085a01c3a260$beaaa380$a301280a@.phx.gbl...
> The title bar only says "SQL server Books online"
> It says the same on the server machine also where i am
> sure SP3 was installed
> Anyways on my PC i found a page on "Ownership Chains"
> Apart from that am i suppose to have anythng else in BOL
> Thanks
> Sanjay
> >--Original Message--
> >Hi Sanjay
> >
> >Did you update your Books Online for SP3? There is a page
> about this. Make
> >sure your BOL title bar says Updated - SP3.
> >Or you check out this KB article:
> >
> >http://support.microsoft.com/default.aspx?scid=kb;en-
> us;810474&Product=sql
> >
> >--
> >HTH
> >--
> >Kalen Delaney
> >SQL Server MVP
> >www.SolidQualityLearning.com
> >
> >
> >"Sanjay" <sanjayg@.hotmail.com> wrote in message
> >news:08bb01c3a25b$39d3a080$a101280a@.phx.gbl...
> >> IN Enterpriese manaage on databasse properties tab i see
> >> an option "Allow Cross database ownership chaining"
> >>
> >> What is this as i dont find anything in BOL for this
> >>
> >> Thanks
> >> Sanjay
> >
> >
> >.
> >
Subscribe to:
Posts (Atom)