Entreprise Manager behaviour

Dear all,
I've got the following scenario:
-Got two EM instances running at the same time. The same view on the right
for both, this is, Tables.
From EM1 I create a table called T. After that I'm going to EM2 and refresh.
Fine because I am seeing the same object.
-Come back to EM1 and drop T object and create again another T object but
different, with more fields. When this time I'm going to EM2 and I do drop
action I've dropped the most new object not the old one when I was waiting a
messagebox or something like that warning me that I am deleting an object
which is different than I though.
Jezz, how can I do for to change this behaviour?
Any help or comment woud be very appreciated.
Current location: Alicante (ES)The behaviour you describe is exactly os should be expected.
When you drop a table in EM, EM actually executes a T-SQL drop table
statement.
"Enric" <vtam13@.terra.es.(donotspam)> wrote in message
news:633618A6-5345-4F82-B27F-4C362546AA93@.microsoft.com...
> Dear all,
> I've got the following scenario:
> -Got two EM instances running at the same time. The same view on the right
> for both, this is, Tables.
> From EM1 I create a table called T. After that I'm going to EM2 and
> refresh.
> Fine because I am seeing the same object.
> -Come back to EM1 and drop T object and create again another T object but
> different, with more fields. When this time I'm going to EM2 and I do drop
> action I've dropped the most new object not the old one when I was waiting
> a
> messagebox or something like that warning me that I am deleting an object
> which is different than I though.
> Jezz, how can I do for to change this behaviour?
> Any help or comment woud be very appreciated.
> --
> Current location: Alicante (ES)|||Hi Stephany,
Yes, I perfectly know it, but I was wondering myself how to change
thanks anyway
--
Current location: Alicante (ES)
"Stephany Young" wrote:

> The behaviour you describe is exactly os should be expected.
> When you drop a table in EM, EM actually executes a T-SQL drop table
> statement.
>
> "Enric" <vtam13@.terra.es.(donotspam)> wrote in message
> news:633618A6-5345-4F82-B27F-4C362546AA93@.microsoft.com...
>
>|||> Jezz, how can I do for to change this behaviour?
Stop using EM at all :-))
"Enric" <vtam13@.terra.es.(donotspam)> wrote in message
news:633618A6-5345-4F82-B27F-4C362546AA93@.microsoft.com...
> Dear all,
> I've got the following scenario:
> -Got two EM instances running at the same time. The same view on the right
> for both, this is, Tables.
> From EM1 I create a table called T. After that I'm going to EM2 and
> refresh.
> Fine because I am seeing the same object.
> -Come back to EM1 and drop T object and create again another T object but
> different, with more fields. When this time I'm going to EM2 and I do drop
> action I've dropped the most new object not the old one when I was waiting
> a
> messagebox or something like that warning me that I am deleting an object
> which is different than I though.
> Jezz, how can I do for to change this behaviour?
> Any help or comment woud be very appreciated.
> --
> Current location: Alicante (ES)|||What would you like to change? Do you want to drop objects without actually
dropping them?
What are you trying to achieve?
ML
http://milambda.blogspot.com/|||In fact, I hope that in early period of time EM will be living and sharing
time with Sql Management Studio
--
Current location: Alicante (ES)
"Uri Dimant" wrote:

> Stop using EM at all :-))
> "Enric" <vtam13@.terra.es.(donotspam)> wrote in message
> news:633618A6-5345-4F82-B27F-4C362546AA93@.microsoft.com...
>
>|||No, I hope that EM works fine. Did it make sense such scenario? I think so.
--
Current location: Alicante (ES)
"ML" wrote:

> What would you like to change? Do you want to drop objects without actuall
y
> dropping them?
> What are you trying to achieve?
> ML
> --
> http://milambda.blogspot.com/|||Great, trade in your Yugo for a Kia. Management Studio is certainly a
better tool than Enterprise Manager in general, but it still shares a lot of
its flaws and limitations.
Hopefully, at least, you'll learn commands like DROP TABLE and BEGIN TRAN /
COMMIT TRAN, instead of pointing and clicking yourself to inevitable
disaster.

> In fact, I hope that in early period of time EM will be living and sharing
> time with Sql Management Studio|||drop and commit? I unfortunately know them
--
Current location: Alicante (ES)
"Aaron Bertrand [SQL Server MVP]" wrote:

> Great, trade in your Yugo for a Kia. Management Studio is certainly a
> better tool than Enterprise Manager in general, but it still shares a lot
of
> its flaws and limitations.
> Hopefully, at least, you'll learn commands like DROP TABLE and BEGIN TRAN
/
> COMMIT TRAN, instead of pointing and clicking yourself to inevitable
> disaster.
>
>
>
>
>
>|||> drop and commit? I unfortunately know them
Well, I should have said, learn to use them. I would much rather write DROP
TABLE and/or wrap my commands in transactions than blindly trust what some
GUI is going to do. Especially when I'm doing some backhanded thing like
just trying to see what will happen when I bounce quickly between two open
apps on the same machine...
A

Enterprise Manager Behaviour for SQL 2000

Thanks in Advance,
I am seeing a strange behavior in the query interface on EM that is
new for me, and it has only occurred in a new environment. So I
believe that this is a configuration setting that one of you can point
out to me.
We I have multiple query windows open, if I turn my attention to
another task in remote desktop, the reminder that a query window has
not been in use for sometime pops up and asks if it can clear the
results. In this environment, that window somehow gets trapped behind
the query windows. This creates a catch 22. I cannot move the focus
to close any of the query windows to reveal the system message, and I
cannot get to the system message to allow me to move the focus.
Is there a configuration solution here?
Mark Simmerman
Napa, CADon't use "Open Table" in Enterprise Manager. Run a SELECT query in Query
Analyzer.
In Enteprise Manager, you are maintaining an association with the source
table (so that you can treat SQL Server like Excel, and edit a "cell"), and
this causes resource drain no matter how long you let it sit there.
<xxxdbaxxx@.gmail.com> wrote in message
news:1170262471.222466.129540@.l53g2000cwa.googlegroups.com...
> Thanks in Advance,
> I am seeing a strange behavior in the query interface on EM that is
> new for me, and it has only occurred in a new environment. So I
> believe that this is a configuration setting that one of you can point
> out to me.
> We I have multiple query windows open, if I turn my attention to
> another task in remote desktop, the reminder that a query window has
> not been in use for sometime pops up and asks if it can clear the
> results. In this environment, that window somehow gets trapped behind
> the query windows. This creates a catch 22. I cannot move the focus
> to close any of the query windows to reveal the system message, and I
> cannot get to the system message to allow me to move the focus.
> Is there a configuration solution here?
> Mark Simmerman
> Napa, CA
>|||On Jan 31, 10:52 am, "Aaron Bertrand [SQL Server MVP]"
<ten...@.dnartreb.noraa> wrote:
> Don't use "Open Table" in Enterprise Manager. Run a SELECT query in Query
> Analyzer.
> In Enteprise Manager, you are maintaining an association with the source
> table (so that you can treat SQL Server like Excel, and edit a "cell"), and
> this causes resource drain no matter how long you let it sit there.
> <xxxdba...@.gmail.com> wrote in message
> news:1170262471.222466.129540@.l53g2000cwa.googlegroups.com...
>
> > Thanks in Advance,
> > I am seeing a strange behavior in the query interface on EM that is
> > new for me, and it has only occurred in a new environment. So I
> > believe that this is a configuration setting that one of you can point
> > out to me.
> > We I have multiple query windows open, if I turn my attention to
> > another task in remote desktop, the reminder that a query window has
> > not been in use for sometime pops up and asks if it can clear the
> > results. In this environment, that window somehow gets trapped behind
> > the query windows. This creates a catch 22. I cannot move the focus
> > to close any of the query windows to reveal the system message, and I
> > cannot get to the system message to allow me to move the focus.
> > Is there a configuration solution here?
> > Mark Simmerman
> > Napa, CA- Hide quoted text -
> - Show quoted text -
OK. Other than telling me to use another tool (in SQL 2005 they are
one and the same), is there any solution or configuration setting that
can address this?
Mark|||> OK. Other than telling me to use another tool (in SQL 2005 they are
> one and the same),
Yes, but you still have different options, like Open Table (bad), and query
windows (good).
> is there any solution or configuration setting that
> can address this?
Not that I know of.|||xxxdbaxxx@.gmail.com wrote:
> OK. Other than telling me to use another tool (in SQL 2005 they are
> one and the same), is there any solution or configuration setting that
> can address this?
> Mark
>
No, they're not really "one and the same". You can "open" tables using
a GUI, ala Enterprise Manager, or you can query them properly ala Query
Analyzer. The only difference in 2005 is that you don't "launch" two
seperate applications.
The limitations are the same - opening a table through the GUI is a
heavy process, prone to blocking. The GUI tools are acceptable for a
development environment, but should not be used against a production
system. Manipulating your tables properly, using T-SQL commands, is the
preferred method.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||On Feb 1, 7:34 am, Tracy McKibben <t...@.realsqlguy.com> wrote:
> xxxdba...@.gmail.com wrote:
> > OK. Other than telling me to use another tool (in SQL 2005 they are
> > one and the same), is there any solution or configuration setting that
> > can address this?
> > Mark
> No, they're not really "one and the same". You can "open" tables using
> a GUI, ala Enterprise Manager, or you can query them properly ala Query
> Analyzer. The only difference in 2005 is that you don't "launch" two
> seperate applications.
> The limitations are the same - opening a table through the GUI is a
> heavy process, prone to blocking. The GUI tools are acceptable for a
> development environment, but should not be used against a production
> system. Manipulating your tables properly, using T-SQL commands, is the
> preferred method.
> --
> Tracy McKibben
> MCDBAhttp://www.realsqlguy.com
OK. I am in a development environment. I would still like to know if
anyone has an answer to the question. It is an annoying behavior on
the part of the GUI. Do you guys get points for non-responsive
responses?
Mark|||> OK. I am in a development environment. I would still like to know if
> anyone has an answer to the question. It is an annoying behavior on
> the part of the GUI. Do you guys get points for non-responsive
> responses?
We don't get "points" for anything. We are here, volunteering our time to
help other people solve problems we might have insight on. Every once in a
while, the recipients feigns appreciation.
If "not that I know of" is not responsive enough for you, then maybe you
know of a better place to get more responsive answers, and should try there.
<shrug><sigh><resisting smacking own forehead>

Enterprise Manager Behaviour for SQL 2000

Thanks in Advance,
I am seeing a strange behavior in the query interface on EM that is
new for me, and it has only occurred in a new environment. So I
believe that this is a configuration setting that one of you can point
out to me.
We I have multiple query windows open, if I turn my attention to
another task in remote desktop, the reminder that a query window has
not been in use for sometime pops up and asks if it can clear the
results. In this environment, that window somehow gets trapped behind
the query windows. This creates a catch 22. I cannot move the focus
to close any of the query windows to reveal the system message, and I
cannot get to the system message to allow me to move the focus.
Is there a configuration solution here?
Mark Simmerman
Napa, CA
Don't use "Open Table" in Enterprise Manager. Run a SELECT query in Query
Analyzer.
In Enteprise Manager, you are maintaining an association with the source
table (so that you can treat SQL Server like Excel, and edit a "cell"), and
this causes resource drain no matter how long you let it sit there.
<xxxdbaxxx@.gmail.com> wrote in message
news:1170262471.222466.129540@.l53g2000cwa.googlegr oups.com...
> Thanks in Advance,
> I am seeing a strange behavior in the query interface on EM that is
> new for me, and it has only occurred in a new environment. So I
> believe that this is a configuration setting that one of you can point
> out to me.
> We I have multiple query windows open, if I turn my attention to
> another task in remote desktop, the reminder that a query window has
> not been in use for sometime pops up and asks if it can clear the
> results. In this environment, that window somehow gets trapped behind
> the query windows. This creates a catch 22. I cannot move the focus
> to close any of the query windows to reveal the system message, and I
> cannot get to the system message to allow me to move the focus.
> Is there a configuration solution here?
> Mark Simmerman
> Napa, CA
>
|||On Jan 31, 10:52 am, "Aaron Bertrand [SQL Server MVP]"
<ten...@.dnartreb.noraa> wrote:
> Don't use "Open Table" in Enterprise Manager. Run a SELECT query in Query
> Analyzer.
> In Enteprise Manager, you are maintaining an association with the source
> table (so that you can treat SQL Server like Excel, and edit a "cell"), and
> this causes resource drain no matter how long you let it sit there.
> <xxxdba...@.gmail.com> wrote in message
> news:1170262471.222466.129540@.l53g2000cwa.googlegr oups.com...
>
>
>
>
> - Show quoted text -
OK. Other than telling me to use another tool (in SQL 2005 they are
one and the same), is there any solution or configuration setting that
can address this?
Mark
|||> OK. Other than telling me to use another tool (in SQL 2005 they are
> one and the same),
Yes, but you still have different options, like Open Table (bad), and query
windows (good).

> is there any solution or configuration setting that
> can address this?
Not that I know of.
|||xxxdbaxxx@.gmail.com wrote:
> OK. Other than telling me to use another tool (in SQL 2005 they are
> one and the same), is there any solution or configuration setting that
> can address this?
> Mark
>
No, they're not really "one and the same". You can "open" tables using
a GUI, ala Enterprise Manager, or you can query them properly ala Query
Analyzer. The only difference in 2005 is that you don't "launch" two
seperate applications.
The limitations are the same - opening a table through the GUI is a
heavy process, prone to blocking. The GUI tools are acceptable for a
development environment, but should not be used against a production
system. Manipulating your tables properly, using T-SQL commands, is the
preferred method.
Tracy McKibben
MCDBA
http://www.realsqlguy.com
|||On Feb 1, 7:34 am, Tracy McKibben <t...@.realsqlguy.com> wrote:
> xxxdba...@.gmail.com wrote:
>
> No, they're not really "one and the same". You can "open" tables using
> a GUI, ala Enterprise Manager, or you can query them properly ala Query
> Analyzer. The only difference in 2005 is that you don't "launch" two
> seperate applications.
> The limitations are the same - opening a table through the GUI is a
> heavy process, prone to blocking. The GUI tools are acceptable for a
> development environment, but should not be used against a production
> system. Manipulating your tables properly, using T-SQL commands, is the
> preferred method.
> --
> Tracy McKibben
> MCDBAhttp://www.realsqlguy.com
OK. I am in a development environment. I would still like to know if
anyone has an answer to the question. It is an annoying behavior on
the part of the GUI. Do you guys get points for non-responsive
responses?
Mark
|||> OK. I am in a development environment. I would still like to know if
> anyone has an answer to the question. It is an annoying behavior on
> the part of the GUI. Do you guys get points for non-responsive
> responses?
We don't get "points" for anything. We are here, volunteering our time to
help other people solve problems we might have insight on. Every once in a
while, the recipients feigns appreciation.
If "not that I know of" is not responsive enough for you, then maybe you
know of a better place to get more responsive answers, and should try there.
<shrug><sigh><resisting smacking own forehead>

Enterprise Manager Behaviour for SQL 2000

Thanks in Advance,
I am seeing a strange behavior in the query interface on EM that is
new for me, and it has only occurred in a new environment. So I
believe that this is a configuration setting that one of you can point
out to me.
We I have multiple query windows open, if I turn my attention to
another task in remote desktop, the reminder that a query window has
not been in use for sometime pops up and asks if it can clear the
results. In this environment, that window somehow gets trapped behind
the query windows. This creates a catch 22. I cannot move the focus
to close any of the query windows to reveal the system message, and I
cannot get to the system message to allow me to move the focus.
Is there a configuration solution here?
Mark Simmerman
Napa, CADon't use "Open Table" in Enterprise Manager. Run a SELECT query in Query
Analyzer.
In Enteprise Manager, you are maintaining an association with the source
table (so that you can treat SQL Server like Excel, and edit a "cell"), and
this causes resource drain no matter how long you let it sit there.
<xxxdbaxxx@.gmail.com> wrote in message
news:1170262471.222466.129540@.l53g2000cwa.googlegroups.com...
> Thanks in Advance,
> I am seeing a strange behavior in the query interface on EM that is
> new for me, and it has only occurred in a new environment. So I
> believe that this is a configuration setting that one of you can point
> out to me.
> We I have multiple query windows open, if I turn my attention to
> another task in remote desktop, the reminder that a query window has
> not been in use for sometime pops up and asks if it can clear the
> results. In this environment, that window somehow gets trapped behind
> the query windows. This creates a catch 22. I cannot move the focus
> to close any of the query windows to reveal the system message, and I
> cannot get to the system message to allow me to move the focus.
> Is there a configuration solution here?
> Mark Simmerman
> Napa, CA
>|||On Jan 31, 10:52 am, "Aaron Bertrand [SQL Server MVP]"
<ten...@.dnartreb.noraa> wrote:
> Don't use "Open Table" in Enterprise Manager. Run a SELECT query in Query
> Analyzer.
> In Enteprise Manager, you are maintaining an association with the source
> table (so that you can treat SQL Server like Excel, and edit a "cell"), an
d
> this causes resource drain no matter how long you let it sit there.
> <xxxdba...@.gmail.com> wrote in message
> news:1170262471.222466.129540@.l53g2000cwa.googlegroups.com...
>
>
>
>
>
>
> - Show quoted text -
OK. Other than telling me to use another tool (in SQL 2005 they are
one and the same), is there any solution or configuration setting that
can address this?
Mark|||> OK. Other than telling me to use another tool (in SQL 2005 they are
> one and the same),
Yes, but you still have different options, like Open Table (bad), and query
windows (good).

> is there any solution or configuration setting that
> can address this?
Not that I know of.|||xxxdbaxxx@.gmail.com wrote:
> OK. Other than telling me to use another tool (in SQL 2005 they are
> one and the same), is there any solution or configuration setting that
> can address this?
> Mark
>
No, they're not really "one and the same". You can "open" tables using
a GUI, ala Enterprise Manager, or you can query them properly ala Query
Analyzer. The only difference in 2005 is that you don't "launch" two
seperate applications.
The limitations are the same - opening a table through the GUI is a
heavy process, prone to blocking. The GUI tools are acceptable for a
development environment, but should not be used against a production
system. Manipulating your tables properly, using T-SQL commands, is the
preferred method.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||On Feb 1, 7:34 am, Tracy McKibben <t...@.realsqlguy.com> wrote:
> xxxdba...@.gmail.com wrote:
>
>
> No, they're not really "one and the same". You can "open" tables using
> a GUI, ala Enterprise Manager, or you can query them properly ala Query
> Analyzer. The only difference in 2005 is that you don't "launch" two
> seperate applications.
> The limitations are the same - opening a table through the GUI is a
> heavy process, prone to blocking. The GUI tools are acceptable for a
> development environment, but should not be used against a production
> system. Manipulating your tables properly, using T-SQL commands, is the
> preferred method.
> --
> Tracy McKibben
> MCDBAhttp://www.realsqlguy.com
OK. I am in a development environment. I would still like to know if
anyone has an answer to the question. It is an annoying behavior on
the part of the GUI. Do you guys get points for non-responsive
responses?
Mark|||> OK. I am in a development environment. I would still like to know if
> anyone has an answer to the question. It is an annoying behavior on
> the part of the GUI. Do you guys get points for non-responsive
> responses?
We don't get "points" for anything. We are here, volunteering our time to
help other people solve problems we might have insight on. Every once in a
while, the recipients feigns appreciation.
If "not that I know of" is not responsive enough for you, then maybe you
know of a better place to get more responsive answers, and should try there.
<shrug><sigh><resisting smacking own forehead>

Enterprise Manager and its particularities

Dear all,
I'm fed up with this problem. I hate that behaviour.
When I create objects from a query analyser session in my own workstation,
then these objects doesn't visible from my MMC. A lot of times I am obligate
d
to close and open again.
I've got a MMC with 13 Sql Server and some of them are remote but I don't
think that that aspect could to interfere in the response for do a refresh.
In a fact I do highest level refresh but nothing happens, objects such as
views, sp or tables are missing.
It's a waste time. Why on earth is happening this?
Thanks a lot and regards,Enric wrote:
> Dear all,
> I'm fed up with this problem. I hate that behaviour.
> When I create objects from a query analyser session in my own
> workstation, then these objects doesn't visible from my MMC. A lot of
> times I am obligated to close and open again.
> I've got a MMC with 13 Sql Server and some of them are remote but I
> don't think that that aspect could to interfere in the response for
> do a refresh. In a fact I do highest level refresh but nothing
> happens, objects such as views, sp or tables are missing.
> It's a waste time. Why on earth is happening this?
> Thanks a lot and regards,
I've seen a few others post this issue on SQL EM, but most of us here
have not experienced the problem. With me, anyway, a selecting the
Refresh context menu option performs the necessary refresh and the new
objects appear.
Can you document the steps to consistently reproduce the refresh issue
or is this something that does not occur with any consistency?
Also, what version of SQL EM are you using? Check Help | About and post
the full version.
David Gugick
Quest Software
www.imceda.com
www.quest.com|||Enric wrote:
> Dear all,
> I'm fed up with this problem. I hate that behaviour.
> When I create objects from a query analyser session in my own
> workstation, then these objects doesn't visible from my MMC. A lot of
> times I am obligated to close and open again.
> I've got a MMC with 13 Sql Server and some of them are remote but I
> don't think that that aspect could to interfere in the response for
> do a refresh. In a fact I do highest level refresh but nothing
> happens, objects such as views, sp or tables are missing.
> It's a waste time. Why on earth is happening this?
> Thanks a lot and regards,
Clarification: For the version, just let us know what SQL Server service
pack you've installed on your client. The version appears to only show
the major version, not the SP level.
David Gugick
Quest Software
www.imceda.com
www.quest.com|||What happend if instead closing, you just disconnect and connect agaiin to
the server?
AMB
"Enric" wrote:

> Dear all,
> I'm fed up with this problem. I hate that behaviour.
> When I create objects from a query analyser session in my own workstation,
> then these objects doesn't visible from my MMC. A lot of times I am obliga
ted
> to close and open again.
> I've got a MMC with 13 Sql Server and some of them are remote but I don't
> think that that aspect could to interfere in the response for do a refresh
.
> In a fact I do highest level refresh but nothing happens, objects such as
> views, sp or tables are missing.
> It's a waste time. Why on earth is happening this?
> Thanks a lot and regards,|||You need to refresh at the right level. Don't do the highest level. Refresh
doesn't work "all the
way down". Do refresh on the right container.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Enric" <Enric@.discussions.microsoft.com> wrote in message
news:259BA9D3-01BE-4962-8F1F-86EB413D4C32@.microsoft.com...
> Dear all,
> I'm fed up with this problem. I hate that behaviour.
> When I create objects from a query analyser session in my own workstation,
> then these objects doesn't visible from my MMC. A lot of times I am obliga
ted
> to close and open again.
> I've got a MMC with 13 Sql Server and some of them are remote but I don't
> think that that aspect could to interfere in the response for do a refresh
.
> In a fact I do highest level refresh but nothing happens, objects such as
> views, sp or tables are missing.
> It's a waste time. Why on earth is happening this?
> Thanks a lot and regards,|||EM is not "active" in the sense that it does not sense changes it does not
make. It is an application that initializes iteslf with data, and knows wha
t
IT does, but not what others (Query Analyzer) do until it re-selects data.
If you want to see new tables, right-click on the "tables" tree in the left
pane and select "refresh". Your new tables will now appear. You can refres
h
at various levels, but the higher-up you go, the longer it will take.
"David Gugick" wrote:

> Enric wrote:
> Clarification: For the version, just let us know what SQL Server service
> pack you've installed on your client. The version appears to only show
> the major version, not the SP level.
> --
> David Gugick
> Quest Software
> www.imceda.com
> www.quest.com
>|||Thanks to all for response.
Tibor,
Your fix not always works.
David,
All the SQL SERVERS (2000) own sp3 and sp3a for olap services.
I think that it could be a network problem between domains or something like
that. There are two sql server which are living in an AD environment, the
rest one running under NT Domains.
Well, I also want understand that maybe to have so many servers at the same
time...
"Tibor Karaszi" wrote:

> You need to refresh at the right level. Don't do the highest level. Refres
h doesn't work "all the
> way down". Do refresh on the right container.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Enric" <Enric@.discussions.microsoft.com> wrote in message
> news:259BA9D3-01BE-4962-8F1F-86EB413D4C32@.microsoft.com...
>|||Enric wrote:
> Thanks to all for response.
> Tibor,
> Your fix not always works.
> David,
> All the SQL SERVERS (2000) own sp3 and sp3a for olap services.
> I think that it could be a network problem between domains or
> something like that. There are two sql server which are living in an
> AD environment, the rest one running under NT Domains.
>
Service Packs should be applied to the client as well as the server.
That's why I asked what version you have on the client. You can check
this from Query Analyzer on the client. You should be running 8.00.760
for SP3/SP3a.
It's possible the RTM release of SQL EM had refresh problems.
David Gugick
Quest Software
www.imceda.com
www.quest.com|||Hi
We have in excess of 95 servers in our EM at work, across multiple domains.
The SP is applied to both the servers and client workstations with EM
installed.
Right clicking as described by other posts in this thread works for us 100%
If you have networking problems between domains, you would get errors as the
objects are refreshed out of sysobjects in each database. It either works or
it gives you an error.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Enric" <Enric@.discussions.microsoft.com> wrote in message
news:CFD1B642-341C-4A97-8D0B-DFDBF16C15FF@.microsoft.com...
> Thanks to all for response.
> Tibor,
> Your fix not always works.
> David,
> All the SQL SERVERS (2000) own sp3 and sp3a for olap services.
> I think that it could be a network problem between domains or something
> like
> that. There are two sql server which are living in an AD environment, the
> rest one running under NT Domains.
> Well, I also want understand that maybe to have so many servers at the
> same
> time...
> "Tibor Karaszi" wrote:
>