Home All Groups Group Topic Archive Search About

SQL2005: "Registered Owner" and "Registered Organization" available?

Author
7 Jun 2006 7:06 PM
Mark Findlay
In SQL2000 the "Registered Owner" and "Registered Organization" were
available as registry values, but the values don't exist in SQL2005. Is
there a way to report these values in SQL2005 - either by registry read, or
perhaps by reading a database table?

Note: SQLDMO fails to return any value in SQL2005.

Thanks!
Mark

Author
8 Jun 2006 7:45 AM
Steven Cheng[MSFT]
Hello Mark,

Thank you for posting in the MSDN newsgroup.

From your description, I understand you used to use the "RegisteredOwner"
registry values in windows registry to query the install user of the SQL
Server 2000 instance(through SQL DMO). However, when you try using DMO to
query the same value on SQL Server 2005 instance, you get nothing, correct?
If there is anything I don't get correctly, please feel free to let me know.

As for the  "RegisteredOwner", based on my research, it is a external value
store only in registry, therefore, there is no duplicated copy in the SQL
Server database where we can use T-SQL to query.   Also, this registry
value seems specific to SQL Server 2000 instance, as for SQL Server 2005
instances, you can still find this value under the following key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\MSSQL.1\MSSQLServer\CurrentVersion

However, this "RegisterdOwner" value is always empty for SQL Server 2005
instances, I think that's why your DMO object always return nothing. BTW,
may I have your detailed scenario that why you will need this
"registeredowner" value, I've also discussed with some other SQL guys and
they agree that this is a legacy feature of previous version and as for SQL
server 2005, we'd better not rely on this since there is no official
document on this.

In addition, as for DMO, it is specific to former versions of SQL
Server(7.0, 8.0), as for SQL Server 2005, it is provided as a legacy
component. And for most common SQL Server management for 2005 instance, we
can consider using the new Server management Objects in SQL Server 2005.

#SQL Server Management Objects (SMO) 
http://msdn2.microsoft.com/en-us/library/ms162169.aspx

Anyway, please feel free to post here if there is anything else we can help
you.

Regards,

Steven Cheng
Microsoft Online Community Support


==================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

==================================================


This posting is provided "AS IS" with no warranties, and confers no rights.



Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
Author
9 Jun 2006 3:21 PM
Steven Cheng[MSFT]
Hello Mark,

How are you doing on this issue, does my last reply helps you a little?
Also, if there is anything else we can help you, please feel free to post
here.


Regards,

Steven Cheng
Microsoft Online Community Support


==================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

==================================================


This posting is provided "AS IS" with no warranties, and confers no rights.



Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
Author
12 Jun 2006 4:14 PM
Mark Findlay
Thanks Steven,

But I do not see any reply. I only see my original question. Can you
resubmit your reply?

Thanks,
Mark

Show quote
"Steven Cheng[MSFT]" <stch***@online.microsoft.com> wrote in message
news:M0Sskh9iGHA.5184@TK2MSFTNGXA01.phx.gbl...
> Hello Mark,
>
> How are you doing on this issue, does my last reply helps you a little?
> Also, if there is anything else we can help you, please feel free to post
> here.
>
>
> Regards,
>
> Steven Cheng
> Microsoft Online Community Support
>
>
> ==================================================
>
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
>
> ==================================================
>
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
>
>
> Get Secure! www.microsoft.com/security
> (This posting is provided "AS IS", with no warranties, and confers no
> rights.)
>
Author
13 Jun 2006 5:43 AM
Steven Cheng[MSFT]
Sure Mark,

Here is my first reply in this thread:
=============================
Hello Mark,

Thank you for posting in the MSDN newsgroup.

From your description, I understand you used to use the "RegisteredOwner"
registry values in windows registry to query the install user of the SQL
Server 2000 instance(through SQL DMO). However, when you try using DMO to
query the same value on SQL Server 2005 instance, you get nothing, correct?
If there is anything I don't get correctly, please feel free to let me know.

As for the  "RegisteredOwner", based on my research, it is a external value
store only in registry, therefore, there is no duplicated copy in the SQL
Server database where we can use T-SQL to query.   Also, this registry
value seems specific to SQL Server 2000 instance, as for SQL Server 2005
instances, you can still find this value under the following key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\MSSQL.1\MSSQLServer\CurrentVersion

However, this "RegisterdOwner" value is always empty for SQL Server 2005
instances, I think that's why your DMO object always return nothing. BTW,
may I have your detailed scenario that why you will need this
"registeredowner" value, I've also discussed with some other SQL guys and
they agree that this is a legacy feature of previous version and as for SQL
server 2005, we'd better not rely on this since there is no official
document on this.

In addition, as for DMO, it is specific to former versions of SQL
Server(7.0, 8.0), as for SQL Server 2005, it is provided as a legacy
component. And for most common SQL Server management for 2005 instance, we
can consider using the new Server management Objects in SQL Server 2005.

#SQL Server Management Objects (SMO) 
http://msdn2.microsoft.com/en-us/library/ms162169.aspx

Anyway, please feel free to post here if there is anything else we can help
you.

Regards,

Steven Cheng
==================================

maybe the message get lost in the reader. Are you using OE or web reader to
access the newsgroup?

Hope this helps.

Regards,

Steven Cheng
Microsoft MSDN Online Support Lead


==================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

==================================================


This posting is provided "AS IS" with no warranties, and confers no rights.



Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

AddThis Social Bookmark Button