EnumObjectPermissions on a ApplicationRole and DatabaseRole objects returns o entries

HI,

Call to EnumObjectPermissions method on a SMO ApplicationRole or DatabseRole object returns an empty collection, however, a call to EnumDatabaseRoleMember on a DatabaseRole object using DMO returns the correct list of membership. Please clarify.

Regards,

Joginder

Hmm I had the same problem with SMO, but I did not try DMO.

I found a workaround. Use the similar method at the Database level, and supply the role name as a string.

using Microsoft.SqlServer.Management.Smo;

using Microsoft.SqlServer.Management.Common;

Database dbHold = smoServer.Databases["YourDB"];

String holdString;

foreach( DatabaseRole dr in dbHold.Roles)

{

ObjectPermissionInfo[] ra = dr.EnumObjectPermissions(); // mysteriously returns null!!

foreach (ObjectPermissionInfo opi in dbHold.EnumObjectPermissions(dr.Name))

{

holdString = String.Format("-OPIRole:{0} has {1}{2}{3}", dr.Name, opi.Grantor, opi.Grantee, opi.ObjectName);

}

}

}

Regards,

Chip

EnumObjectPermissions on a ApplicationRole and DatabaseRole objects returns o entries

HI,

Call to EnumObjectPermissions method on a SMO ApplicationRole or DatabseRole object returns an empty collection, however, a call to EnumDatabaseRoleMember on a DatabaseRole object using DMO returns the correct list of membership. Please clarify.

Regards,

Joginder

Hmm I had the same problem with SMO, but I did not try DMO.

I found a workaround. Use the similar method at the Database level, and supply the role name as a string.

using Microsoft.SqlServer.Management.Smo;

using Microsoft.SqlServer.Management.Common;

Database dbHold = smoServer.Databases["YourDB"];

String holdString;

foreach( DatabaseRole dr in dbHold.Roles)

{

ObjectPermissionInfo[] ra = dr.EnumObjectPermissions(); // mysteriously returns null!!

foreach (ObjectPermissionInfo opi in dbHold.EnumObjectPermissions(dr.Name))

{

holdString = String.Format("-OPIRole:{0} has {1}{2}{3}", dr.Name, opi.Grantor, opi.Grantee, opi.ObjectName);

}

}

}

Regards,

Chip

Entries in Sysindexes

Recently a copy of a production database was made in order to try to improve
for an application that was experiencing slowness. Performance had
apparently improved until today. The developers are claiming that the
degredation in performance is due to extra enties in sysindexes with names
starting with '_WA_SYS_'. A more complete example is
'_WA_Sys_TS_ESTATE_ANALYSIS_29221CFB'
When I execute sp_helpindex on a table with these kind of entires, I do not
see anything that corresponds to this name. I did notice that for a given
table there could be many entries like this. I do see entires in sysindexes
corresponding to actual indexes. I've also noticed that the entries startin
g
with '_WA_SYS_' have the first & root fields equal to '0x00000000'.
Can someone explain what these '_WA_SYS_' entries are and can they be
deleted safely?
There is a mainteneace plan set up to due data & index page reorganization
everyday except Sunday. Could this be what is creating this entires?
Thanks
--
MGI believe those are index column statistics and I am sure they are not the
cause of any degraded performance. IMHO you should not delete them.
Nathan H. Omukwenyi.
"MGeles" <michael.geles@.thomson.com> wrote in message
news:E3DF30D2-787E-4051-B58A-1C49EE8BCE2C@.microsoft.com...
> Recently a copy of a production database was made in order to try to
> improve
> for an application that was experiencing slowness. Performance had
> apparently improved until today. The developers are claiming that the
> degredation in performance is due to extra enties in sysindexes with names
> starting with '_WA_SYS_'. A more complete example is
> '_WA_Sys_TS_ESTATE_ANALYSIS_29221CFB'
> When I execute sp_helpindex on a table with these kind of entires, I do
> not
> see anything that corresponds to this name. I did notice that for a given
> table there could be many entries like this. I do see entires in
> sysindexes
> corresponding to actual indexes. I've also noticed that the entries
> starting
> with '_WA_SYS_' have the first & root fields equal to '0x00000000'.
> Can someone explain what these '_WA_SYS_' entries are and can they be
> deleted safely?
> There is a mainteneace plan set up to due data & index page reorganization
> everyday except Sunday. Could this be what is creating this entires?
> Thanks
> --
> MG|||When the Auto Create Statistics option is enabled, _WA_ indexes are
created for columns that do not have an index.
Somewhere I read, can't find the article right now, that if you are
seeing indexes named that way, it is advisable to add indexes to replace
them, as the Auto created ones are not as efficient as a regular index.
The article also stated that the Auto Create Statistics should not be
disable as any index is better then none.
HTH
Michael
nathan wrote:
> I believe those are index column statistics and I am sure they are not the
> cause of any degraded performance. IMHO you should not delete them.
> Nathan H. Omukwenyi.
>
>
> "MGeles" <michael.geles@.thomson.com> wrote in message
> news:E3DF30D2-787E-4051-B58A-1C49EE8BCE2C@.microsoft.com...
>|||"Michael T" <michaelteff@.skyline.com> wrote in message
news:uD1bdQlYGHA.4424@.TK2MSFTNGP05.phx.gbl...
> When the Auto Create Statistics option is enabled, _WA_ indexes are
> created for columns that do not have an index.
> Somewhere I read, can't find the article right now, that if you are seeing
> indexes named that way, it is advisable to add indexes to replace them, as
> the Auto created ones are not as efficient as a regular index. The article
> also stated that the Auto Create Statistics should not be disable as any
> index is better then none.
>
Ok. Indexes and Statistics are distinct, but related objects. When you
create an index, statistics are created automatically, but you might want to
create additional statistics on unindexed columns or sets of columns.
See:
Statistics Used by the Query Optimizer in Microsoft SQL Server 2005
http://www.microsoft.com/technet/pr...5/qrystats.mspx
Much of the information is valid for SQL 2000 too.
David|||MGeles,
Those entries are create automatically by sql server when the database
option "auto create statistics" is on. SQL Server create those statistics on
columns used in the "join" clause, or in the "where" clause, and there is no
t
an index associated to them (from where sql server can access distribution
statistics about those columns). These statistics are used by the query
optimizer when creating the execution plan. If you delete those entries, SQL
Server will create them again as soon as it needs them.
Statistical maintenance functionality (autostats) in SQL Server
http://support.microsoft.com/kb/q195565/
AMB
"MGeles" wrote:

> Recently a copy of a production database was made in order to try to impro
ve
> for an application that was experiencing slowness. Performance had
> apparently improved until today. The developers are claiming that the
> degredation in performance is due to extra enties in sysindexes with names
> starting with '_WA_SYS_'. A more complete example is
> '_WA_Sys_TS_ESTATE_ANALYSIS_29221CFB'
> When I execute sp_helpindex on a table with these kind of entires, I do no
t
> see anything that corresponds to this name. I did notice that for a given
> table there could be many entries like this. I do see entires in sysindex
es
> corresponding to actual indexes. I've also noticed that the entries start
ing
> with '_WA_SYS_' have the first & root fields equal to '0x00000000'.
> Can someone explain what these '_WA_SYS_' entries are and can they be
> deleted safely?
> There is a mainteneace plan set up to due data & index page reorganization
> everyday except Sunday. Could this be what is creating this entires?
> Thanks
> --
> MG|||MG-
Check out the link below.
http://www.extremeexperts.com/SQL/FAQ/SysStats.aspx
--
Thomas
"MGeles" wrote:

> Recently a copy of a production database was made in order to try to impro
ve
> for an application that was experiencing slowness. Performance had
> apparently improved until today. The developers are claiming that the
> degredation in performance is due to extra enties in sysindexes with names
> starting with '_WA_SYS_'. A more complete example is
> '_WA_Sys_TS_ESTATE_ANALYSIS_29221CFB'
> When I execute sp_helpindex on a table with these kind of entires, I do no
t
> see anything that corresponds to this name. I did notice that for a given
> table there could be many entries like this. I do see entires in sysindex
es
> corresponding to actual indexes. I've also noticed that the entries start
ing
> with '_WA_SYS_' have the first & root fields equal to '0x00000000'.
> Can someone explain what these '_WA_SYS_' entries are and can they be
> deleted safely?
> There is a mainteneace plan set up to due data & index page reorganization
> everyday except Sunday. Could this be what is creating this entires?
> Thanks
> --
> MGsql

Entries in Sysindexes

Recently a copy of a production database was made in order to try to improve
for an application that was experiencing slowness. Performance had
apparently improved until today. The developers are claiming that the
degredation in performance is due to extra enties in sysindexes with names
starting with '_WA_SYS_'. A more complete example is
'_WA_Sys_TS_ESTATE_ANALYSIS_29221CFB'
When I execute sp_helpindex on a table with these kind of entires, I do not
see anything that corresponds to this name. I did notice that for a given
table there could be many entries like this. I do see entires in sysindexes
corresponding to actual indexes. I've also noticed that the entries starting
with '_WA_SYS_' have the first & root fields equal to '0x00000000'.
Can someone explain what these '_WA_SYS_' entries are and can they be
deleted safely?
There is a mainteneace plan set up to due data & index page reorganization
everyday except Sunday. Could this be what is creating this entires?
Thanks
--
MGI believe those are index column statistics and I am sure they are not the
cause of any degraded performance. IMHO you should not delete them.
Nathan H. Omukwenyi.
"MGeles" <michael.geles@.thomson.com> wrote in message
news:E3DF30D2-787E-4051-B58A-1C49EE8BCE2C@.microsoft.com...
> Recently a copy of a production database was made in order to try to
> improve
> for an application that was experiencing slowness. Performance had
> apparently improved until today. The developers are claiming that the
> degredation in performance is due to extra enties in sysindexes with names
> starting with '_WA_SYS_'. A more complete example is
> '_WA_Sys_TS_ESTATE_ANALYSIS_29221CFB'
> When I execute sp_helpindex on a table with these kind of entires, I do
> not
> see anything that corresponds to this name. I did notice that for a given
> table there could be many entries like this. I do see entires in
> sysindexes
> corresponding to actual indexes. I've also noticed that the entries
> starting
> with '_WA_SYS_' have the first & root fields equal to '0x00000000'.
> Can someone explain what these '_WA_SYS_' entries are and can they be
> deleted safely?
> There is a mainteneace plan set up to due data & index page reorganization
> everyday except Sunday. Could this be what is creating this entires?
> Thanks
> --
> MG|||When the Auto Create Statistics option is enabled, _WA_ indexes are
created for columns that do not have an index.
Somewhere I read, can't find the article right now, that if you are
seeing indexes named that way, it is advisable to add indexes to replace
them, as the Auto created ones are not as efficient as a regular index.
The article also stated that the Auto Create Statistics should not be
disable as any index is better then none.
HTH
Michael
nathan wrote:
> I believe those are index column statistics and I am sure they are not the
> cause of any degraded performance. IMHO you should not delete them.
> Nathan H. Omukwenyi.
>
>
> "MGeles" <michael.geles@.thomson.com> wrote in message
> news:E3DF30D2-787E-4051-B58A-1C49EE8BCE2C@.microsoft.com...
>> Recently a copy of a production database was made in order to try to
>> improve
>> for an application that was experiencing slowness. Performance had
>> apparently improved until today. The developers are claiming that the
>> degredation in performance is due to extra enties in sysindexes with names
>> starting with '_WA_SYS_'. A more complete example is
>> '_WA_Sys_TS_ESTATE_ANALYSIS_29221CFB'
>> When I execute sp_helpindex on a table with these kind of entires, I do
>> not
>> see anything that corresponds to this name. I did notice that for a given
>> table there could be many entries like this. I do see entires in
>> sysindexes
>> corresponding to actual indexes. I've also noticed that the entries
>> starting
>> with '_WA_SYS_' have the first & root fields equal to '0x00000000'.
>> Can someone explain what these '_WA_SYS_' entries are and can they be
>> deleted safely?
>> There is a mainteneace plan set up to due data & index page reorganization
>> everyday except Sunday. Could this be what is creating this entires?
>> Thanks
>> --
>> MG
>|||"Michael T" <michaelteff@.skyline.com> wrote in message
news:uD1bdQlYGHA.4424@.TK2MSFTNGP05.phx.gbl...
> When the Auto Create Statistics option is enabled, _WA_ indexes are
> created for columns that do not have an index.
> Somewhere I read, can't find the article right now, that if you are seeing
> indexes named that way, it is advisable to add indexes to replace them, as
> the Auto created ones are not as efficient as a regular index. The article
> also stated that the Auto Create Statistics should not be disable as any
> index is better then none.
>
Ok. Indexes and Statistics are distinct, but related objects. When you
create an index, statistics are created automatically, but you might want to
create additional statistics on unindexed columns or sets of columns.
See:
Statistics Used by the Query Optimizer in Microsoft SQL Server 2005
http://www.microsoft.com/technet/prodtechnol/sql/2005/qrystats.mspx
Much of the information is valid for SQL 2000 too.
David|||MGeles,
Those entries are create automatically by sql server when the database
option "auto create statistics" is on. SQL Server create those statistics on
columns used in the "join" clause, or in the "where" clause, and there is not
an index associated to them (from where sql server can access distribution
statistics about those columns). These statistics are used by the query
optimizer when creating the execution plan. If you delete those entries, SQL
Server will create them again as soon as it needs them.
Statistical maintenance functionality (autostats) in SQL Server
http://support.microsoft.com/kb/q195565/
AMB
"MGeles" wrote:
> Recently a copy of a production database was made in order to try to improve
> for an application that was experiencing slowness. Performance had
> apparently improved until today. The developers are claiming that the
> degredation in performance is due to extra enties in sysindexes with names
> starting with '_WA_SYS_'. A more complete example is
> '_WA_Sys_TS_ESTATE_ANALYSIS_29221CFB'
> When I execute sp_helpindex on a table with these kind of entires, I do not
> see anything that corresponds to this name. I did notice that for a given
> table there could be many entries like this. I do see entires in sysindexes
> corresponding to actual indexes. I've also noticed that the entries starting
> with '_WA_SYS_' have the first & root fields equal to '0x00000000'.
> Can someone explain what these '_WA_SYS_' entries are and can they be
> deleted safely?
> There is a mainteneace plan set up to due data & index page reorganization
> everyday except Sunday. Could this be what is creating this entires?
> Thanks
> --
> MG|||MG-
Check out the link below.
http://www.extremeexperts.com/SQL/FAQ/SysStats.aspx
--
Thomas
"MGeles" wrote:
> Recently a copy of a production database was made in order to try to improve
> for an application that was experiencing slowness. Performance had
> apparently improved until today. The developers are claiming that the
> degredation in performance is due to extra enties in sysindexes with names
> starting with '_WA_SYS_'. A more complete example is
> '_WA_Sys_TS_ESTATE_ANALYSIS_29221CFB'
> When I execute sp_helpindex on a table with these kind of entires, I do not
> see anything that corresponds to this name. I did notice that for a given
> table there could be many entries like this. I do see entires in sysindexes
> corresponding to actual indexes. I've also noticed that the entries starting
> with '_WA_SYS_' have the first & root fields equal to '0x00000000'.
> Can someone explain what these '_WA_SYS_' entries are and can they be
> deleted safely?
> There is a mainteneace plan set up to due data & index page reorganization
> everyday except Sunday. Could this be what is creating this entires?
> Thanks
> --
> MG

enterprise manager entries

where does sqlserver store the enterprise manager server registration entries
in the registry?Per default:
HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL Server\80\Tools\SQLEW\Registered Servers X
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Bharath" <Bharath@.discussions.microsoft.com> wrote in message
news:E296F5A6-F532-49DB-852C-2755B266C9B0@.microsoft.com...
> where does sqlserver store the enterprise manager server registration entries
> in the registry?

enterprise manager entries

I create SQL Server Groups in Enterprise manager and for
some reason and at what seems like random times they all
go away. I see a blank list under SQL Server Groups.
I checked the registry entry below and all SQL Server
Groups that I created are there.
HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL
Server\80\Tools\SQLEW\Registered Servers X\SQL Server
Group
With that information, is there a way to hook it back
together so what is in the registry is what is displayed
in enterprise manager for SQL Server?
Thanks
RickRick,
Strange!What service pack and OS are you on?
--
Dinesh.
SQL Server FAQ at
http://www.tkdinesh.com
"Rick Allison" <allisonrja@.hotmail.com> wrote in message
news:edc3f8oWDHA.2056@.TK2MSFTNGP11.phx.gbl...
> I create SQL Server Groups in Enterprise manager and for
> some reason and at what seems like random times they all
> go away. I see a blank list under SQL Server Groups.
> I checked the registry entry below and all SQL Server
> Groups that I created are there.
> HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL
> Server\80\Tools\SQLEW\Registered Servers X\SQL Server
> Group
> With that information, is there a way to hook it back
> together so what is in the registry is what is displayed
> in enterprise manager for SQL Server?
> Thanks
> Rick
>|||Dinesh,
I am running Windows XP and enterprise manager version 8.0. (at least
that's what is says in help about)
Does that help?
Rick
"Dinesh.T.K" <tkdinesh@.nospam.mail.tkdinesh.com> wrote in message
news:uZ6mdGpWDHA.1744@.TK2MSFTNGP12.phx.gbl...
> Rick,
> Strange!What service pack and OS are you on?
> --
> Dinesh.
> SQL Server FAQ at
> http://www.tkdinesh.com
> "Rick Allison" <allisonrja@.hotmail.com> wrote in message
> news:edc3f8oWDHA.2056@.TK2MSFTNGP11.phx.gbl...
> > I create SQL Server Groups in Enterprise manager and for
> > some reason and at what seems like random times they all
> > go away. I see a blank list under SQL Server Groups.
> >
> > I checked the registry entry below and all SQL Server
> > Groups that I created are there.
> > HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL
> > Server\80\Tools\SQLEW\Registered Servers X\SQL Server
> > Group
> >
> > With that information, is there a way to hook it back
> > together so what is in the registry is what is displayed
> > in enterprise manager for SQL Server?
> >
> > Thanks
> >
> > Rick
> >
> >
>|||Rick,
Thanks but I need the service pack(sp) info. too to report this case in mvp
newsgroup.You can find the sp info by executing the below command in Query
Analyzer
SELECT SERVERPROPERTY('PRODUCTLEVEL')
Dinesh.
SQL Server FAQ at
http://www.tkdinesh.com
"Rick Allison" <allisonrja@.hotmail.com> wrote in message
news:%23umCGTpWDHA.1900@.TK2MSFTNGP10.phx.gbl...
> Dinesh,
> I am running Windows XP and enterprise manager version 8.0. (at least
> that's what is says in help about)
> Does that help?
> Rick
> "Dinesh.T.K" <tkdinesh@.nospam.mail.tkdinesh.com> wrote in message
> news:uZ6mdGpWDHA.1744@.TK2MSFTNGP12.phx.gbl...
> > Rick,
> >
> > Strange!What service pack and OS are you on?
> >
> > --
> > Dinesh.
> > SQL Server FAQ at
> > http://www.tkdinesh.com
> >
> > "Rick Allison" <allisonrja@.hotmail.com> wrote in message
> > news:edc3f8oWDHA.2056@.TK2MSFTNGP11.phx.gbl...
> > > I create SQL Server Groups in Enterprise manager and for
> > > some reason and at what seems like random times they all
> > > go away. I see a blank list under SQL Server Groups.
> > >
> > > I checked the registry entry below and all SQL Server
> > > Groups that I created are there.
> > > HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL
> > > Server\80\Tools\SQLEW\Registered Servers X\SQL Server
> > > Group
> > >
> > > With that information, is there a way to hook it back
> > > together so what is in the registry is what is displayed
> > > in enterprise manager for SQL Server?
> > >
> > > Thanks
> > >
> > > Rick
> > >
> > >
> >
> >
>|||Rick,
Thanks.Can you try upgrading to SP3 or latest SP3a?the download is available
at http://www.microsoft.com/sql/downloads/2000/sp3.asp.
The reason for my advice is , may be, its due to the slammer worm.More
details
http://www.microsoft.com/sql/techinfo/administration/2000/security/slammer.asp
Even if you report this error(or bug), the first suggestion would be to go
in for the latest service pack.So do a test of your app. in a test env. with
SP3(a) and if okay, then go for the same with prod.
--
Dinesh.
SQL Server FAQ at
http://www.tkdinesh.com
"Rick Allison" <allisonrja@.hotmail.com> wrote in message
news:ObqkmvpWDHA.1872@.TK2MSFTNGP12.phx.gbl...
> Dinesh,
> The query returned - SP2
> Rick
> "Dinesh.T.K" <tkdinesh@.nospam.mail.tkdinesh.com> wrote in message
> news:OANx1WpWDHA.1900@.TK2MSFTNGP10.phx.gbl...
> > Rick,
> >
> > Thanks but I need the service pack(sp) info. too to report this case in
> mvp
> > newsgroup.You can find the sp info by executing the below command in
Query
> > Analyzer
> >
> > SELECT SERVERPROPERTY('PRODUCTLEVEL')
> >
> >
> > --
> > Dinesh.
> > SQL Server FAQ at
> > http://www.tkdinesh.com
> >
> > "Rick Allison" <allisonrja@.hotmail.com> wrote in message
> > news:%23umCGTpWDHA.1900@.TK2MSFTNGP10.phx.gbl...
> > > Dinesh,
> > >
> > > I am running Windows XP and enterprise manager version 8.0. (at least
> > > that's what is says in help about)
> > >
> > > Does that help?
> > >
> > > Rick
> > > "Dinesh.T.K" <tkdinesh@.nospam.mail.tkdinesh.com> wrote in message
> > > news:uZ6mdGpWDHA.1744@.TK2MSFTNGP12.phx.gbl...
> > > > Rick,
> > > >
> > > > Strange!What service pack and OS are you on?
> > > >
> > > > --
> > > > Dinesh.
> > > > SQL Server FAQ at
> > > > http://www.tkdinesh.com
> > > >
> > > > "Rick Allison" <allisonrja@.hotmail.com> wrote in message
> > > > news:edc3f8oWDHA.2056@.TK2MSFTNGP11.phx.gbl...
> > > > > I create SQL Server Groups in Enterprise manager and for
> > > > > some reason and at what seems like random times they all
> > > > > go away. I see a blank list under SQL Server Groups.
> > > > >
> > > > > I checked the registry entry below and all SQL Server
> > > > > Groups that I created are there.
> > > > > HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL
> > > > > Server\80\Tools\SQLEW\Registered Servers X\SQL Server
> > > > > Group
> > > > >
> > > > > With that information, is there a way to hook it back
> > > > > together so what is in the registry is what is displayed
> > > > > in enterprise manager for SQL Server?
> > > > >
> > > > > Thanks
> > > > >
> > > > > Rick
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>|||Dinesh,
Okay - I'll go try.
I am, however, a developer in a large corporation and I use enterprise
manager to point to many different SQL Server databases, test and
production. Do I need to have each database updated or can I just update
enterprise manager that is loaded on my computer?
If I need to do each database, that is not a simple task. (sigh)
Thanks for all your help.
Rick
"Dinesh.T.K" <tkdinesh@.nospam.mail.tkdinesh.com> wrote in message
news:O%23FGn4pWDHA.3404@.tk2msftngp13.phx.gbl...
> Rick,
> Thanks.Can you try upgrading to SP3 or latest SP3a?the download is
available
> at http://www.microsoft.com/sql/downloads/2000/sp3.asp.
> The reason for my advice is , may be, its due to the slammer worm.More
> details
>
http://www.microsoft.com/sql/techinfo/administration/2000/security/slammer.asp
> Even if you report this error(or bug), the first suggestion would be to go
> in for the latest service pack.So do a test of your app. in a test env.
with
> SP3(a) and if okay, then go for the same with prod.
> --
> Dinesh.
> SQL Server FAQ at
> http://www.tkdinesh.com
> "Rick Allison" <allisonrja@.hotmail.com> wrote in message
> news:ObqkmvpWDHA.1872@.TK2MSFTNGP12.phx.gbl...
> > Dinesh,
> >
> > The query returned - SP2
> >
> > Rick
> >
> > "Dinesh.T.K" <tkdinesh@.nospam.mail.tkdinesh.com> wrote in message
> > news:OANx1WpWDHA.1900@.TK2MSFTNGP10.phx.gbl...
> > > Rick,
> > >
> > > Thanks but I need the service pack(sp) info. too to report this case
in
> > mvp
> > > newsgroup.You can find the sp info by executing the below command in
> Query
> > > Analyzer
> > >
> > > SELECT SERVERPROPERTY('PRODUCTLEVEL')
> > >
> > >
> > > --
> > > Dinesh.
> > > SQL Server FAQ at
> > > http://www.tkdinesh.com
> > >
> > > "Rick Allison" <allisonrja@.hotmail.com> wrote in message
> > > news:%23umCGTpWDHA.1900@.TK2MSFTNGP10.phx.gbl...
> > > > Dinesh,
> > > >
> > > > I am running Windows XP and enterprise manager version 8.0. (at
least
> > > > that's what is says in help about)
> > > >
> > > > Does that help?
> > > >
> > > > Rick
> > > > "Dinesh.T.K" <tkdinesh@.nospam.mail.tkdinesh.com> wrote in message
> > > > news:uZ6mdGpWDHA.1744@.TK2MSFTNGP12.phx.gbl...
> > > > > Rick,
> > > > >
> > > > > Strange!What service pack and OS are you on?
> > > > >
> > > > > --
> > > > > Dinesh.
> > > > > SQL Server FAQ at
> > > > > http://www.tkdinesh.com
> > > > >
> > > > > "Rick Allison" <allisonrja@.hotmail.com> wrote in message
> > > > > news:edc3f8oWDHA.2056@.TK2MSFTNGP11.phx.gbl...
> > > > > > I create SQL Server Groups in Enterprise manager and for
> > > > > > some reason and at what seems like random times they all
> > > > > > go away. I see a blank list under SQL Server Groups.
> > > > > >
> > > > > > I checked the registry entry below and all SQL Server
> > > > > > Groups that I created are there.
> > > > > > HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL
> > > > > > Server\80\Tools\SQLEW\Registered Servers X\SQL Server
> > > > > > Group
> > > > > >
> > > > > > With that information, is there a way to hook it back
> > > > > > together so what is in the registry is what is displayed
> > > > > > in enterprise manager for SQL Server?
> > > > > >
> > > > > > Thanks
> > > > > >
> > > > > > Rick
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>

enterprise manager entries

where does sqlserver store the enterprise manager server registration entries
in the registry?
Per default:
HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL Server\80\Tools\SQLEW\Registered Servers X
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Bharath" <Bharath@.discussions.microsoft.com> wrote in message
news:E296F5A6-F532-49DB-852C-2755B266C9B0@.microsoft.com...
> where does sqlserver store the enterprise manager server registration entries
> in the registry?

enterprise manager entries

where does sqlserver store the enterprise manager server registration entrie
s
in the registry?Per default:
HKEY_CURRENT_USER\Software\Microsoft\Mic
rosoft SQL Server\80\Tools\SQLEW\Reg
istered Servers X
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Bharath" <Bharath@.discussions.microsoft.com> wrote in message
news:E296F5A6-F532-49DB-852C-2755B266C9B0@.microsoft.com...
> where does sqlserver store the enterprise manager server registration entr
ies
> in the registry?