 | |
SSMS 2008: Object Explorer Details
microsoft.public.sqlserver.tools microsoft.public.sqlserver.tools
 |
| | Thread Tools | Display Modes |
#41
 
| |||
| |||
|
Re: SSMS 2008: Object Explorer Details -
12-24-2008
, 05:28 PM
|
It was after testing with that and not having an issue that I figured out my problem was really with the objects that were in schemas other than dbo. All of the schemas were owned by the user id that created them rather than being owned by dbo. I changed them to dbo and was able to grant the permissions needed. I can now see the objects in SSMS without a problem. Thank you for your help and for including your script. |
....and for the future, recall to include such details that objects are
different schemas with different owners. It's easier to help when I
have the full knowledge of what is going on.
--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se
Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000: http://www.microsoft.com/sql/prodinf...ons/books.mspx
#42
| |||
| |||
|
|
It was after testing with that and not having an issue that I figured out my problem was really with the objects that were in schemas other than dbo. All of the schemas were owned by the user id that created them rather than being owned by dbo. I changed them to dbo and was able to grant the permissions needed. I can now see the objects in SSMS without a problem. Thank you for your help and for including your script. |
....and for the future, recall to include such details that objects are
different schemas with different owners. It's easier to help when I
have the full knowledge of what is going on.
--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se
Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000: http://www.microsoft.com/sql/prodinf...ons/books.mspx
#43
| |||
| |||
|
|
It was after testing with that and not having an issue that I figured out my problem was really with the objects that were in schemas other than dbo. All of the schemas were owned by the user id that created them rather than being owned by dbo. I changed them to dbo and was able to grant the permissions needed. I can now see the objects in SSMS without a problem. Thank you for your help and for including your script. |
....and for the future, recall to include such details that objects are
different schemas with different owners. It's easier to help when I
have the full knowledge of what is going on.
--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se
Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000: http://www.microsoft.com/sql/prodinf...ons/books.mspx
#44
| |||
| |||
|
|
It was after testing with that and not having an issue that I figured out my problem was really with the objects that were in schemas other than dbo. All of the schemas were owned by the user id that created them rather than being owned by dbo. I changed them to dbo and was able to grant the permissions needed. I can now see the objects in SSMS without a problem. Thank you for your help and for including your script. |
....and for the future, recall to include such details that objects are
different schemas with different owners. It's easier to help when I
have the full knowledge of what is going on.
--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se
Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000: http://www.microsoft.com/sql/prodinf...ons/books.mspx
#45
| |||
| |||
|
|
It was after testing with that and not having an issue that I figured out my problem was really with the objects that were in schemas other than dbo. All of the schemas were owned by the user id that created them rather than being owned by dbo. I changed them to dbo and was able to grant the permissions needed. I can now see the objects in SSMS without a problem. Thank you for your help and for including your script. |
....and for the future, recall to include such details that objects are
different schemas with different owners. It's easier to help when I
have the full knowledge of what is going on.
--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se
Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000: http://www.microsoft.com/sql/prodinf...ons/books.mspx
#46
| |||
| |||
|
|
It was after testing with that and not having an issue that I figured out my problem was really with the objects that were in schemas other than dbo. All of the schemas were owned by the user id that created them rather than being owned by dbo. I changed them to dbo and was able to grant the permissions needed. I can now see the objects in SSMS without a problem. Thank you for your help and for including your script. |
....and for the future, recall to include such details that objects are
different schemas with different owners. It's easier to help when I
have the full knowledge of what is going on.
--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se
Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000: http://www.microsoft.com/sql/prodinf...ons/books.mspx
|
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.