What are the pros of having SQL Server instance added to Active Directory ?
I was looking at the server properties and saw the Active Directory tab and
had an option to add it.
What may be the cons ? Right now none of our SQL Servers are added. Do most
of you add the server to AD ? What am I missing by not doing so ? Thanks
Well, are you using AD for anything now? If not, it is unlikely that the
mere adding of SQL Server to AD will produce any tangible benefits.
What you get by adding SQL Server to AD are things like Service Publication,
which is just a fancy form of an alias or DNS, IMHO. For example, if SQL
Server is on myServer01, it can be published through AD, then you can move
the server and clients do not need to know that the server has moved...
Since, instead of using a hard-coded IP address or server name, you are
going through AD, and it is redirecting you based solely on the name of the
database you want to connect to. This means you will have to change your
applications (and expect to need this flexibility) before you will see this
benefit.
A few of the problems I see with the above approach:
(a) obviously with AD there are more security considerations, so it won't be
like SQL Server authentication anymore. Apps have to be rewritten and
protecting the directory might take a significant amount of work.
(b) in our environment we have several locations with the same database -
e.g. Dev, QA, Production. If I want to connect to the Sales database, I now
have to think about this differently. Instead of "just connect to the Sales
database on the QA server," I now have to give each one a distinct
publication name, such as QA-SalesDB. This isn't a difficult change, and in
fact in some lights it is better, but it is a change, and we know how some
people are resistant to even the smallest delta in mindset or approach.
(c) using SQL through ADSI versus directly through the OLEDB provider can
cause some problems with existing code (and habits that will lend to
continuing to write code this way). There is no longer the ability to use
SELECT * ... You must name your columns.
As in a previous thread, I strongly suggest you spend some time reading on
the subject. You'll be much better informed to make a decision than just
listening to opinions (which are not based at all on anything specific in
YOUR environment).
ADSI and using SQL Server through AD are documented in MSDN Online, as well
as several 3rd party web sites.
On 3/20/05 2:51 PM, in article #NqyHZYLFHA.732@.TK2MSFTNGP12.phx.gbl,
"Hassan" <fatima_ja@.hotmail.com> wrote:
> What are the pros of having SQL Server instance added to Active Directory ?
> I was looking at the server properties and saw the Active Directory tab and
> had an option to add it.
> What may be the cons ? Right now none of our SQL Servers are added. Do most
> of you add the server to AD ? What am I missing by not doing so ? Thanks
>
Showing posts with label properties. Show all posts
Showing posts with label properties. Show all posts
Friday, March 30, 2012
Pros of having SQL server added to AD
What are the pros of having SQL Server instance added to Active Directory ?
I was looking at the server properties and saw the Active Directory tab and
had an option to add it.
What may be the cons ? Right now none of our SQL Servers are added. Do most
of you add the server to AD ? What am I missing by not doing so ? ThanksWell, are you using AD for anything now? If not, it is unlikely that the
mere adding of SQL Server to AD will produce any tangible benefits.
What you get by adding SQL Server to AD are things like Service Publication,
which is just a fancy form of an alias or DNS, IMHO. For example, if SQL
Server is on myServer01, it can be published through AD, then you can move
the server and clients do not need to know that the server has moved...
Since, instead of using a hard-coded IP address or server name, you are
going through AD, and it is redirecting you based solely on the name of the
database you want to connect to. This means you will have to change your
applications (and expect to need this flexibility) before you will see this
benefit.
A few of the problems I see with the above approach:
(a) obviously with AD there are more security considerations, so it won't be
like SQL Server authentication anymore. Apps have to be rewritten and
protecting the directory might take a significant amount of work.
(b) in our environment we have several locations with the same database -
e.g. Dev, QA, Production. If I want to connect to the Sales database, I now
have to think about this differently. Instead of "just connect to the Sales
database on the QA server," I now have to give each one a distinct
publication name, such as QA-SalesDB. This isn't a difficult change, and in
fact in some lights it is better, but it is a change, and we know how some
people are resistant to even the smallest delta in mindset or approach.
(c) using SQL through ADSI versus directly through the OLEDB provider can
cause some problems with existing code (and habits that will lend to
continuing to write code this way). There is no longer the ability to use
SELECT * ... You must name your columns.
As in a previous thread, I strongly suggest you spend some time reading on
the subject. You'll be much better informed to make a decision than just
listening to opinions (which are not based at all on anything specific in
YOUR environment).
ADSI and using SQL Server through AD are documented in MSDN Online, as well
as several 3rd party web sites.
On 3/20/05 2:51 PM, in article #NqyHZYLFHA.732@.TK2MSFTNGP12.phx.gbl,
"Hassan" <fatima_ja@.hotmail.com> wrote:
> What are the pros of having SQL Server instance added to Active Directory ?
> I was looking at the server properties and saw the Active Directory tab and
> had an option to add it.
> What may be the cons ? Right now none of our SQL Servers are added. Do most
> of you add the server to AD ? What am I missing by not doing so ? Thanks
>sql
I was looking at the server properties and saw the Active Directory tab and
had an option to add it.
What may be the cons ? Right now none of our SQL Servers are added. Do most
of you add the server to AD ? What am I missing by not doing so ? ThanksWell, are you using AD for anything now? If not, it is unlikely that the
mere adding of SQL Server to AD will produce any tangible benefits.
What you get by adding SQL Server to AD are things like Service Publication,
which is just a fancy form of an alias or DNS, IMHO. For example, if SQL
Server is on myServer01, it can be published through AD, then you can move
the server and clients do not need to know that the server has moved...
Since, instead of using a hard-coded IP address or server name, you are
going through AD, and it is redirecting you based solely on the name of the
database you want to connect to. This means you will have to change your
applications (and expect to need this flexibility) before you will see this
benefit.
A few of the problems I see with the above approach:
(a) obviously with AD there are more security considerations, so it won't be
like SQL Server authentication anymore. Apps have to be rewritten and
protecting the directory might take a significant amount of work.
(b) in our environment we have several locations with the same database -
e.g. Dev, QA, Production. If I want to connect to the Sales database, I now
have to think about this differently. Instead of "just connect to the Sales
database on the QA server," I now have to give each one a distinct
publication name, such as QA-SalesDB. This isn't a difficult change, and in
fact in some lights it is better, but it is a change, and we know how some
people are resistant to even the smallest delta in mindset or approach.
(c) using SQL through ADSI versus directly through the OLEDB provider can
cause some problems with existing code (and habits that will lend to
continuing to write code this way). There is no longer the ability to use
SELECT * ... You must name your columns.
As in a previous thread, I strongly suggest you spend some time reading on
the subject. You'll be much better informed to make a decision than just
listening to opinions (which are not based at all on anything specific in
YOUR environment).
ADSI and using SQL Server through AD are documented in MSDN Online, as well
as several 3rd party web sites.
On 3/20/05 2:51 PM, in article #NqyHZYLFHA.732@.TK2MSFTNGP12.phx.gbl,
"Hassan" <fatima_ja@.hotmail.com> wrote:
> What are the pros of having SQL Server instance added to Active Directory ?
> I was looking at the server properties and saw the Active Directory tab and
> had an option to add it.
> What may be the cons ? Right now none of our SQL Servers are added. Do most
> of you add the server to AD ? What am I missing by not doing so ? Thanks
>sql
Pros of having SQL server added to AD
What are the pros of having SQL Server instance added to Active Directory ?
I was looking at the server properties and saw the Active Directory tab and
had an option to add it.
What may be the cons ? Right now none of our SQL Servers are added. Do most
of you add the server to AD ? What am I missing by not doing so ? ThanksWell, are you using AD for anything now? If not, it is unlikely that the
mere adding of SQL Server to AD will produce any tangible benefits.
What you get by adding SQL Server to AD are things like Service Publication,
which is just a fancy form of an alias or DNS, IMHO. For example, if SQL
Server is on myServer01, it can be published through AD, then you can move
the server and clients do not need to know that the server has moved...
Since, instead of using a hard-coded IP address or server name, you are
going through AD, and it is redirecting you based solely on the name of the
database you want to connect to. This means you will have to change your
applications (and expect to need this flexibility) before you will see this
benefit.
A few of the problems I see with the above approach:
(a) obviously with AD there are more security considerations, so it won't be
like SQL Server authentication anymore. Apps have to be rewritten and
protecting the directory might take a significant amount of work.
(b) in our environment we have several locations with the same database -
e.g. Dev, QA, Production. If I want to connect to the Sales database, I now
have to think about this differently. Instead of "just connect to the Sales
database on the QA server," I now have to give each one a distinct
publication name, such as QA-SalesDB. This isn't a difficult change, and in
fact in some lights it is better, but it is a change, and we know how some
people are resistant to even the smallest delta in mindset or approach.
(c) using SQL through ADSI versus directly through the OLEDB provider can
cause some problems with existing code (and habits that will lend to
continuing to write code this way). There is no longer the ability to use
SELECT * ... You must name your columns.
As in a previous thread, I strongly suggest you spend some time reading on
the subject. You'll be much better informed to make a decision than just
listening to opinions (which are not based at all on anything specific in
YOUR environment).
ADSI and using SQL Server through AD are documented in MSDN Online, as well
as several 3rd party web sites.
On 3/20/05 2:51 PM, in article #NqyHZYLFHA.732@.TK2MSFTNGP12.phx.gbl,
"Hassan" <fatima_ja@.hotmail.com> wrote:
> What are the pros of having SQL Server instance added to Active Directory
?
> I was looking at the server properties and saw the Active Directory tab an
d
> had an option to add it.
> What may be the cons ? Right now none of our SQL Servers are added. Do mos
t
> of you add the server to AD ? What am I missing by not doing so ? Thanks
>
I was looking at the server properties and saw the Active Directory tab and
had an option to add it.
What may be the cons ? Right now none of our SQL Servers are added. Do most
of you add the server to AD ? What am I missing by not doing so ? ThanksWell, are you using AD for anything now? If not, it is unlikely that the
mere adding of SQL Server to AD will produce any tangible benefits.
What you get by adding SQL Server to AD are things like Service Publication,
which is just a fancy form of an alias or DNS, IMHO. For example, if SQL
Server is on myServer01, it can be published through AD, then you can move
the server and clients do not need to know that the server has moved...
Since, instead of using a hard-coded IP address or server name, you are
going through AD, and it is redirecting you based solely on the name of the
database you want to connect to. This means you will have to change your
applications (and expect to need this flexibility) before you will see this
benefit.
A few of the problems I see with the above approach:
(a) obviously with AD there are more security considerations, so it won't be
like SQL Server authentication anymore. Apps have to be rewritten and
protecting the directory might take a significant amount of work.
(b) in our environment we have several locations with the same database -
e.g. Dev, QA, Production. If I want to connect to the Sales database, I now
have to think about this differently. Instead of "just connect to the Sales
database on the QA server," I now have to give each one a distinct
publication name, such as QA-SalesDB. This isn't a difficult change, and in
fact in some lights it is better, but it is a change, and we know how some
people are resistant to even the smallest delta in mindset or approach.
(c) using SQL through ADSI versus directly through the OLEDB provider can
cause some problems with existing code (and habits that will lend to
continuing to write code this way). There is no longer the ability to use
SELECT * ... You must name your columns.
As in a previous thread, I strongly suggest you spend some time reading on
the subject. You'll be much better informed to make a decision than just
listening to opinions (which are not based at all on anything specific in
YOUR environment).
ADSI and using SQL Server through AD are documented in MSDN Online, as well
as several 3rd party web sites.
On 3/20/05 2:51 PM, in article #NqyHZYLFHA.732@.TK2MSFTNGP12.phx.gbl,
"Hassan" <fatima_ja@.hotmail.com> wrote:
> What are the pros of having SQL Server instance added to Active Directory
?
> I was looking at the server properties and saw the Active Directory tab an
d
> had an option to add it.
> What may be the cons ? Right now none of our SQL Servers are added. Do mos
t
> of you add the server to AD ? What am I missing by not doing so ? Thanks
>
Proprties not imported with Table
I am developing a DB with others in my group. When I import tables created on other servers to my server, the primary key and other properties do not import with the tables. Can anyone explain why this is happening? Is there a setting I have over looked?If you use DTS, make usre you use the Copy object(s) instead of Copy table(s) option.|||Nope...what method are you using to migrate the Data
Look at DTS transfer Database Task option
Or better yet, script the objects then build them...I prefer this method, and use bcp|||Originally posted by joejcheng
If you use DTS, make usre you use the Copy object(s) instead of Copy table(s) option.
The copy object worked ... Thanks
Look at DTS transfer Database Task option
Or better yet, script the objects then build them...I prefer this method, and use bcp|||Originally posted by joejcheng
If you use DTS, make usre you use the Copy object(s) instead of Copy table(s) option.
The copy object worked ... Thanks
Wednesday, March 28, 2012
Property Owner is not available for Database '[DTA_TaxMan]'. This property may not exist
I get the following error everytime I try to go to the properties of
one of my databases.
The help link was useless.
I am not sure what to do. I am the top level administrator to my
server.
===================================
Cannot show requested dialog.
===================================
Cannot show requested dialog. (SqlMgmt)
Program Location:
at
Microsoft.SqlServer.Management.SqlMgmt.DefaultLaun chFormHostedControlAllocator.AllocateDialog(XmlDoc ument
initializationXml, IServiceProvider dialogServiceProvider,
CDataContainer dc)
at
Microsoft.SqlServer.Management.SqlMgmt.DefaultLaun chFormHostedControlAllocator.Microsoft.SqlServer.M anagement.SqlMgmt.ILaunchFormHostedControlAllocato r.CreateDialog(XmlDocument
initializationXml, IServiceProvider dialogServiceProvider)
at
Microsoft.SqlServer.Management.SqlMgmt.LaunchForm. InitializeForm(XmlDocument
doc, IServiceProvider provider, ISqlControlCollection control)
at
Microsoft.SqlServer.Management.SqlMgmt.LaunchForm. .ctor(XmlDocument
doc, IServiceProvider provider)
at
Microsoft.SqlServer.Management.UI.VSIntegration.Ob jectExplorer.ToolsMenuItem.OnCreateAndShowForm(ISe rviceProvider
sp, XmlDocument doc)
at
Microsoft.SqlServer.Management.SqlMgmt.RunningForm sTable.RunningFormsTableImpl.ThreadStarter.StartTh read()
===================================
Property Owner is not available for Database '[DTA_TaxMan]'. This
property may not exist for this object, or may not be retrievable due
to insufficient access rights. (Microsoft.SqlServer.Smo)
For help, click:
[url]http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00. 2047.00&EvtSrc=Microsoft.SqlServer.Management.Smo. ExceptionTemplates.PropertyCannotBeRetrievedExcept ionText&EvtID=Owner&LinkId=20476[/url]
Program Location:
at
Microsoft.SqlServer.Management.Smo.PropertyCollect ion.HandleNullValue(Int32
index)
at Microsoft.SqlServer.Management.Smo.Database.get_Ow ner()
at
Microsoft.SqlServer.Management.SqlManagerUI.Create DatabaseData.DatabasePrototype.DatabaseData..ctor( CDataContainer
context, String databaseName)
at
Microsoft.SqlServer.Management.SqlManagerUI.Create DatabaseData.DatabasePrototype.LoadDefinition(Stri ng
newName)
at
Microsoft.SqlServer.Management.SqlManagerUI.Create DatabaseData.DatabasePrototype..ctor(CDataContaine r
context)
at
Microsoft.SqlServer.Management.SqlManagerUI.DBProp Sheet..ctor(CDataContainer
context)
I have also signed back in with SA, and still having the same problem.
sql
one of my databases.
The help link was useless.
I am not sure what to do. I am the top level administrator to my
server.
===================================
Cannot show requested dialog.
===================================
Cannot show requested dialog. (SqlMgmt)
Program Location:
at
Microsoft.SqlServer.Management.SqlMgmt.DefaultLaun chFormHostedControlAllocator.AllocateDialog(XmlDoc ument
initializationXml, IServiceProvider dialogServiceProvider,
CDataContainer dc)
at
Microsoft.SqlServer.Management.SqlMgmt.DefaultLaun chFormHostedControlAllocator.Microsoft.SqlServer.M anagement.SqlMgmt.ILaunchFormHostedControlAllocato r.CreateDialog(XmlDocument
initializationXml, IServiceProvider dialogServiceProvider)
at
Microsoft.SqlServer.Management.SqlMgmt.LaunchForm. InitializeForm(XmlDocument
doc, IServiceProvider provider, ISqlControlCollection control)
at
Microsoft.SqlServer.Management.SqlMgmt.LaunchForm. .ctor(XmlDocument
doc, IServiceProvider provider)
at
Microsoft.SqlServer.Management.UI.VSIntegration.Ob jectExplorer.ToolsMenuItem.OnCreateAndShowForm(ISe rviceProvider
sp, XmlDocument doc)
at
Microsoft.SqlServer.Management.SqlMgmt.RunningForm sTable.RunningFormsTableImpl.ThreadStarter.StartTh read()
===================================
Property Owner is not available for Database '[DTA_TaxMan]'. This
property may not exist for this object, or may not be retrievable due
to insufficient access rights. (Microsoft.SqlServer.Smo)
For help, click:
[url]http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00. 2047.00&EvtSrc=Microsoft.SqlServer.Management.Smo. ExceptionTemplates.PropertyCannotBeRetrievedExcept ionText&EvtID=Owner&LinkId=20476[/url]
Program Location:
at
Microsoft.SqlServer.Management.Smo.PropertyCollect ion.HandleNullValue(Int32
index)
at Microsoft.SqlServer.Management.Smo.Database.get_Ow ner()
at
Microsoft.SqlServer.Management.SqlManagerUI.Create DatabaseData.DatabasePrototype.DatabaseData..ctor( CDataContainer
context, String databaseName)
at
Microsoft.SqlServer.Management.SqlManagerUI.Create DatabaseData.DatabasePrototype.LoadDefinition(Stri ng
newName)
at
Microsoft.SqlServer.Management.SqlManagerUI.Create DatabaseData.DatabasePrototype..ctor(CDataContaine r
context)
at
Microsoft.SqlServer.Management.SqlManagerUI.DBProp Sheet..ctor(CDataContainer
context)
I have also signed back in with SA, and still having the same problem.
sql
Property Owner is not available for Database '[DTA_TaxMan]'. This property may not exist
I get the following error everytime I try to go to the properties of
one of my databases.
The help link was useless.
I am not sure what to do. I am the top level administrator to my
server.
===================================
Cannot show requested dialog.
===================================
Cannot show requested dialog. (SqlMgmt)
--
Program Location:
at
Microsoft.SqlServer.Management.SqlMgmt.DefaultLaunchFormHostedControlAllocator.AllocateDialog(XmlDocument
initializationXml, IServiceProvider dialogServiceProvider,
CDataContainer dc)
at
Microsoft.SqlServer.Management.SqlMgmt.DefaultLaunchFormHostedControlAllocator.Microsoft.SqlServer.Management.SqlMgmt.ILaunchFormHostedControlAllocator.CreateDialog(XmlDocument
initializationXml, IServiceProvider dialogServiceProvider)
at
Microsoft.SqlServer.Management.SqlMgmt.LaunchForm.InitializeForm(XmlDocument
doc, IServiceProvider provider, ISqlControlCollection control)
at
Microsoft.SqlServer.Management.SqlMgmt.LaunchForm..ctor(XmlDocument
doc, IServiceProvider provider)
at
Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ToolsMenuItem.OnCreateAndShowForm(IServiceProvider
sp, XmlDocument doc)
at
Microsoft.SqlServer.Management.SqlMgmt.RunningFormsTable.RunningFormsTableImpl.ThreadStarter.StartThread()
===================================
Property Owner is not available for Database '[DTA_TaxMan]'. This
property may not exist for this object, or may not be retrievable due
to insufficient access rights. (Microsoft.SqlServer.Smo)
--
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.2047.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.PropertyCannotBeRetrievedExceptionText&EvtID=Owner&LinkId=20476
--
Program Location:
at
Microsoft.SqlServer.Management.Smo.PropertyCollection.HandleNullValue(Int32
index)
at Microsoft.SqlServer.Management.Smo.Database.get_Owner()
at
Microsoft.SqlServer.Management.SqlManagerUI.CreateDatabaseData.DatabasePrototype.DatabaseData..ctor(CDataContainer
context, String databaseName)
at
Microsoft.SqlServer.Management.SqlManagerUI.CreateDatabaseData.DatabasePrototype.LoadDefinition(String
newName)
at
Microsoft.SqlServer.Management.SqlManagerUI.CreateDatabaseData.DatabasePrototype..ctor(CDataContainer
context)
at
Microsoft.SqlServer.Management.SqlManagerUI.DBPropSheet..ctor(CDataContainer
context)I have also signed back in with SA, and still having the same problem.
one of my databases.
The help link was useless.
I am not sure what to do. I am the top level administrator to my
server.
===================================
Cannot show requested dialog.
===================================
Cannot show requested dialog. (SqlMgmt)
--
Program Location:
at
Microsoft.SqlServer.Management.SqlMgmt.DefaultLaunchFormHostedControlAllocator.AllocateDialog(XmlDocument
initializationXml, IServiceProvider dialogServiceProvider,
CDataContainer dc)
at
Microsoft.SqlServer.Management.SqlMgmt.DefaultLaunchFormHostedControlAllocator.Microsoft.SqlServer.Management.SqlMgmt.ILaunchFormHostedControlAllocator.CreateDialog(XmlDocument
initializationXml, IServiceProvider dialogServiceProvider)
at
Microsoft.SqlServer.Management.SqlMgmt.LaunchForm.InitializeForm(XmlDocument
doc, IServiceProvider provider, ISqlControlCollection control)
at
Microsoft.SqlServer.Management.SqlMgmt.LaunchForm..ctor(XmlDocument
doc, IServiceProvider provider)
at
Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ToolsMenuItem.OnCreateAndShowForm(IServiceProvider
sp, XmlDocument doc)
at
Microsoft.SqlServer.Management.SqlMgmt.RunningFormsTable.RunningFormsTableImpl.ThreadStarter.StartThread()
===================================
Property Owner is not available for Database '[DTA_TaxMan]'. This
property may not exist for this object, or may not be retrievable due
to insufficient access rights. (Microsoft.SqlServer.Smo)
--
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.2047.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.PropertyCannotBeRetrievedExceptionText&EvtID=Owner&LinkId=20476
--
Program Location:
at
Microsoft.SqlServer.Management.Smo.PropertyCollection.HandleNullValue(Int32
index)
at Microsoft.SqlServer.Management.Smo.Database.get_Owner()
at
Microsoft.SqlServer.Management.SqlManagerUI.CreateDatabaseData.DatabasePrototype.DatabaseData..ctor(CDataContainer
context, String databaseName)
at
Microsoft.SqlServer.Management.SqlManagerUI.CreateDatabaseData.DatabasePrototype.LoadDefinition(String
newName)
at
Microsoft.SqlServer.Management.SqlManagerUI.CreateDatabaseData.DatabasePrototype..ctor(CDataContainer
context)
at
Microsoft.SqlServer.Management.SqlManagerUI.DBPropSheet..ctor(CDataContainer
context)I have also signed back in with SA, and still having the same problem.
Property Owner is not available for Database
I am getting this error while selecting the properties of one database.
Property Owner is not available for Database '[TEST]'. This property may not exist for this object, or may not be retrievable due to insufficient access rights. (Microsoft.SqlServer.Smo)
Suddently this error started coming ? why ?
Make sure that the database owner is/was not a user / principal which has been deleted in the meantime. Orphaned database owner can be fixed using the sp_changedbowner and assigning a new owner to the database.
Jens K. Suessmeyer
http://www.sqlserver2005.de
|||Thanks..
I am getting this error while executing this.Do you know how to see the current/previous owner in studio ?
USE [TEST]
GO
EXEC sp_changedbowner 'dbo'
GO
Error
Msg 15151, Level 16, State 1, Line 1
Cannot find the principal 'dbo', because it does not exist or you do not have permission.
|||
You will have to provide a server prinicpal like 'sa'
To get the current owners, you will have to use something like the following:
SELECT databases.NAME,server_Principals.NAME
FROM sys.[databases]
INNER JOIN sys.[server_principals]
ON
[databases].owner_sid = [server_principals].sid
Jens K. Suessmeyer
http://www.sqlserver2005.de
|||1) In this database all the tables/views owner is dbo.does that mean dbo should set as database owner ?
Your query is seleted only 7 databases Out of 15 databases . What is that mean ?
Can one database work with out principal login ? What is the default owner of non-system databases ?
Is there any code changes required if any database owner change ?
2) In studio , what is the difference between root--> security-->logins vs root>databases>TEST-->security--> users
Thanks
Julius
|||That means that a macthing sid is not found int he server principals table, these database seem owner orphaned. Use a left join to find out which ones are not in there.
Databases can work without a principals owner but this should not be a normal state.
The default owner of newly created database is the server principal who created the database.
The are no code changes unless you use something like database ownership chaining.
2) The first path are the server principals (logins who have access to the server), the second path are the database principals (Server principals mapped to database principals) whoc have certain permissions on the database either through individual rights or group memebership.
Jens K. Suessmeyer
http://www.sqlserver2005.de
Property IsPrimaryFile is not available for DataFile
I backup an SQL Server 2000 database (MY_DATABASE) and restore it in
SQLServer 2005.
Then, when I try to access its properties I get:
Property IsPrimaryFile is not available for DataFile '[MY_DATABASE]'. This
property may not exist for this object, or may not be retrievable due to
insufficient access rights. (Microsoft.SqlServer.Smo)
- I'm using a windows 2003 administrator account
- I tried setting compatibility level to 90 but it didn't help.
- If I connect with a sql-level user (not windows 2003 login) a can view the
properties, but I can't change anything.
Any ideas?
Thanks!http://www.dbtalk.net/microsoft-public-sqlserver-setup/copying-databse-sql-2000-sql-265404.html
"Gaspar" <Gaspar@.Gaspar.com> wrote in message
news:uOX2SbJaGHA.3612@.TK2MSFTNGP03.phx.gbl...
>I backup an SQL Server 2000 database (MY_DATABASE) and restore it in
>SQLServer 2005.
> Then, when I try to access its properties I get:
> Property IsPrimaryFile is not available for DataFile '[MY_DATABASE]'. This
> property may not exist for this object, or may not be retrievable due to
> insufficient access rights. (Microsoft.SqlServer.Smo)
> - I'm using a windows 2003 administrator account
> - I tried setting compatibility level to 90 but it didn't help.
> - If I connect with a sql-level user (not windows 2003 login) a can view
> the properties, but I can't change anything.
> Any ideas?
> Thanks!
>
SQLServer 2005.
Then, when I try to access its properties I get:
Property IsPrimaryFile is not available for DataFile '[MY_DATABASE]'. This
property may not exist for this object, or may not be retrievable due to
insufficient access rights. (Microsoft.SqlServer.Smo)
- I'm using a windows 2003 administrator account
- I tried setting compatibility level to 90 but it didn't help.
- If I connect with a sql-level user (not windows 2003 login) a can view the
properties, but I can't change anything.
Any ideas?
Thanks!http://www.dbtalk.net/microsoft-public-sqlserver-setup/copying-databse-sql-2000-sql-265404.html
"Gaspar" <Gaspar@.Gaspar.com> wrote in message
news:uOX2SbJaGHA.3612@.TK2MSFTNGP03.phx.gbl...
>I backup an SQL Server 2000 database (MY_DATABASE) and restore it in
>SQLServer 2005.
> Then, when I try to access its properties I get:
> Property IsPrimaryFile is not available for DataFile '[MY_DATABASE]'. This
> property may not exist for this object, or may not be retrievable due to
> insufficient access rights. (Microsoft.SqlServer.Smo)
> - I'm using a windows 2003 administrator account
> - I tried setting compatibility level to 90 but it didn't help.
> - If I connect with a sql-level user (not windows 2003 login) a can view
> the properties, but I can't change anything.
> Any ideas?
> Thanks!
>
Property IsPrimaryFile is not available for DataFile
I backup an SQL Server 2000 database (MY_DATABASE) and restore it in
SQLServer 2005.
Then, when I try to access its properties I get:
Property IsPrimaryFile is not available for DataFile '[MY_DATABASE]'. Th
is
property may not exist for this object, or may not be retrievable due to
insufficient access rights. (Microsoft.SqlServer.Smo)
- I'm using a windows 2003 administrator account
- I tried setting compatibility level to 90 but it didn't help.
- If I connect with a sql-level user (not windows 2003 login) a can view the
properties, but I can't change anything.
Any ideas?
Thanks!http://www.dbtalk.net/microsoft-pub...
l-265404.html
"Gaspar" <Gaspar@.Gaspar.com> wrote in message
news:uOX2SbJaGHA.3612@.TK2MSFTNGP03.phx.gbl...
>I backup an SQL Server 2000 database (MY_DATABASE) and restore it in
>SQLServer 2005.
> Then, when I try to access its properties I get:
> Property IsPrimaryFile is not available for DataFile '[MY_DATABASE]'.
This
> property may not exist for this object, or may not be retrievable due to
> insufficient access rights. (Microsoft.SqlServer.Smo)
> - I'm using a windows 2003 administrator account
> - I tried setting compatibility level to 90 but it didn't help.
> - If I connect with a sql-level user (not windows 2003 login) a can view
> the properties, but I can't change anything.
> Any ideas?
> Thanks!
>
SQLServer 2005.
Then, when I try to access its properties I get:
Property IsPrimaryFile is not available for DataFile '[MY_DATABASE]'. Th
is
property may not exist for this object, or may not be retrievable due to
insufficient access rights. (Microsoft.SqlServer.Smo)
- I'm using a windows 2003 administrator account
- I tried setting compatibility level to 90 but it didn't help.
- If I connect with a sql-level user (not windows 2003 login) a can view the
properties, but I can't change anything.
Any ideas?
Thanks!http://www.dbtalk.net/microsoft-pub...
l-265404.html
"Gaspar" <Gaspar@.Gaspar.com> wrote in message
news:uOX2SbJaGHA.3612@.TK2MSFTNGP03.phx.gbl...
>I backup an SQL Server 2000 database (MY_DATABASE) and restore it in
>SQLServer 2005.
> Then, when I try to access its properties I get:
> Property IsPrimaryFile is not available for DataFile '[MY_DATABASE]'.
This
> property may not exist for this object, or may not be retrievable due to
> insufficient access rights. (Microsoft.SqlServer.Smo)
> - I'm using a windows 2003 administrator account
> - I tried setting compatibility level to 90 but it didn't help.
> - If I connect with a sql-level user (not windows 2003 login) a can view
> the properties, but I can't change anything.
> Any ideas?
> Thanks!
>
Property IsLocked is not available for Login '[sa]'
Hi everyone,
I'm at wits-end here and cannot figure out how in the world to show
the properties dialog window for the [sa] account (as well as one
other SQL account) in SQL Server 2005 Standard Edititon. This isn't
happening to all SQL accounts nor is it happening to any Windows
account on the server.
Below is the following error:
TITLE: Microsoft SQL Server Management Studio
--
Cannot show requested dialog.
--
ADDITIONAL INFORMATION:
Cannot show requested dialog. (SqlMgmt)
--
Property IsLocked is not available for Login '[sa]'. This property may
not exist for this object, or may not be retrievable due to
insufficient access rights. (Microsoft.SqlServer.Smo)
For help, click:
http://go.microsoft.com/fwlink?Prod...ed&LinkId=20476
--
BUTTONS:
OK
--
I've browsed the entire interweb (or at least the indexed pages of it
and every newsgroup I can think of) and have come to the conclusion
that this is one of the general errors that SQL 2005 kicks out when
things get good and screwed up.
Here are some futile attempts I've taken to remedy this error:
1) Executed this in a query windows: ALTER LOGIN sa WITH PASSWORD =
'DamnYouStupidError' UNLOCK
2) Verified all databases had a valid account as an owner (all have sa
as an owner)
3) Verfied the sa account did not have rights to an old or nonexistent
database.
4) Verifed SP2 is installed, which it is
5) Pulled out my hair
6) Cussed in public... a lot
7) Posted to the newsgroups
I've basically wasted the better part of two days trying everything
under the sun to fix this, but I feel that I've gotten no where. If
anyone has any suggestions shy of reinstalling SQL Server 2005, I'd
love to hear them.
Thanks,
JohnI have the same problem
Any solution about this?
Thanks
"John" <John.Eisbrener@.gmail.com> escribi en el mensaje
news:1177964038.783366.122620@.q75g2000hsh.googlegroups.com...
> Hi everyone,
> I'm at wits-end here and cannot figure out how in the world to show
> the properties dialog window for the [sa] account (as well as one
> other SQL account) in SQL Server 2005 Standard Edititon. This isn't
> happening to all SQL accounts nor is it happening to any Windows
> account on the server.
> Below is the following error:
>
> TITLE: Microsoft SQL Server Management Studio
> --
> Cannot show requested dialog.
> --
> ADDITIONAL INFORMATION:
> Cannot show requested dialog. (SqlMgmt)
> --
> Property IsLocked is not available for Login '[sa]'. This property may
> not exist for this object, or may not be retrievable due to
> insufficient access rights. (Microsoft.SqlServer.Smo)
> For help, click:
> http://go.microsoft.com/fwlink?Prod...ed&LinkId=20476
> --
> BUTTONS:
> OK
> --
> I've browsed the entire interweb (or at least the indexed pages of it
> and every newsgroup I can think of) and have come to the conclusion
> that this is one of the general errors that SQL 2005 kicks out when
> things get good and screwed up.
> Here are some futile attempts I've taken to remedy this error:
> 1) Executed this in a query windows: ALTER LOGIN sa WITH PASSWORD =
> 'DamnYouStupidError' UNLOCK
> 2) Verified all databases had a valid account as an owner (all have sa
> as an owner)
> 3) Verfied the sa account did not have rights to an old or nonexistent
> database.
> 4) Verifed SP2 is installed, which it is
> 5) Pulled out my hair
> 6) Cussed in public... a lot
> 7) Posted to the newsgroups
> I've basically wasted the better part of two days trying everything
> under the sun to fix this, but I feel that I've gotten no where. If
> anyone has any suggestions shy of reinstalling SQL Server 2005, I'd
> love to hear them.
> Thanks,
> John
>|||What operating system are you using? I'm having the same problem on Vista x6
4.
"John" wrote:
> Hi everyone,
> I'm at wits-end here and cannot figure out how in the world to show
> the properties dialog window for the [sa] account (as well as one
> other SQL account) in SQL Server 2005 Standard Edititon. This isn't
> happening to all SQL accounts nor is it happening to any Windows
> account on the server.
> Below is the following error:
>
> TITLE: Microsoft SQL Server Management Studio
> --
> Cannot show requested dialog.
> --
> ADDITIONAL INFORMATION:
> Cannot show requested dialog. (SqlMgmt)
> --
> Property IsLocked is not available for Login '[sa]'. This property may
> not exist for this object, or may not be retrievable due to
> insufficient access rights. (Microsoft.SqlServer.Smo)
> For help, click:
> http://go.microsoft.com/fwlink?Prod...ed&LinkId=20476
> --
> BUTTONS:
> OK
> --
> I've browsed the entire interweb (or at least the indexed pages of it
> and every newsgroup I can think of) and have come to the conclusion
> that this is one of the general errors that SQL 2005 kicks out when
> things get good and screwed up.
> Here are some futile attempts I've taken to remedy this error:
> 1) Executed this in a query windows: ALTER LOGIN sa WITH PASSWORD =
> 'DamnYouStupidError' UNLOCK
> 2) Verified all databases had a valid account as an owner (all have sa
> as an owner)
> 3) Verfied the sa account did not have rights to an old or nonexistent
> database.
> 4) Verifed SP2 is installed, which it is
> 5) Pulled out my hair
> 6) Cussed in public... a lot
> 7) Posted to the newsgroups
> I've basically wasted the better part of two days trying everything
> under the sun to fix this, but I feel that I've gotten no where. If
> anyone has any suggestions shy of reinstalling SQL Server 2005, I'd
> love to hear them.
> Thanks,
> John
>|||I have Windows 2003 R2 64bits. I use SQL Server 2005 x64 in cluster.
Others problem around this are
Activity Monitor doesn't work. ("Unable to launch activity monitor. You may
not have sufficient permissions")
"Akhiris" <Akhiris@.discussions.microsoft.com> escribi en el mensaje
news:23AB87FD-8F62-4913-9DF6-53E45BCEC20C@.microsoft.com...[vbcol=seagreen]
> What operating system are you using? I'm having the same problem on Vista
> x64.
> "John" wrote:
>|||The only "solution" that I've found is to backup all of your
databases, uninstall SQL and reinstall it. Then restore the databases
and finally as a preventative measure, switch ownership of each
database to the dbo account. I'm still of the believe that there is a
different way to remedy this situation, but I haven't found anything
yet.
John
On May 31, 9:03 am, "Jose Cebrian" <jcebrian2...@.yahoo.es> wrote:
> I have the same problem
> Any solution about this?
> Thanks
> "John" <John.Eisbre...@.gmail.com> escribi=F3 en el mensajenews:1177964038=
.783366.122620@.q75g2000hsh.googlegroups.com...[vbcol=seagreen]
>
>
>
>
>
=3D...[vbcol=seagreen]
>
>
>
>
>
>
I'm at wits-end here and cannot figure out how in the world to show
the properties dialog window for the [sa] account (as well as one
other SQL account) in SQL Server 2005 Standard Edititon. This isn't
happening to all SQL accounts nor is it happening to any Windows
account on the server.
Below is the following error:
TITLE: Microsoft SQL Server Management Studio
--
Cannot show requested dialog.
--
ADDITIONAL INFORMATION:
Cannot show requested dialog. (SqlMgmt)
--
Property IsLocked is not available for Login '[sa]'. This property may
not exist for this object, or may not be retrievable due to
insufficient access rights. (Microsoft.SqlServer.Smo)
For help, click:
http://go.microsoft.com/fwlink?Prod...ed&LinkId=20476
--
BUTTONS:
OK
--
I've browsed the entire interweb (or at least the indexed pages of it
and every newsgroup I can think of) and have come to the conclusion
that this is one of the general errors that SQL 2005 kicks out when
things get good and screwed up.
Here are some futile attempts I've taken to remedy this error:
1) Executed this in a query windows: ALTER LOGIN sa WITH PASSWORD =
'DamnYouStupidError' UNLOCK
2) Verified all databases had a valid account as an owner (all have sa
as an owner)
3) Verfied the sa account did not have rights to an old or nonexistent
database.
4) Verifed SP2 is installed, which it is
5) Pulled out my hair
6) Cussed in public... a lot
7) Posted to the newsgroups
I've basically wasted the better part of two days trying everything
under the sun to fix this, but I feel that I've gotten no where. If
anyone has any suggestions shy of reinstalling SQL Server 2005, I'd
love to hear them.
Thanks,
JohnI have the same problem
Any solution about this?
Thanks
"John" <John.Eisbrener@.gmail.com> escribi en el mensaje
news:1177964038.783366.122620@.q75g2000hsh.googlegroups.com...
> Hi everyone,
> I'm at wits-end here and cannot figure out how in the world to show
> the properties dialog window for the [sa] account (as well as one
> other SQL account) in SQL Server 2005 Standard Edititon. This isn't
> happening to all SQL accounts nor is it happening to any Windows
> account on the server.
> Below is the following error:
>
> TITLE: Microsoft SQL Server Management Studio
> --
> Cannot show requested dialog.
> --
> ADDITIONAL INFORMATION:
> Cannot show requested dialog. (SqlMgmt)
> --
> Property IsLocked is not available for Login '[sa]'. This property may
> not exist for this object, or may not be retrievable due to
> insufficient access rights. (Microsoft.SqlServer.Smo)
> For help, click:
> http://go.microsoft.com/fwlink?Prod...ed&LinkId=20476
> --
> BUTTONS:
> OK
> --
> I've browsed the entire interweb (or at least the indexed pages of it
> and every newsgroup I can think of) and have come to the conclusion
> that this is one of the general errors that SQL 2005 kicks out when
> things get good and screwed up.
> Here are some futile attempts I've taken to remedy this error:
> 1) Executed this in a query windows: ALTER LOGIN sa WITH PASSWORD =
> 'DamnYouStupidError' UNLOCK
> 2) Verified all databases had a valid account as an owner (all have sa
> as an owner)
> 3) Verfied the sa account did not have rights to an old or nonexistent
> database.
> 4) Verifed SP2 is installed, which it is
> 5) Pulled out my hair
> 6) Cussed in public... a lot
> 7) Posted to the newsgroups
> I've basically wasted the better part of two days trying everything
> under the sun to fix this, but I feel that I've gotten no where. If
> anyone has any suggestions shy of reinstalling SQL Server 2005, I'd
> love to hear them.
> Thanks,
> John
>|||What operating system are you using? I'm having the same problem on Vista x6
4.
"John" wrote:
> Hi everyone,
> I'm at wits-end here and cannot figure out how in the world to show
> the properties dialog window for the [sa] account (as well as one
> other SQL account) in SQL Server 2005 Standard Edititon. This isn't
> happening to all SQL accounts nor is it happening to any Windows
> account on the server.
> Below is the following error:
>
> TITLE: Microsoft SQL Server Management Studio
> --
> Cannot show requested dialog.
> --
> ADDITIONAL INFORMATION:
> Cannot show requested dialog. (SqlMgmt)
> --
> Property IsLocked is not available for Login '[sa]'. This property may
> not exist for this object, or may not be retrievable due to
> insufficient access rights. (Microsoft.SqlServer.Smo)
> For help, click:
> http://go.microsoft.com/fwlink?Prod...ed&LinkId=20476
> --
> BUTTONS:
> OK
> --
> I've browsed the entire interweb (or at least the indexed pages of it
> and every newsgroup I can think of) and have come to the conclusion
> that this is one of the general errors that SQL 2005 kicks out when
> things get good and screwed up.
> Here are some futile attempts I've taken to remedy this error:
> 1) Executed this in a query windows: ALTER LOGIN sa WITH PASSWORD =
> 'DamnYouStupidError' UNLOCK
> 2) Verified all databases had a valid account as an owner (all have sa
> as an owner)
> 3) Verfied the sa account did not have rights to an old or nonexistent
> database.
> 4) Verifed SP2 is installed, which it is
> 5) Pulled out my hair
> 6) Cussed in public... a lot
> 7) Posted to the newsgroups
> I've basically wasted the better part of two days trying everything
> under the sun to fix this, but I feel that I've gotten no where. If
> anyone has any suggestions shy of reinstalling SQL Server 2005, I'd
> love to hear them.
> Thanks,
> John
>|||I have Windows 2003 R2 64bits. I use SQL Server 2005 x64 in cluster.
Others problem around this are
Activity Monitor doesn't work. ("Unable to launch activity monitor. You may
not have sufficient permissions")
"Akhiris" <Akhiris@.discussions.microsoft.com> escribi en el mensaje
news:23AB87FD-8F62-4913-9DF6-53E45BCEC20C@.microsoft.com...[vbcol=seagreen]
> What operating system are you using? I'm having the same problem on Vista
> x64.
> "John" wrote:
>|||The only "solution" that I've found is to backup all of your
databases, uninstall SQL and reinstall it. Then restore the databases
and finally as a preventative measure, switch ownership of each
database to the dbo account. I'm still of the believe that there is a
different way to remedy this situation, but I haven't found anything
yet.
John
On May 31, 9:03 am, "Jose Cebrian" <jcebrian2...@.yahoo.es> wrote:
> I have the same problem
> Any solution about this?
> Thanks
> "John" <John.Eisbre...@.gmail.com> escribi=F3 en el mensajenews:1177964038=
.783366.122620@.q75g2000hsh.googlegroups.com...[vbcol=seagreen]
>
>
>
>
>
=3D...[vbcol=seagreen]
>
>
>
>
>
>
Properties window closes abruptly - Flashes on for a second only.
I have a SQL 2000 server, SP3a, on a Windows 2000 server, SP4. When I
try to access the properties window of the server, it just flashes on
the screen for a second, and closes. Other applications with
properties type windows work fine, so it appears to be SQL related.
Any ideas would be greatly appreciated.Hello,
Thanks for your post. According to your description I understand that when
you try to access the properties window of SQL Server, the dialog just
flashes on the screen for a second and closes. This behavior is strange and
I would like you to provide more information so that I can fully understand
the problem.
1. What is the properties window of the SQL Server? Do you mean the
property dialog of SQL Server in Enterprise Manager?
2. Does this problem occur randomly? Can you reproduce this behavior?
3. If so, please describe the reproduce steps in detail so that I can try
to reproduce this behavior on my side.
I am looking forward to hearing from you soon.
Best regards,
Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
try to access the properties window of the server, it just flashes on
the screen for a second, and closes. Other applications with
properties type windows work fine, so it appears to be SQL related.
Any ideas would be greatly appreciated.Hello,
Thanks for your post. According to your description I understand that when
you try to access the properties window of SQL Server, the dialog just
flashes on the screen for a second and closes. This behavior is strange and
I would like you to provide more information so that I can fully understand
the problem.
1. What is the properties window of the SQL Server? Do you mean the
property dialog of SQL Server in Enterprise Manager?
2. Does this problem occur randomly? Can you reproduce this behavior?
3. If so, please describe the reproduce steps in detail so that I can try
to reproduce this behavior on my side.
I am looking forward to hearing from you soon.
Best regards,
Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Properties window closes abruptly - Flashes on for a second only.
I have a SQL 2000 server, SP3a, on a Windows 2000 server, SP4. When I
try to access the properties window of the server, it just flashes on
the screen for a second, and closes. Other applications with
properties type windows work fine, so it appears to be SQL related.
Any ideas would be greatly appreciated.Hello,
Thanks for your post. According to your description I understand that when
you try to access the properties window of SQL Server, the dialog just
flashes on the screen for a second and closes. This behavior is strange and
I would like you to provide more information so that I can fully understand
the problem.
1. What is the properties window of the SQL Server? Do you mean the
property dialog of SQL Server in Enterprise Manager?
2. Does this problem occur randomly? Can you reproduce this behavior?
3. If so, please describe the reproduce steps in detail so that I can try
to reproduce this behavior on my side.
I am looking forward to hearing from you soon.
Best regards,
Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
try to access the properties window of the server, it just flashes on
the screen for a second, and closes. Other applications with
properties type windows work fine, so it appears to be SQL related.
Any ideas would be greatly appreciated.Hello,
Thanks for your post. According to your description I understand that when
you try to access the properties window of SQL Server, the dialog just
flashes on the screen for a second and closes. This behavior is strange and
I would like you to provide more information so that I can fully understand
the problem.
1. What is the properties window of the SQL Server? Do you mean the
property dialog of SQL Server in Enterprise Manager?
2. Does this problem occur randomly? Can you reproduce this behavior?
3. If so, please describe the reproduce steps in detail so that I can try
to reproduce this behavior on my side.
I am looking forward to hearing from you soon.
Best regards,
Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Properties Pane Help (was Re: Many to Many Relationships ... AS200
Thanks a lot.
A last question (honest!) - Is there anywhere I can get the documentation on
what all of the properties in the properties pane do? At the moment hitting
F1 just tells me how to set the associated property in C# but not what the
purpose of the property is. I wonder if there are some features I'm missing
or some understanding I don't quite have because there are properties I don'
t
fully understand.As we get closer to RTM books-online will be providing more and more
information about the various properties.
--
Dave Wickert [MSFT]
dwickert@.online.microsoft.com
Program Manager
BI SystemsTeam
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Richard Corfield" <RichardCorfield@.discussions.microsoft.com> wrote in
message news:C4782D0F-58AD-4C3B-8A56-A05EB7614919@.microsoft.com...
> Thanks a lot.
> A last question (honest!) - Is there anywhere I can get the documentation
on
> what all of the properties in the properties pane do? At the moment
hitting
> F1 just tells me how to set the associated property in C# but not what the
> purpose of the property is. I wonder if there are some features I'm
missing
> or some understanding I don't quite have because there are properties I
don't
> fully understand.
A last question (honest!) - Is there anywhere I can get the documentation on
what all of the properties in the properties pane do? At the moment hitting
F1 just tells me how to set the associated property in C# but not what the
purpose of the property is. I wonder if there are some features I'm missing
or some understanding I don't quite have because there are properties I don'
t
fully understand.As we get closer to RTM books-online will be providing more and more
information about the various properties.
--
Dave Wickert [MSFT]
dwickert@.online.microsoft.com
Program Manager
BI SystemsTeam
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Richard Corfield" <RichardCorfield@.discussions.microsoft.com> wrote in
message news:C4782D0F-58AD-4C3B-8A56-A05EB7614919@.microsoft.com...
> Thanks a lot.
> A last question (honest!) - Is there anywhere I can get the documentation
on
> what all of the properties in the properties pane do? At the moment
hitting
> F1 just tells me how to set the associated property in C# but not what the
> purpose of the property is. I wonder if there are some features I'm
missing
> or some understanding I don't quite have because there are properties I
don't
> fully understand.
properties owner and users owner.
In the properties section of a database there is a owner.
Under the users of a database there is the dbo with
a Login Name.
What is the difference between the 'two owners' ?
ben brugmanHi,
"Both can be same in most of the situation."
DBO - DBO is a role, A user with a DBO role can do any activities inside
the database.
Properties section of a database there is a owner?
He will be person who creates the database. By default he will a DBO. This
owner can be changed using the procedure,
sp_changedbowner.
Thanks
Hari
MCDBA
"ben brugman" <ben@.niethier.nl> wrote in message
news:eCuSx$chEHA.4064@.TK2MSFTNGP12.phx.gbl...
> In the properties section of a database there is a owner.
> Under the users of a database there is the dbo with
> a Login Name.
> What is the difference between the 'two owners' ?
> ben brugman
>|||Thanks for your time and quick response,
see inline :
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:O2$NJIdhEHA.2052@.tk2msftngp13.phx.gbl...
> Hi,
> "Both can be same in most of the situation."
I tried to make both the same.
> DBO - DBO is a role, A user with a DBO role can do any activities inside
> the database.
> Properties section of a database there is a owner?
> He will be person who creates the database. By default he will a DBO. This
> owner can be changed using the procedure,
> sp_changedbowner.
I cannot change the owner because :
"
Server: Msg 15110, Level 16, State 1, Procedure sp_changedbowner, Line 46
The proposed new database owner is already a user in the database.
"
And in the database he is the dbo owner, so I do not think deleting that
owner
is wise.
I still have difficulty grasping the difference between the two owners and
still would like them to be the same.
Thanks
ben brugman
> Thanks
> Hari
> MCDBA
>
>
> "ben brugman" <ben@.niethier.nl> wrote in message
> news:eCuSx$chEHA.4064@.TK2MSFTNGP12.phx.gbl...
>|||Hari
DBO is a privileged user.
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:O2$NJIdhEHA.2052@.tk2msftngp13.phx.gbl...
> Hi,
> "Both can be same in most of the situation."
> DBO - DBO is a role, A user with a DBO role can do any activities inside
> the database.
> Properties section of a database there is a owner?
> He will be person who creates the database. By default he will a DBO. This
> owner can be changed using the procedure,
> sp_changedbowner.
> Thanks
> Hari
> MCDBA
>
>
> "ben brugman" <ben@.niethier.nl> wrote in message
> news:eCuSx$chEHA.4064@.TK2MSFTNGP12.phx.gbl...
>|||'dbo' is a special database user and must exist in every database. The
database owner is the *login* that is mapped to the database 'dbo' user and
this mapping is stored in 2 places, sysdatabases and sysusers. These should
normally be the same login but can get out-of-sync in some situations, such
as a restore or attach. The query below will return the same login if the
owner entries are synchronized:
USE MyDatabase
SELECT 'sysdatabases mapping=' + SUSER_SNAME(sid)
FROM master..sysdatabases
WHERE name = DB_NAME()
UNION ALL
SELECT 'sysusers mapping=' + SUSER_SNAME(sid)
FROM sysusers
WHERE name = 'dbo'
You can execute sp_changedbowner to change or correct the mapping. If you
get error 15110, ensure the specified login is not already a database user
since a login can be mapped to only one database user at a time.
The 15110 error can also be raised due to an out-of-sync condition mentioned
above. In that case, temporarily change database ownership to a
non-conflicting login and then to the desired login like the example below:
USE MyDatabase
EXEC sp_addlogin 'TempOwner'
EXEC sp_changedbowner 'TempOwner'
EXEC sp_changedbowner 'MyDatabaseOwner'
EXEC sp_droplogin 'TempOwner'
GO
Hope this helps.
Dan Guzman
SQL Server MVP
"ben brugman" <ben@.niethier.nl> wrote in message
news:%23nqiINdhEHA.3076@.tk2msftngp13.phx.gbl...
> Thanks for your time and quick response,
> see inline :
> "Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
> news:O2$NJIdhEHA.2052@.tk2msftngp13.phx.gbl...
> I tried to make both the same.
>
inside[vbcol=seagreen]
This[vbcol=seagreen]
> I cannot change the owner because :
> "
> Server: Msg 15110, Level 16, State 1, Procedure sp_changedbowner, Line 46
> The proposed new database owner is already a user in the database.
> "
> And in the database he is the dbo owner, so I do not think deleting that
> owner
> is wise.
> I still have difficulty grasping the difference between the two owners and
> still would like them to be the same.
> Thanks
> ben brugman
>
>sql
Under the users of a database there is the dbo with
a Login Name.
What is the difference between the 'two owners' ?
ben brugmanHi,
"Both can be same in most of the situation."
DBO - DBO is a role, A user with a DBO role can do any activities inside
the database.
Properties section of a database there is a owner?
He will be person who creates the database. By default he will a DBO. This
owner can be changed using the procedure,
sp_changedbowner.
Thanks
Hari
MCDBA
"ben brugman" <ben@.niethier.nl> wrote in message
news:eCuSx$chEHA.4064@.TK2MSFTNGP12.phx.gbl...
> In the properties section of a database there is a owner.
> Under the users of a database there is the dbo with
> a Login Name.
> What is the difference between the 'two owners' ?
> ben brugman
>|||Thanks for your time and quick response,
see inline :
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:O2$NJIdhEHA.2052@.tk2msftngp13.phx.gbl...
> Hi,
> "Both can be same in most of the situation."
I tried to make both the same.
> DBO - DBO is a role, A user with a DBO role can do any activities inside
> the database.
> Properties section of a database there is a owner?
> He will be person who creates the database. By default he will a DBO. This
> owner can be changed using the procedure,
> sp_changedbowner.
I cannot change the owner because :
"
Server: Msg 15110, Level 16, State 1, Procedure sp_changedbowner, Line 46
The proposed new database owner is already a user in the database.
"
And in the database he is the dbo owner, so I do not think deleting that
owner
is wise.
I still have difficulty grasping the difference between the two owners and
still would like them to be the same.
Thanks
ben brugman
> Thanks
> Hari
> MCDBA
>
>
> "ben brugman" <ben@.niethier.nl> wrote in message
> news:eCuSx$chEHA.4064@.TK2MSFTNGP12.phx.gbl...
>|||Hari
DBO is a privileged user.
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:O2$NJIdhEHA.2052@.tk2msftngp13.phx.gbl...
> Hi,
> "Both can be same in most of the situation."
> DBO - DBO is a role, A user with a DBO role can do any activities inside
> the database.
> Properties section of a database there is a owner?
> He will be person who creates the database. By default he will a DBO. This
> owner can be changed using the procedure,
> sp_changedbowner.
> Thanks
> Hari
> MCDBA
>
>
> "ben brugman" <ben@.niethier.nl> wrote in message
> news:eCuSx$chEHA.4064@.TK2MSFTNGP12.phx.gbl...
>|||'dbo' is a special database user and must exist in every database. The
database owner is the *login* that is mapped to the database 'dbo' user and
this mapping is stored in 2 places, sysdatabases and sysusers. These should
normally be the same login but can get out-of-sync in some situations, such
as a restore or attach. The query below will return the same login if the
owner entries are synchronized:
USE MyDatabase
SELECT 'sysdatabases mapping=' + SUSER_SNAME(sid)
FROM master..sysdatabases
WHERE name = DB_NAME()
UNION ALL
SELECT 'sysusers mapping=' + SUSER_SNAME(sid)
FROM sysusers
WHERE name = 'dbo'
You can execute sp_changedbowner to change or correct the mapping. If you
get error 15110, ensure the specified login is not already a database user
since a login can be mapped to only one database user at a time.
The 15110 error can also be raised due to an out-of-sync condition mentioned
above. In that case, temporarily change database ownership to a
non-conflicting login and then to the desired login like the example below:
USE MyDatabase
EXEC sp_addlogin 'TempOwner'
EXEC sp_changedbowner 'TempOwner'
EXEC sp_changedbowner 'MyDatabaseOwner'
EXEC sp_droplogin 'TempOwner'
GO
Hope this helps.
Dan Guzman
SQL Server MVP
"ben brugman" <ben@.niethier.nl> wrote in message
news:%23nqiINdhEHA.3076@.tk2msftngp13.phx.gbl...
> Thanks for your time and quick response,
> see inline :
> "Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
> news:O2$NJIdhEHA.2052@.tk2msftngp13.phx.gbl...
> I tried to make both the same.
>
inside[vbcol=seagreen]
This[vbcol=seagreen]
> I cannot change the owner because :
> "
> Server: Msg 15110, Level 16, State 1, Procedure sp_changedbowner, Line 46
> The proposed new database owner is already a user in the database.
> "
> And in the database he is the dbo owner, so I do not think deleting that
> owner
> is wise.
> I still have difficulty grasping the difference between the two owners and
> still would like them to be the same.
> Thanks
> ben brugman
>
>sql
properties owner and users owner.
In the properties section of a database there is a owner.
Under the users of a database there is the dbo with
a Login Name.
What is the difference between the 'two owners' ?
ben brugmanHi,
"Both can be same in most of the situation."
DBO - DBO is a role, A user with a DBO role can do any activities inside
the database.
Properties section of a database there is a owner?
He will be person who creates the database. By default he will a DBO. This
owner can be changed using the procedure,
sp_changedbowner.
Thanks
Hari
MCDBA
"ben brugman" <ben@.niethier.nl> wrote in message
news:eCuSx$chEHA.4064@.TK2MSFTNGP12.phx.gbl...
> In the properties section of a database there is a owner.
> Under the users of a database there is the dbo with
> a Login Name.
> What is the difference between the 'two owners' ?
> ben brugman
>|||Hari
DBO is a privileged user.
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:O2$NJIdhEHA.2052@.tk2msftngp13.phx.gbl...
> Hi,
> "Both can be same in most of the situation."
> DBO - DBO is a role, A user with a DBO role can do any activities inside
> the database.
> Properties section of a database there is a owner?
> He will be person who creates the database. By default he will a DBO. This
> owner can be changed using the procedure,
> sp_changedbowner.
> Thanks
> Hari
> MCDBA
>
>
> "ben brugman" <ben@.niethier.nl> wrote in message
> news:eCuSx$chEHA.4064@.TK2MSFTNGP12.phx.gbl...
> > In the properties section of a database there is a owner.
> >
> > Under the users of a database there is the dbo with
> > a Login Name.
> >
> > What is the difference between the 'two owners' ?
> >
> > ben brugman
> >
> >
>|||Thanks for your time and quick response,
see inline :
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:O2$NJIdhEHA.2052@.tk2msftngp13.phx.gbl...
> Hi,
> "Both can be same in most of the situation."
I tried to make both the same.
> DBO - DBO is a role, A user with a DBO role can do any activities inside
> the database.
> Properties section of a database there is a owner?
> He will be person who creates the database. By default he will a DBO. This
> owner can be changed using the procedure,
> sp_changedbowner.
I cannot change the owner because :
"
Server: Msg 15110, Level 16, State 1, Procedure sp_changedbowner, Line 46
The proposed new database owner is already a user in the database.
"
And in the database he is the dbo owner, so I do not think deleting that
owner
is wise.
I still have difficulty grasping the difference between the two owners and
still would like them to be the same.
Thanks
ben brugman
> Thanks
> Hari
> MCDBA
>
>
> "ben brugman" <ben@.niethier.nl> wrote in message
> news:eCuSx$chEHA.4064@.TK2MSFTNGP12.phx.gbl...
> > In the properties section of a database there is a owner.
> >
> > Under the users of a database there is the dbo with
> > a Login Name.
> >
> > What is the difference between the 'two owners' ?
> >
> > ben brugman
> >
> >
>|||'dbo' is a special database user and must exist in every database. The
database owner is the *login* that is mapped to the database 'dbo' user and
this mapping is stored in 2 places, sysdatabases and sysusers. These should
normally be the same login but can get out-of-sync in some situations, such
as a restore or attach. The query below will return the same login if the
owner entries are synchronized:
USE MyDatabase
SELECT 'sysdatabases mapping=' + SUSER_SNAME(sid)
FROM master..sysdatabases
WHERE name = DB_NAME()
UNION ALL
SELECT 'sysusers mapping=' + SUSER_SNAME(sid)
FROM sysusers
WHERE name = 'dbo'
You can execute sp_changedbowner to change or correct the mapping. If you
get error 15110, ensure the specified login is not already a database user
since a login can be mapped to only one database user at a time.
The 15110 error can also be raised due to an out-of-sync condition mentioned
above. In that case, temporarily change database ownership to a
non-conflicting login and then to the desired login like the example below:
USE MyDatabase
EXEC sp_addlogin 'TempOwner'
EXEC sp_changedbowner 'TempOwner'
EXEC sp_changedbowner 'MyDatabaseOwner'
EXEC sp_droplogin 'TempOwner'
GO
--
Hope this helps.
Dan Guzman
SQL Server MVP
"ben brugman" <ben@.niethier.nl> wrote in message
news:%23nqiINdhEHA.3076@.tk2msftngp13.phx.gbl...
> Thanks for your time and quick response,
> see inline :
> "Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
> news:O2$NJIdhEHA.2052@.tk2msftngp13.phx.gbl...
> > Hi,
> >
> > "Both can be same in most of the situation."
> I tried to make both the same.
> >
> > DBO - DBO is a role, A user with a DBO role can do any activities
inside
> > the database.
> >
> > Properties section of a database there is a owner?
> >
> > He will be person who creates the database. By default he will a DBO.
This
> > owner can be changed using the procedure,
> >
> > sp_changedbowner.
> I cannot change the owner because :
> "
> Server: Msg 15110, Level 16, State 1, Procedure sp_changedbowner, Line 46
> The proposed new database owner is already a user in the database.
> "
> And in the database he is the dbo owner, so I do not think deleting that
> owner
> is wise.
> I still have difficulty grasping the difference between the two owners and
> still would like them to be the same.
> Thanks
> ben brugman
> >
> > Thanks
> > Hari
> > MCDBA
> >
> >
> >
> >
> > "ben brugman" <ben@.niethier.nl> wrote in message
> > news:eCuSx$chEHA.4064@.TK2MSFTNGP12.phx.gbl...
> > > In the properties section of a database there is a owner.
> > >
> > > Under the users of a database there is the dbo with
> > > a Login Name.
> > >
> > > What is the difference between the 'two owners' ?
> > >
> > > ben brugman
> > >
> > >
> >
> >
>
Under the users of a database there is the dbo with
a Login Name.
What is the difference between the 'two owners' ?
ben brugmanHi,
"Both can be same in most of the situation."
DBO - DBO is a role, A user with a DBO role can do any activities inside
the database.
Properties section of a database there is a owner?
He will be person who creates the database. By default he will a DBO. This
owner can be changed using the procedure,
sp_changedbowner.
Thanks
Hari
MCDBA
"ben brugman" <ben@.niethier.nl> wrote in message
news:eCuSx$chEHA.4064@.TK2MSFTNGP12.phx.gbl...
> In the properties section of a database there is a owner.
> Under the users of a database there is the dbo with
> a Login Name.
> What is the difference between the 'two owners' ?
> ben brugman
>|||Hari
DBO is a privileged user.
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:O2$NJIdhEHA.2052@.tk2msftngp13.phx.gbl...
> Hi,
> "Both can be same in most of the situation."
> DBO - DBO is a role, A user with a DBO role can do any activities inside
> the database.
> Properties section of a database there is a owner?
> He will be person who creates the database. By default he will a DBO. This
> owner can be changed using the procedure,
> sp_changedbowner.
> Thanks
> Hari
> MCDBA
>
>
> "ben brugman" <ben@.niethier.nl> wrote in message
> news:eCuSx$chEHA.4064@.TK2MSFTNGP12.phx.gbl...
> > In the properties section of a database there is a owner.
> >
> > Under the users of a database there is the dbo with
> > a Login Name.
> >
> > What is the difference between the 'two owners' ?
> >
> > ben brugman
> >
> >
>|||Thanks for your time and quick response,
see inline :
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:O2$NJIdhEHA.2052@.tk2msftngp13.phx.gbl...
> Hi,
> "Both can be same in most of the situation."
I tried to make both the same.
> DBO - DBO is a role, A user with a DBO role can do any activities inside
> the database.
> Properties section of a database there is a owner?
> He will be person who creates the database. By default he will a DBO. This
> owner can be changed using the procedure,
> sp_changedbowner.
I cannot change the owner because :
"
Server: Msg 15110, Level 16, State 1, Procedure sp_changedbowner, Line 46
The proposed new database owner is already a user in the database.
"
And in the database he is the dbo owner, so I do not think deleting that
owner
is wise.
I still have difficulty grasping the difference between the two owners and
still would like them to be the same.
Thanks
ben brugman
> Thanks
> Hari
> MCDBA
>
>
> "ben brugman" <ben@.niethier.nl> wrote in message
> news:eCuSx$chEHA.4064@.TK2MSFTNGP12.phx.gbl...
> > In the properties section of a database there is a owner.
> >
> > Under the users of a database there is the dbo with
> > a Login Name.
> >
> > What is the difference between the 'two owners' ?
> >
> > ben brugman
> >
> >
>|||'dbo' is a special database user and must exist in every database. The
database owner is the *login* that is mapped to the database 'dbo' user and
this mapping is stored in 2 places, sysdatabases and sysusers. These should
normally be the same login but can get out-of-sync in some situations, such
as a restore or attach. The query below will return the same login if the
owner entries are synchronized:
USE MyDatabase
SELECT 'sysdatabases mapping=' + SUSER_SNAME(sid)
FROM master..sysdatabases
WHERE name = DB_NAME()
UNION ALL
SELECT 'sysusers mapping=' + SUSER_SNAME(sid)
FROM sysusers
WHERE name = 'dbo'
You can execute sp_changedbowner to change or correct the mapping. If you
get error 15110, ensure the specified login is not already a database user
since a login can be mapped to only one database user at a time.
The 15110 error can also be raised due to an out-of-sync condition mentioned
above. In that case, temporarily change database ownership to a
non-conflicting login and then to the desired login like the example below:
USE MyDatabase
EXEC sp_addlogin 'TempOwner'
EXEC sp_changedbowner 'TempOwner'
EXEC sp_changedbowner 'MyDatabaseOwner'
EXEC sp_droplogin 'TempOwner'
GO
--
Hope this helps.
Dan Guzman
SQL Server MVP
"ben brugman" <ben@.niethier.nl> wrote in message
news:%23nqiINdhEHA.3076@.tk2msftngp13.phx.gbl...
> Thanks for your time and quick response,
> see inline :
> "Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
> news:O2$NJIdhEHA.2052@.tk2msftngp13.phx.gbl...
> > Hi,
> >
> > "Both can be same in most of the situation."
> I tried to make both the same.
> >
> > DBO - DBO is a role, A user with a DBO role can do any activities
inside
> > the database.
> >
> > Properties section of a database there is a owner?
> >
> > He will be person who creates the database. By default he will a DBO.
This
> > owner can be changed using the procedure,
> >
> > sp_changedbowner.
> I cannot change the owner because :
> "
> Server: Msg 15110, Level 16, State 1, Procedure sp_changedbowner, Line 46
> The proposed new database owner is already a user in the database.
> "
> And in the database he is the dbo owner, so I do not think deleting that
> owner
> is wise.
> I still have difficulty grasping the difference between the two owners and
> still would like them to be the same.
> Thanks
> ben brugman
> >
> > Thanks
> > Hari
> > MCDBA
> >
> >
> >
> >
> > "ben brugman" <ben@.niethier.nl> wrote in message
> > news:eCuSx$chEHA.4064@.TK2MSFTNGP12.phx.gbl...
> > > In the properties section of a database there is a owner.
> > >
> > > Under the users of a database there is the dbo with
> > > a Login Name.
> > >
> > > What is the difference between the 'two owners' ?
> > >
> > > ben brugman
> > >
> > >
> >
> >
>
properties owner and users owner.
In the properties section of a database there is a owner.
Under the users of a database there is the dbo with
a Login Name.
What is the difference between the 'two owners' ?
ben brugman
Hi,
"Both can be same in most of the situation."
DBO - DBO is a role, A user with a DBO role can do any activities inside
the database.
Properties section of a database there is a owner?
He will be person who creates the database. By default he will a DBO. This
owner can be changed using the procedure,
sp_changedbowner.
Thanks
Hari
MCDBA
"ben brugman" <ben@.niethier.nl> wrote in message
news:eCuSx$chEHA.4064@.TK2MSFTNGP12.phx.gbl...
> In the properties section of a database there is a owner.
> Under the users of a database there is the dbo with
> a Login Name.
> What is the difference between the 'two owners' ?
> ben brugman
>
|||Thanks for your time and quick response,
see inline :
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:O2$NJIdhEHA.2052@.tk2msftngp13.phx.gbl...
> Hi,
> "Both can be same in most of the situation."
I tried to make both the same.
> DBO - DBO is a role, A user with a DBO role can do any activities inside
> the database.
> Properties section of a database there is a owner?
> He will be person who creates the database. By default he will a DBO. This
> owner can be changed using the procedure,
> sp_changedbowner.
I cannot change the owner because :
"
Server: Msg 15110, Level 16, State 1, Procedure sp_changedbowner, Line 46
The proposed new database owner is already a user in the database.
"
And in the database he is the dbo owner, so I do not think deleting that
owner
is wise.
I still have difficulty grasping the difference between the two owners and
still would like them to be the same.
Thanks
ben brugman
> Thanks
> Hari
> MCDBA
>
>
> "ben brugman" <ben@.niethier.nl> wrote in message
> news:eCuSx$chEHA.4064@.TK2MSFTNGP12.phx.gbl...
>
|||Hari
DBO is a privileged user.
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:O2$NJIdhEHA.2052@.tk2msftngp13.phx.gbl...
> Hi,
> "Both can be same in most of the situation."
> DBO - DBO is a role, A user with a DBO role can do any activities inside
> the database.
> Properties section of a database there is a owner?
> He will be person who creates the database. By default he will a DBO. This
> owner can be changed using the procedure,
> sp_changedbowner.
> Thanks
> Hari
> MCDBA
>
>
> "ben brugman" <ben@.niethier.nl> wrote in message
> news:eCuSx$chEHA.4064@.TK2MSFTNGP12.phx.gbl...
>
|||'dbo' is a special database user and must exist in every database. The
database owner is the *login* that is mapped to the database 'dbo' user and
this mapping is stored in 2 places, sysdatabases and sysusers. These should
normally be the same login but can get out-of-sync in some situations, such
as a restore or attach. The query below will return the same login if the
owner entries are synchronized:
USE MyDatabase
SELECT 'sysdatabases mapping=' + SUSER_SNAME(sid)
FROM master..sysdatabases
WHERE name = DB_NAME()
UNION ALL
SELECT 'sysusers mapping=' + SUSER_SNAME(sid)
FROM sysusers
WHERE name = 'dbo'
You can execute sp_changedbowner to change or correct the mapping. If you
get error 15110, ensure the specified login is not already a database user
since a login can be mapped to only one database user at a time.
The 15110 error can also be raised due to an out-of-sync condition mentioned
above. In that case, temporarily change database ownership to a
non-conflicting login and then to the desired login like the example below:
USE MyDatabase
EXEC sp_addlogin 'TempOwner'
EXEC sp_changedbowner 'TempOwner'
EXEC sp_changedbowner 'MyDatabaseOwner'
EXEC sp_droplogin 'TempOwner'
GO
Hope this helps.
Dan Guzman
SQL Server MVP
"ben brugman" <ben@.niethier.nl> wrote in message
news:%23nqiINdhEHA.3076@.tk2msftngp13.phx.gbl...[vbcol=seagreen]
> Thanks for your time and quick response,
> see inline :
> "Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
> news:O2$NJIdhEHA.2052@.tk2msftngp13.phx.gbl...
> I tried to make both the same.
inside[vbcol=seagreen]
This
> I cannot change the owner because :
> "
> Server: Msg 15110, Level 16, State 1, Procedure sp_changedbowner, Line 46
> The proposed new database owner is already a user in the database.
> "
> And in the database he is the dbo owner, so I do not think deleting that
> owner
> is wise.
> I still have difficulty grasping the difference between the two owners and
> still would like them to be the same.
> Thanks
> ben brugman
>
>
Under the users of a database there is the dbo with
a Login Name.
What is the difference between the 'two owners' ?
ben brugman
Hi,
"Both can be same in most of the situation."
DBO - DBO is a role, A user with a DBO role can do any activities inside
the database.
Properties section of a database there is a owner?
He will be person who creates the database. By default he will a DBO. This
owner can be changed using the procedure,
sp_changedbowner.
Thanks
Hari
MCDBA
"ben brugman" <ben@.niethier.nl> wrote in message
news:eCuSx$chEHA.4064@.TK2MSFTNGP12.phx.gbl...
> In the properties section of a database there is a owner.
> Under the users of a database there is the dbo with
> a Login Name.
> What is the difference between the 'two owners' ?
> ben brugman
>
|||Thanks for your time and quick response,
see inline :
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:O2$NJIdhEHA.2052@.tk2msftngp13.phx.gbl...
> Hi,
> "Both can be same in most of the situation."
I tried to make both the same.
> DBO - DBO is a role, A user with a DBO role can do any activities inside
> the database.
> Properties section of a database there is a owner?
> He will be person who creates the database. By default he will a DBO. This
> owner can be changed using the procedure,
> sp_changedbowner.
I cannot change the owner because :
"
Server: Msg 15110, Level 16, State 1, Procedure sp_changedbowner, Line 46
The proposed new database owner is already a user in the database.
"
And in the database he is the dbo owner, so I do not think deleting that
owner
is wise.
I still have difficulty grasping the difference between the two owners and
still would like them to be the same.
Thanks
ben brugman
> Thanks
> Hari
> MCDBA
>
>
> "ben brugman" <ben@.niethier.nl> wrote in message
> news:eCuSx$chEHA.4064@.TK2MSFTNGP12.phx.gbl...
>
|||Hari
DBO is a privileged user.
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:O2$NJIdhEHA.2052@.tk2msftngp13.phx.gbl...
> Hi,
> "Both can be same in most of the situation."
> DBO - DBO is a role, A user with a DBO role can do any activities inside
> the database.
> Properties section of a database there is a owner?
> He will be person who creates the database. By default he will a DBO. This
> owner can be changed using the procedure,
> sp_changedbowner.
> Thanks
> Hari
> MCDBA
>
>
> "ben brugman" <ben@.niethier.nl> wrote in message
> news:eCuSx$chEHA.4064@.TK2MSFTNGP12.phx.gbl...
>
|||'dbo' is a special database user and must exist in every database. The
database owner is the *login* that is mapped to the database 'dbo' user and
this mapping is stored in 2 places, sysdatabases and sysusers. These should
normally be the same login but can get out-of-sync in some situations, such
as a restore or attach. The query below will return the same login if the
owner entries are synchronized:
USE MyDatabase
SELECT 'sysdatabases mapping=' + SUSER_SNAME(sid)
FROM master..sysdatabases
WHERE name = DB_NAME()
UNION ALL
SELECT 'sysusers mapping=' + SUSER_SNAME(sid)
FROM sysusers
WHERE name = 'dbo'
You can execute sp_changedbowner to change or correct the mapping. If you
get error 15110, ensure the specified login is not already a database user
since a login can be mapped to only one database user at a time.
The 15110 error can also be raised due to an out-of-sync condition mentioned
above. In that case, temporarily change database ownership to a
non-conflicting login and then to the desired login like the example below:
USE MyDatabase
EXEC sp_addlogin 'TempOwner'
EXEC sp_changedbowner 'TempOwner'
EXEC sp_changedbowner 'MyDatabaseOwner'
EXEC sp_droplogin 'TempOwner'
GO
Hope this helps.
Dan Guzman
SQL Server MVP
"ben brugman" <ben@.niethier.nl> wrote in message
news:%23nqiINdhEHA.3076@.tk2msftngp13.phx.gbl...[vbcol=seagreen]
> Thanks for your time and quick response,
> see inline :
> "Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
> news:O2$NJIdhEHA.2052@.tk2msftngp13.phx.gbl...
> I tried to make both the same.
inside[vbcol=seagreen]
This
> I cannot change the owner because :
> "
> Server: Msg 15110, Level 16, State 1, Procedure sp_changedbowner, Line 46
> The proposed new database owner is already a user in the database.
> "
> And in the database he is the dbo owner, so I do not think deleting that
> owner
> is wise.
> I still have difficulty grasping the difference between the two owners and
> still would like them to be the same.
> Thanks
> ben brugman
>
>
Monday, March 26, 2012
properties on stored procedure
Hey
I have a problem viewing properties on my stored procudures, when i right click there is no properties button like in the other versions, is that a bug ?
hi,
if you mean "extended properties" of a specified object, you can access them right clicking the relative object in SQL Server Management Studio (or SQL Server Management Studio Express) and accessing the last "tab" (Extended Properties tab.. 
regards
Properties List
Where can I get a list of all the properties for a control such as a textbox?The RDL documentation lists all properties for all controls. From
programming standpoint, the only Textbox property exposed to you is the
Value property.
--
HTH,
---
Teo Lachev, MVP, MCSD, MCT
"Microsoft Reporting Services in Action"
"Applied Microsoft Analysis Services 2005"
Home page and blog: http://www.prologika.com/
---
"David" <David@.discussions.microsoft.com> wrote in message
news:F033C6DF-06FF-423B-8F5C-DB99E00BD085@.microsoft.com...
> Where can I get a list of all the properties for a control such as a
> textbox?
programming standpoint, the only Textbox property exposed to you is the
Value property.
--
HTH,
---
Teo Lachev, MVP, MCSD, MCT
"Microsoft Reporting Services in Action"
"Applied Microsoft Analysis Services 2005"
Home page and blog: http://www.prologika.com/
---
"David" <David@.discussions.microsoft.com> wrote in message
news:F033C6DF-06FF-423B-8F5C-DB99E00BD085@.microsoft.com...
> Where can I get a list of all the properties for a control such as a
> textbox?
Properties in many reports
I have many reports in a project and I want to set some of the properties in
one place and have all of the reports read from it. Properties like page
size, margins, font size, etc.
Is that possible?Create a standard template and copy it at ProjectItems\ReportProject search
for this directory default should be where your projects are stored. Once you
copy any one creating a report will select the template. So we can maintain a
standard.
Amarnath
"David" wrote:
> I have many reports in a project and I want to set some of the properties in
> one place and have all of the reports read from it. Properties like page
> size, margins, font size, etc.
> Is that possible?
>|||You can store these values in a table you reference via a dataset and then
use an expression to set the format values from the fields in the dataset.
Using parameters for the reportname and the user, you could allow users to
personalize individual reports.
"David" wrote:
> I have many reports in a project and I want to set some of the properties in
> one place and have all of the reports read from it. Properties like page
> size, margins, font size, etc.
> Is that possible?
>sql
one place and have all of the reports read from it. Properties like page
size, margins, font size, etc.
Is that possible?Create a standard template and copy it at ProjectItems\ReportProject search
for this directory default should be where your projects are stored. Once you
copy any one creating a report will select the template. So we can maintain a
standard.
Amarnath
"David" wrote:
> I have many reports in a project and I want to set some of the properties in
> one place and have all of the reports read from it. Properties like page
> size, margins, font size, etc.
> Is that possible?
>|||You can store these values in a table you reference via a dataset and then
use an expression to set the format values from the fields in the dataset.
Using parameters for the reportname and the user, you could allow users to
personalize individual reports.
"David" wrote:
> I have many reports in a project and I want to set some of the properties in
> one place and have all of the reports read from it. Properties like page
> size, margins, font size, etc.
> Is that possible?
>sql
Properties Expressions
I can create an expression for the visibility property as follows:
=iif(countDistinct(Fields!RefNbr.Value)=1,True,False)
BUT when I try to do something similar for the fontweight property like
=iif( Fields!Carryover.Value = 2 ,Heavy,Normal) I get the following error message
Name Heavy is not declared
'Try: =iif( Fields!Carryover.Value = 2 ,"Heavy","Normal")
-Lukasz
This posting is provided "AS IS" with no warranties, and confers no rights.
"Mardy" <Mardy@.discussions.microsoft.com> wrote in message
news:E4B78AB2-9D82-4B14-9A0A-2FFD4D41359D@.microsoft.com...
>I can create an expression for the visibility property as follows:
> =iif(countDistinct(Fields!RefNbr.Value)=1,True,False)
> BUT when I try to do something similar for the fontweight property like
> =iif( Fields!Carryover.Value = 2 ,Heavy,Normal) I get the following error
> message
> Name Heavy is not declared
> '|||Another gotcha is using font weight names in expression. When using a font
weight in an expression you have to use the serialized value.
In your case you will need to use =iif(Fields!Carryover.Value = 2, "900",
"Normal).
This chart shows how the named displyed in Report Designer's UI maps to the
serialized value.
UI Display Serialized
Lighter Lighter
Thin 100
Extra Light 200
Light Light
Normal Normal
Medium 500
Semi-Bold 600
Bold 700
Extra Bold 800
Heavy 900
Bolder Bolder
Bruce Johnson [MSFT]
Microsoft SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Lukasz Pawlowski [MSFT]" <lukaszp@.online.microsoft.com> wrote in message
news:O86wRYyeEHA.384@.TK2MSFTNGP10.phx.gbl...
> Try: =iif( Fields!Carryover.Value = 2 ,"Heavy","Normal")
> -Lukasz
>
> --
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> "Mardy" <Mardy@.discussions.microsoft.com> wrote in message
> news:E4B78AB2-9D82-4B14-9A0A-2FFD4D41359D@.microsoft.com...
> >I can create an expression for the visibility property as follows:
> > =iif(countDistinct(Fields!RefNbr.Value)=1,True,False)
> >
> > BUT when I try to do something similar for the fontweight property like
> > =iif( Fields!Carryover.Value = 2 ,Heavy,Normal) I get the following
error
> > message
> >
> > Name Heavy is not declared
> >
> > '
>
=iif(countDistinct(Fields!RefNbr.Value)=1,True,False)
BUT when I try to do something similar for the fontweight property like
=iif( Fields!Carryover.Value = 2 ,Heavy,Normal) I get the following error message
Name Heavy is not declared
'Try: =iif( Fields!Carryover.Value = 2 ,"Heavy","Normal")
-Lukasz
This posting is provided "AS IS" with no warranties, and confers no rights.
"Mardy" <Mardy@.discussions.microsoft.com> wrote in message
news:E4B78AB2-9D82-4B14-9A0A-2FFD4D41359D@.microsoft.com...
>I can create an expression for the visibility property as follows:
> =iif(countDistinct(Fields!RefNbr.Value)=1,True,False)
> BUT when I try to do something similar for the fontweight property like
> =iif( Fields!Carryover.Value = 2 ,Heavy,Normal) I get the following error
> message
> Name Heavy is not declared
> '|||Another gotcha is using font weight names in expression. When using a font
weight in an expression you have to use the serialized value.
In your case you will need to use =iif(Fields!Carryover.Value = 2, "900",
"Normal).
This chart shows how the named displyed in Report Designer's UI maps to the
serialized value.
UI Display Serialized
Lighter Lighter
Thin 100
Extra Light 200
Light Light
Normal Normal
Medium 500
Semi-Bold 600
Bold 700
Extra Bold 800
Heavy 900
Bolder Bolder
Bruce Johnson [MSFT]
Microsoft SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Lukasz Pawlowski [MSFT]" <lukaszp@.online.microsoft.com> wrote in message
news:O86wRYyeEHA.384@.TK2MSFTNGP10.phx.gbl...
> Try: =iif( Fields!Carryover.Value = 2 ,"Heavy","Normal")
> -Lukasz
>
> --
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> "Mardy" <Mardy@.discussions.microsoft.com> wrote in message
> news:E4B78AB2-9D82-4B14-9A0A-2FFD4D41359D@.microsoft.com...
> >I can create an expression for the visibility property as follows:
> > =iif(countDistinct(Fields!RefNbr.Value)=1,True,False)
> >
> > BUT when I try to do something similar for the fontweight property like
> > =iif( Fields!Carryover.Value = 2 ,Heavy,Normal) I get the following
error
> > message
> >
> > Name Heavy is not declared
> >
> > '
>
Subscribe to:
Posts (Atom)