Enterprise Mgr Problem in 2000 (Please HELP!)

Typically when I bring up Enterprise Mgr, I get the options to look at the databases, tables, etc. Now, when I choose EM, it brings up the Microsoft Management Console without anything in it except 'Console', 'Window', and 'Help'. When I open a new window, I can see the databases etc. but the top of the window says 'SQL Server Enterprise Manager [2:Console Root\Microsoft SQL Servers]' and a few of the icons are grayed out like 'New Database', 'New Login', and 'New Job'. I haven't changed anything that I know of. Please Help!

thx

Kat

One of the easy ways to fix this is to re run the install of the cliet tools from the server instal disk.

|||

fyi, the reinstallation worked. Also, working on an older pc without much space probably caused the problem.

thx,

Kat

Enterprise Mgr as an end-user data manipulation tool

As DBAs we typically restrict the use of Enterprise Manager and other DBA
Admin type utilities from end-users. Even with a user's SQL server
permissions being appropriately defined and restricted, to limit their
abilities within Enterprise Manager, I typically do not allow end users to
use Enterprise Manager, for the same reason that an Exchange administrator
doesn't allow end-users to run Exchange Administrator to manage their
mailbox. It's an administration utility and is not intended as a data
manipulation interface.
I am faced with a unique situation where a 'power user' insists on wanting
to use SQL Enterprise Manager to access a particular database to which he has
read/write permissions to the production data, as he wants to browse and
modify data ad-hoc within the Enterprise Manager GUI (by right-clicking on a
table and selecting the 'Open, Return All Rows', etc. Due to political
reasons beyond my control, it appears that I will be 'told' to let him use
Enterprise Manager by upper management, so that the user can manage the data
via SQL EM.
Outside of the technical reasons why an end-user should not be using SQL
Enterprise Manager as the GUI to manage data within a database, even with
proper security, does anyone know of official audit guidelines that would
raise a 'red flag' if an audit determined that an end-user(s) were managing
data via SQL Enterprise Manager?
Thanks
D
Apart from read/write to certain tables in the DB, what other rights does
this user have within the server and database? The fact that an end-user
can (knowingly or not), if their rights aren't severely restricted, drop a
table, access and modify security/login info, modify/overwrite/delete
backups, add/remove indexes, etc. would make me wary.
Maybe you can suggest to them that this guy use Access as the front end, and
Link the tables he needs into Access so he can edit to his heart's content
without getting anywhere near EM?
"DBADave" <DBADave@.discussions.microsoft.com> wrote in message
news:D8E94FA5-3F83-4B63-9EFA-1A65F14C1857@.microsoft.com...
> As DBAs we typically restrict the use of Enterprise Manager and other DBA
> Admin type utilities from end-users. Even with a user's SQL server
> permissions being appropriately defined and restricted, to limit their
> abilities within Enterprise Manager, I typically do not allow end users to
> use Enterprise Manager, for the same reason that an Exchange administrator
> doesn't allow end-users to run Exchange Administrator to manage their
> mailbox. It's an administration utility and is not intended as a data
> manipulation interface.
> I am faced with a unique situation where a 'power user' insists on wanting
> to use SQL Enterprise Manager to access a particular database to which he
> has
> read/write permissions to the production data, as he wants to browse and
> modify data ad-hoc within the Enterprise Manager GUI (by right-clicking on
> a
> table and selecting the 'Open, Return All Rows', etc. Due to political
> reasons beyond my control, it appears that I will be 'told' to let him use
> Enterprise Manager by upper management, so that the user can manage the
> data
> via SQL EM.
> Outside of the technical reasons why an end-user should not be using SQL
> Enterprise Manager as the GUI to manage data within a database, even with
> proper security, does anyone know of official audit guidelines that would
> raise a 'red flag' if an audit determined that an end-user(s) were
> managing
> data via SQL Enterprise Manager?
> Thanks
> D

Enterprise Mgr as an end-user data manipulation tool

As DBAs we typically restrict the use of Enterprise Manager and other DBA
Admin type utilities from end-users. Even with a user's SQL server
permissions being appropriately defined and restricted, to limit their
abilities within Enterprise Manager, I typically do not allow end users to
use Enterprise Manager, for the same reason that an Exchange administrator
doesn't allow end-users to run Exchange Administrator to manage their
mailbox. It's an administration utility and is not intended as a data
manipulation interface.
I am faced with a unique situation where a 'power user' insists on wanting
to use SQL Enterprise Manager to access a particular database to which he ha
s
read/write permissions to the production data, as he wants to browse and
modify data ad-hoc within the Enterprise Manager GUI (by right-clicking on a
table and selecting the 'Open, Return All Rows', etc. Due to political
reasons beyond my control, it appears that I will be 'told' to let him use
Enterprise Manager by upper management, so that the user can manage the data
via SQL EM.
Outside of the technical reasons why an end-user should not be using SQL
Enterprise Manager as the GUI to manage data within a database, even with
proper security, does anyone know of official audit guidelines that would
raise a 'red flag' if an audit determined that an end-user(s) were managing
data via SQL Enterprise Manager?
Thanks
DApart from read/write to certain tables in the DB, what other rights does
this user have within the server and database? The fact that an end-user
can (knowingly or not), if their rights aren't severely restricted, drop a
table, access and modify security/login info, modify/overwrite/delete
backups, add/remove indexes, etc. would make me wary.
Maybe you can suggest to them that this guy use Access as the front end, and
Link the tables he needs into Access so he can edit to his heart's content
without getting anywhere near EM?
"DBADave" <DBADave@.discussions.microsoft.com> wrote in message
news:D8E94FA5-3F83-4B63-9EFA-1A65F14C1857@.microsoft.com...
> As DBAs we typically restrict the use of Enterprise Manager and other DBA
> Admin type utilities from end-users. Even with a user's SQL server
> permissions being appropriately defined and restricted, to limit their
> abilities within Enterprise Manager, I typically do not allow end users to
> use Enterprise Manager, for the same reason that an Exchange administrator
> doesn't allow end-users to run Exchange Administrator to manage their
> mailbox. It's an administration utility and is not intended as a data
> manipulation interface.
> I am faced with a unique situation where a 'power user' insists on wanting
> to use SQL Enterprise Manager to access a particular database to which he
> has
> read/write permissions to the production data, as he wants to browse and
> modify data ad-hoc within the Enterprise Manager GUI (by right-clicking on
> a
> table and selecting the 'Open, Return All Rows', etc. Due to political
> reasons beyond my control, it appears that I will be 'told' to let him use
> Enterprise Manager by upper management, so that the user can manage the
> data
> via SQL EM.
> Outside of the technical reasons why an end-user should not be using SQL
> Enterprise Manager as the GUI to manage data within a database, even with
> proper security, does anyone know of official audit guidelines that would
> raise a 'red flag' if an audit determined that an end-user(s) were
> managing
> data via SQL Enterprise Manager?
> Thanks
> D

Enterprise Manager in version 2000

Typically when I bring up Enterprise Mgr, I get the options to look at the databases, tables, etc. Now, when I choose EM, it brings up the Microsoft Management Console without anything in it except 'Console', 'Window', and 'Help'. When I open a new window, I can see the databases etc. but the top of the window says 'SQL Server Enterprise Manager [2:Console Root\Microsoft SQL Servers]' and a few of the icons are grayed out like 'New Database', 'New Login', and 'New Job'. I haven't changed anything that I know of. Please Help!

thx

Kat

A reinstallation of SQL Server solved the problem. I think it came up because I'm working on an old laptop while my newer one is getting fixed. Not much space, memory, and it is slow. Oh, the joy of technology and the obsolescence of all machines...

Kat

Enterprise Manager - Database list hangs

I have this problem on a couple of machines, where when I expand the
Database list under the server (typically the local server, i.e. the one EM
is installed on) it takes a very long time to respond and sometimes hangs
for over 10 minutes.
The only KB article I could find was referring to a problem with a large
number of databases, whereas these only have about 10-20 databases on them.
I assume it's some sort of name resolution problem - any ideas how to debug
what's happening?
Paul
See of you have ODBC tracing turned on...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Paul Hatcher" <phatcher@.nospam.cix.co.uk> wrote in message
news:%23zkR9x0wFHA.2924@.TK2MSFTNGP15.phx.gbl...
>I have this problem on a couple of machines, where when I expand the Database list under the server
>(typically the local server, i.e. the one EM is installed on) it takes a very long time to respond
>and sometimes hangs for over 10 minutes.
> The only KB article I could find was referring to a problem with a large number of databases,
> whereas these only have about 10-20 databases on them.
> I assume it's some sort of name resolution problem - any ideas how to debug what's happening?
> Paul
>
|||Tibor, thanks but no cigar - not turned on.
I'll try using the profiler any see if I can see anything - there's no
obvious CPU actvitity whilst it's hanging so I think it might be down to
networking issues of some sort.
Paul
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:ObaZv60wFHA.720@.TK2MSFTNGP10.phx.gbl...
> See of you have ODBC tracing turned on...
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Paul Hatcher" <phatcher@.nospam.cix.co.uk> wrote in message
> news:%23zkR9x0wFHA.2924@.TK2MSFTNGP15.phx.gbl...
>
|||Also make sure autoclose is turned off for the databases and
that you have applied the latest service packs on the client
where Enterprise Manager seems to hang. There were some
fixes for the issue you described in one of the service
packs.
-Sue
On Thu, 29 Sep 2005 10:24:30 +0100, "Paul Hatcher"
<phatcher@.nospam.cix.co.uk> wrote:

>Tibor, thanks but no cigar - not turned on.
>I'll try using the profiler any see if I can see anything - there's no
>obvious CPU actvitity whilst it's hanging so I think it might be down to
>networking issues of some sort.
>Paul
>"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
>message news:ObaZv60wFHA.720@.TK2MSFTNGP10.phx.gbl...
>
|||Paul
Check the service pack version of Enterprise Manager. There was a bug in an
earlier build (before sp3) where EM did a self join of sysdatabases, and if
that was combined with the autoclose option as Sue suggested, it could take
a LONG time to open the list. Make sure you check the version of the tools
on the client machine, not the version of the server. Sometimes people
forget to apply a sp to all the clients.
HTH
Kalen Delaney, SQL Server MVP
www.solidqualitylearning.com
"Paul Hatcher" <phatcher@.nospam.cix.co.uk> wrote in message
news:%23zkR9x0wFHA.2924@.TK2MSFTNGP15.phx.gbl...
>I have this problem on a couple of machines, where when I expand the
>Database list under the server (typically the local server, i.e. the one EM
>is installed on) it takes a very long time to respond and sometimes hangs
>for over 10 minutes.
> The only KB article I could find was referring to a problem with a large
> number of databases, whereas these only have about 10-20 databases on
> them.
> I assume it's some sort of name resolution problem - any ideas how to
> debug what's happening?
> Paul
>