Dave Wickert, if you're out there...
I posted this question before, but would like to know if there is a way to
keep domain admins from viewing cube data from Excel. I tried creating roles
and preventing access by restricting dimensions in MDX expressions, but they
can still see the data, regardless of how I construct the role. They are not
OLAP administrators, so can someone who knows, please tell me what's going on
here behind the scenes?
Thanks
I think I may have posted to your previous question, but since then I
have found the answer.
There is a registry setting that was introduced for SP4 that allows you
to exclude the machine admins from the OLAP Administrators.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\OLAP Server
\CurrentVersionExcludeMachineAdminFromOLAPAdmin
Creating a Dword entry and setting it to a value of 1 should fix your
issue. (I assume you may need to restart the service after setting this
value)
There is a list of all the Analysis Services registry entries here:
http://msdn.microsoft.com/library/de...l=/library/en-
us/dnsql2k/html/sql2k_anservregsettings.asp
Below is the section of that page that refers to this new key.
<snip>
The ExcludeMachineAdminFromOLAPAdmin entry controls the inclusion of the
local Administrators group as administrators of the Analysis Services
server.
This entry is not installed in the registry during the setup process.
This entry was added for SP4.
<snip>
Regards
Darren Gosbell [MCSD]
<dgosbell_at_yahoo_dot_com>
Blog: http://www.geekswithblogs.net/darrengosbell
|||Yep. That's what I was looking for. Thanks.
"Darren Gosbell" wrote:
> I think I may have posted to your previous question, but since then I
> have found the answer.
> There is a registry setting that was introduced for SP4 that allows you
> to exclude the machine admins from the OLAP Administrators.
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\OLAP Server
> \CurrentVersionExcludeMachineAdminFromOLAPAdmin
> Creating a Dword entry and setting it to a value of 1 should fix your
> issue. (I assume you may need to restart the service after setting this
> value)
> There is a list of all the Analysis Services registry entries here:
> http://msdn.microsoft.com/library/de...l=/library/en-
> us/dnsql2k/html/sql2k_anservregsettings.asp
> Below is the section of that page that refers to this new key.
> <snip>
> The ExcludeMachineAdminFromOLAPAdmin entry controls the inclusion of the
> local Administrators group as administrators of the Analysis Services
> server.
> This entry is not installed in the registry during the setup process.
> This entry was added for SP4.
> <snip>
> --
> Regards
> Darren Gosbell [MCSD]
> <dgosbell_at_yahoo_dot_com>
> Blog: http://www.geekswithblogs.net/darrengosbell
>
|||I'll point out the obvious that an Administrator can always add him/her to
the OLAP Administrators group, perform whatever query they want, and then
remove themselves. So if you are going to go down this route, and you really
want a secure system, you need to put auditing of groups into place.
Dave Wickert [MSFT]
dwickert@.online.microsoft.com
Program Manager
BI Systems Team
SQL BI Product Unit (Analysis Services)
This posting is provided "AS IS" with no warranties, and confers no rights.
"Tom" <Tom@.discussions.microsoft.com> wrote in message
news:115E132E-E4DC-4CB5-BADD-06EA7F44EFE1@.microsoft.com...[vbcol=seagreen]
> Yep. That's what I was looking for. Thanks.
> "Darren Gosbell" wrote:
2012年3月19日星期一
Any way to do this?
Dave Wickert, if you're out there...
I posted this question before, but would like to know if there is a way to
keep domain admins from viewing cube data from Excel. I tried creating roles
and preventing access by restricting dimensions in MDX expressions, but they
can still see the data, regardless of how I construct the role. They are not
OLAP administrators, so can someone who knows, please tell me what's going o
n
here behind the scenes?
ThanksI think I may have posted to your previous question, but since then I
have found the answer.
There is a registry setting that was introduced for SP4 that allows you
to exclude the machine admins from the OLAP Administrators.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\OL
AP Server
\CurrentVersionExcludeMachineAdminFromOL
APAdmin
Creating a Dword entry and setting it to a value of 1 should fix your
issue. (I assume you may need to restart the service after setting this
value)
There is a list of all the Analysis Services registry entries here:
http://msdn.microsoft.com/library/d...rl=/library/en-
us/dnsql2k/html/sql2k_anservregsettings.asp
Below is the section of that page that refers to this new key.
<snip>
The ExcludeMachineAdminFromOLAPAdmin entry controls the inclusion of the
local Administrators group as administrators of the Analysis Services
server.
This entry is not installed in the registry during the setup process.
This entry was added for SP4.
<snip>
Regards
Darren Gosbell [MCSD]
<dgosbell_at_yahoo_dot_com>
Blog: http://www.geekswithblogs.net/darrengosbell|||Yep. That's what I was looking for. Thanks.
"Darren Gosbell" wrote:
> I think I may have posted to your previous question, but since then I
> have found the answer.
> There is a registry setting that was introduced for SP4 that allows you
> to exclude the machine admins from the OLAP Administrators.
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\OL
AP Server
> \CurrentVersionExcludeMachineAdminFromOL
APAdmin
> Creating a Dword entry and setting it to a value of 1 should fix your
> issue. (I assume you may need to restart the service after setting this
> value)
> There is a list of all the Analysis Services registry entries here:
> http://msdn.microsoft.com/library/d...rl=/library/en-
> us/dnsql2k/html/sql2k_anservregsettings.asp
> Below is the section of that page that refers to this new key.
> <snip>
> The ExcludeMachineAdminFromOLAPAdmin entry controls the inclusion of the
> local Administrators group as administrators of the Analysis Services
> server.
> This entry is not installed in the registry during the setup process.
> This entry was added for SP4.
> <snip>
> --
> Regards
> Darren Gosbell [MCSD]
> <dgosbell_at_yahoo_dot_com>
> Blog: http://www.geekswithblogs.net/darrengosbell
>|||I'll point out the obvious that an Administrator can always add him/her to
the OLAP Administrators group, perform whatever query they want, and then
remove themselves. So if you are going to go down this route, and you really
want a secure system, you need to put auditing of groups into place.
--
Dave Wickert [MSFT]
dwickert@.online.microsoft.com
Program Manager
BI Systems Team
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Tom" <Tom@.discussions.microsoft.com> wrote in message
news:115E132E-E4DC-4CB5-BADD-06EA7F44EFE1@.microsoft.com...[vbcol=seagreen]
> Yep. That's what I was looking for. Thanks.
> "Darren Gosbell" wrote:
>
I posted this question before, but would like to know if there is a way to
keep domain admins from viewing cube data from Excel. I tried creating roles
and preventing access by restricting dimensions in MDX expressions, but they
can still see the data, regardless of how I construct the role. They are not
OLAP administrators, so can someone who knows, please tell me what's going o
n
here behind the scenes?
ThanksI think I may have posted to your previous question, but since then I
have found the answer.
There is a registry setting that was introduced for SP4 that allows you
to exclude the machine admins from the OLAP Administrators.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\OL
AP Server
\CurrentVersionExcludeMachineAdminFromOL
APAdmin
Creating a Dword entry and setting it to a value of 1 should fix your
issue. (I assume you may need to restart the service after setting this
value)
There is a list of all the Analysis Services registry entries here:
http://msdn.microsoft.com/library/d...rl=/library/en-
us/dnsql2k/html/sql2k_anservregsettings.asp
Below is the section of that page that refers to this new key.
<snip>
The ExcludeMachineAdminFromOLAPAdmin entry controls the inclusion of the
local Administrators group as administrators of the Analysis Services
server.
This entry is not installed in the registry during the setup process.
This entry was added for SP4.
<snip>
Regards
Darren Gosbell [MCSD]
<dgosbell_at_yahoo_dot_com>
Blog: http://www.geekswithblogs.net/darrengosbell|||Yep. That's what I was looking for. Thanks.
"Darren Gosbell" wrote:
> I think I may have posted to your previous question, but since then I
> have found the answer.
> There is a registry setting that was introduced for SP4 that allows you
> to exclude the machine admins from the OLAP Administrators.
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\OL
AP Server
> \CurrentVersionExcludeMachineAdminFromOL
APAdmin
> Creating a Dword entry and setting it to a value of 1 should fix your
> issue. (I assume you may need to restart the service after setting this
> value)
> There is a list of all the Analysis Services registry entries here:
> http://msdn.microsoft.com/library/d...rl=/library/en-
> us/dnsql2k/html/sql2k_anservregsettings.asp
> Below is the section of that page that refers to this new key.
> <snip>
> The ExcludeMachineAdminFromOLAPAdmin entry controls the inclusion of the
> local Administrators group as administrators of the Analysis Services
> server.
> This entry is not installed in the registry during the setup process.
> This entry was added for SP4.
> <snip>
> --
> Regards
> Darren Gosbell [MCSD]
> <dgosbell_at_yahoo_dot_com>
> Blog: http://www.geekswithblogs.net/darrengosbell
>|||I'll point out the obvious that an Administrator can always add him/her to
the OLAP Administrators group, perform whatever query they want, and then
remove themselves. So if you are going to go down this route, and you really
want a secure system, you need to put auditing of groups into place.
--
Dave Wickert [MSFT]
dwickert@.online.microsoft.com
Program Manager
BI Systems Team
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Tom" <Tom@.discussions.microsoft.com> wrote in message
news:115E132E-E4DC-4CB5-BADD-06EA7F44EFE1@.microsoft.com...[vbcol=seagreen]
> Yep. That's what I was looking for. Thanks.
> "Darren Gosbell" wrote:
>
2012年3月11日星期日
any stored procedure to report all the databases' information
Hello everyone,
We're going to migrate our SQL 2000 server from one domain to another. I
need to get a better idea of how our current databases are structured and
utilized. What I want is a report showing each database's:
name
data size
log size
users
if backed up or not
Before I dive into it in my own way, just wondering if there is any stored
procedure that can help collect the above information? I'd appreciate any
help.
Thanks,
Bing
sp_helpdb does most what I wanted.
"bing" wrote:
> Hello everyone,
> We're going to migrate our SQL 2000 server from one domain to another. I
> need to get a better idea of how our current databases are structured and
> utilized. What I want is a report showing each database's:
> name
> data size
> log size
> users
> if backed up or not
> Before I dive into it in my own way, just wondering if there is any stored
> procedure that can help collect the above information? I'd appreciate any
> help.
> Thanks,
> Bing
We're going to migrate our SQL 2000 server from one domain to another. I
need to get a better idea of how our current databases are structured and
utilized. What I want is a report showing each database's:
name
data size
log size
users
if backed up or not
Before I dive into it in my own way, just wondering if there is any stored
procedure that can help collect the above information? I'd appreciate any
help.
Thanks,
Bing
sp_helpdb does most what I wanted.
"bing" wrote:
> Hello everyone,
> We're going to migrate our SQL 2000 server from one domain to another. I
> need to get a better idea of how our current databases are structured and
> utilized. What I want is a report showing each database's:
> name
> data size
> log size
> users
> if backed up or not
> Before I dive into it in my own way, just wondering if there is any stored
> procedure that can help collect the above information? I'd appreciate any
> help.
> Thanks,
> Bing
any stored procedure to report all the databases' information
Hello everyone,
We're going to migrate our SQL 2000 server from one domain to another. I
need to get a better idea of how our current databases are structured and
utilized. What I want is a report showing each database's:
name
data size
log size
users
if backed up or not
Before I dive into it in my own way, just wondering if there is any stored
procedure that can help collect the above information? I'd appreciate any
help.
Thanks,
Bingsp_helpdb does most what I wanted.
"bing" wrote:
> Hello everyone,
> We're going to migrate our SQL 2000 server from one domain to another. I
> need to get a better idea of how our current databases are structured and
> utilized. What I want is a report showing each database's:
> name
> data size
> log size
> users
> if backed up or not
> Before I dive into it in my own way, just wondering if there is any stored
> procedure that can help collect the above information? I'd appreciate any
> help.
> Thanks,
> Bing
We're going to migrate our SQL 2000 server from one domain to another. I
need to get a better idea of how our current databases are structured and
utilized. What I want is a report showing each database's:
name
data size
log size
users
if backed up or not
Before I dive into it in my own way, just wondering if there is any stored
procedure that can help collect the above information? I'd appreciate any
help.
Thanks,
Bingsp_helpdb does most what I wanted.
"bing" wrote:
> Hello everyone,
> We're going to migrate our SQL 2000 server from one domain to another. I
> need to get a better idea of how our current databases are structured and
> utilized. What I want is a report showing each database's:
> name
> data size
> log size
> users
> if backed up or not
> Before I dive into it in my own way, just wondering if there is any stored
> procedure that can help collect the above information? I'd appreciate any
> help.
> Thanks,
> Bing
any stored procedure to report all the databases' information
Hello everyone,
We're going to migrate our SQL 2000 server from one domain to another. I
need to get a better idea of how our current databases are structured and
utilized. What I want is a report showing each database's:
name
data size
log size
users
if backed up or not
Before I dive into it in my own way, just wondering if there is any stored
procedure that can help collect the above information? I'd appreciate any
help.
Thanks,
Bingsp_helpdb does most what I wanted.
"bing" wrote:
> Hello everyone,
> We're going to migrate our SQL 2000 server from one domain to another. I
> need to get a better idea of how our current databases are structured and
> utilized. What I want is a report showing each database's:
> name
> data size
> log size
> users
> if backed up or not
> Before I dive into it in my own way, just wondering if there is any stored
> procedure that can help collect the above information? I'd appreciate any
> help.
> Thanks,
> Bing
We're going to migrate our SQL 2000 server from one domain to another. I
need to get a better idea of how our current databases are structured and
utilized. What I want is a report showing each database's:
name
data size
log size
users
if backed up or not
Before I dive into it in my own way, just wondering if there is any stored
procedure that can help collect the above information? I'd appreciate any
help.
Thanks,
Bingsp_helpdb does most what I wanted.
"bing" wrote:
> Hello everyone,
> We're going to migrate our SQL 2000 server from one domain to another. I
> need to get a better idea of how our current databases are structured and
> utilized. What I want is a report showing each database's:
> name
> data size
> log size
> users
> if backed up or not
> Before I dive into it in my own way, just wondering if there is any stored
> procedure that can help collect the above information? I'd appreciate any
> help.
> Thanks,
> Bing
2012年2月18日星期六
Any help welcomed
Hello all,
I have a SQL 2000 database running on a clustered server. The server domain has recently been changed and may/may not be the cause of my problem. The problem arising is that whenever I backup my database using Enterprise Manager or Query analyser the operation is said to have completed successfully (although looking at the progress bar - which doesn't show the blue status bars moving - this suggestes different). The backup will not then restore or indeed any other backup will not restore, and the database is left in a loading state and never moves away from this.
Any help or suggestions will be greatly appreciated.
Thanks
Richardhttp://support.microsoft.com/newsgroups/default.aspx?NewsGroup=microsoft.public.sqlserver. mseq&SLCID=US&ICP=GSS3&sd=GN&id=fh;en-us;newsgroups
go to clustering
I have a SQL 2000 database running on a clustered server. The server domain has recently been changed and may/may not be the cause of my problem. The problem arising is that whenever I backup my database using Enterprise Manager or Query analyser the operation is said to have completed successfully (although looking at the progress bar - which doesn't show the blue status bars moving - this suggestes different). The backup will not then restore or indeed any other backup will not restore, and the database is left in a loading state and never moves away from this.
Any help or suggestions will be greatly appreciated.
Thanks
Richardhttp://support.microsoft.com/newsgroups/default.aspx?NewsGroup=microsoft.public.sqlserver. mseq&SLCID=US&ICP=GSS3&sd=GN&id=fh;en-us;newsgroups
go to clustering
2012年2月13日星期一
Any comments on DCPROMO to promote domain controller on SQL Server?
We're planning to make our SQL server act as a passive domain controller
and are considering the use of DCPromo to accomplish this. Anybody have
comments regarding their experience changing the Domain Controller roles
on an active SQL server? We've all seen problems in the past monkeying
with core components on stable systems...
Thanks in advance.It is generally not recommende to put SQL on a domain controller ( because
of potential security issues and the DC is likely busy anyway.)
however, the thing that comes to mind is that when the box gets promoted to
a DC, the Domain Controller Security policy now applies to the machine in
addition to the local policies...
Wayne Snyder MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
(Please respond only to the newsgroups.)
I support the Professional Association for SQL Server
(www.sqlpass.org)
"Rusty" <aid940one@.nospam.ohwhocares.com> wrote in message
news:40193732.7020809@.nospam.ohwhocares.com...
and are considering the use of DCPromo to accomplish this. Anybody have
comments regarding their experience changing the Domain Controller roles
on an active SQL server? We've all seen problems in the past monkeying
with core components on stable systems...
Thanks in advance.It is generally not recommende to put SQL on a domain controller ( because
of potential security issues and the DC is likely busy anyway.)
however, the thing that comes to mind is that when the box gets promoted to
a DC, the Domain Controller Security policy now applies to the machine in
addition to the local policies...
Wayne Snyder MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
(Please respond only to the newsgroups.)
I support the Professional Association for SQL Server
(www.sqlpass.org)
"Rusty" <aid940one@.nospam.ohwhocares.com> wrote in message
news:40193732.7020809@.nospam.ohwhocares.com...
quote:
> We're planning to make our SQL server act as a passive domain controller
> and are considering the use of DCPromo to accomplish this. Anybody have
> comments regarding their experience changing the Domain Controller roles
> on an active SQL server? We've all seen problems in the past monkeying
> with core components on stable systems...
> Thanks in advance.
>
Any comments on DCPROMO to promote domain controller on SQL Server?
We're planning to make our SQL server act as a passive domain controller
and are considering the use of DCPromo to accomplish this. Anybody have
comments regarding their experience changing the Domain Controller roles
on an active SQL server? We've all seen problems in the past monkeying
with core components on stable systems...
Thanks in advance.It is generally not recommende to put SQL on a domain controller ( because
of potential security issues and the DC is likely busy anyway.)
however, the thing that comes to mind is that when the box gets promoted to
a DC, the Domain Controller Security policy now applies to the machine in
addition to the local policies...
--
Wayne Snyder MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
(Please respond only to the newsgroups.)
I support the Professional Association for SQL Server
(www.sqlpass.org)
"Rusty" <aid940one@.nospam.ohwhocares.com> wrote in message
news:40193732.7020809@.nospam.ohwhocares.com...
> We're planning to make our SQL server act as a passive domain controller
> and are considering the use of DCPromo to accomplish this. Anybody have
> comments regarding their experience changing the Domain Controller roles
> on an active SQL server? We've all seen problems in the past monkeying
> with core components on stable systems...
> Thanks in advance.
>
and are considering the use of DCPromo to accomplish this. Anybody have
comments regarding their experience changing the Domain Controller roles
on an active SQL server? We've all seen problems in the past monkeying
with core components on stable systems...
Thanks in advance.It is generally not recommende to put SQL on a domain controller ( because
of potential security issues and the DC is likely busy anyway.)
however, the thing that comes to mind is that when the box gets promoted to
a DC, the Domain Controller Security policy now applies to the machine in
addition to the local policies...
--
Wayne Snyder MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
(Please respond only to the newsgroups.)
I support the Professional Association for SQL Server
(www.sqlpass.org)
"Rusty" <aid940one@.nospam.ohwhocares.com> wrote in message
news:40193732.7020809@.nospam.ohwhocares.com...
> We're planning to make our SQL server act as a passive domain controller
> and are considering the use of DCPromo to accomplish this. Anybody have
> comments regarding their experience changing the Domain Controller roles
> on an active SQL server? We've all seen problems in the past monkeying
> with core components on stable systems...
> Thanks in advance.
>
订阅：
博文 (Atom)