Hi,
I have a machine that has just SQL2005 (as default instance with no instance
name.) I am trying to list all SQL 2005 server instances on the network usin
g
SmoApplication.EnumAvailableSqlServers( ) and trying to filter the servers
based on version information. This machine shows up in the list, but does no
t
have version information. I saw another post on Sql Server Programming
newgroup without any response. Is this a known bug in SMO? If it is, does
anyone know how I can list SQL2005 servers only on a network that has both
SQL2005 and SQL2000 servers?
Any help is geratly appreciated.SMO in its current implementation uses
SqlDataSourceEnumerator.GetDataSources under the cover (
http://msdn2.microsoft.com/en-us/li...
etdatasources(VS.80).aspx)
Can you try writing calling this instead and see if you get the version?
This can help us isolate the problem.
Thanks,
--
Ciprian Gerea
SDE, SqlServer
This posting is provided "AS IS" with no warranties, and confers no rights.
"Raghu" <Raghu@.discussions.microsoft.com> wrote in message
news:7EB858DE-22E5-41B3-B46A-1D8229406630@.microsoft.com...
> Hi,
> I have a machine that has just SQL2005 (as default instance with no
> instance
> name.) I am trying to list all SQL 2005 server instances on the network
> using
> SmoApplication.EnumAvailableSqlServers( ) and trying to filter the servers
> based on version information. This machine shows up in the list, but does
> not
> have version information. I saw another post on Sql Server Programming
> newgroup without any response. Is this a known bug in SMO? If it is, does
> anyone know how I can list SQL2005 servers only on a network that has both
> SQL2005 and SQL2000 servers?
> Any help is geratly appreciated.
Showing posts with label machine. Show all posts
Showing posts with label machine. Show all posts
Tuesday, March 27, 2012
Monday, March 26, 2012
Entity ’ in SQL Server 2000 output
I have an application that queries a SQL Server 2000 db through an ODBC driver on my Win2000 machine.
The DB contains some french text e.g. ltranger stored in a nvarchar column.
When I query the DB the result contains the entity &# 8217; rather than the character itself. I don't want this and it doesn't happen in SQL Server 7.
Tried changing the collation from SQL_Latin1_General_Cp1_CI_AS but with no luck.
Does anyone have experience with this?
ThanksHi,
Did you change collation on the entire dB or on table and column ?
Which collation do you have as standard ?
Regards
Tommy|||Hi,
We've changed the collation of the individual dB/table, but not
the collation of the server (which is still SQL_Latin1_General_CP1_CI_AS), so as not to affect other dBs.
Is it likely to be a collation issue?|||Hi,
I'm not sure about that. I've tried to insert that text into a table with collation SQL_Latin1_General_CP1_CI_AS and the result in query analyzer is correct, have you tried select "column" from "table".
Is the result the same ?
Where did the dB data come from ?
You may check how it's inserted into the dB.
Let me know !
Tommy|||Hi,
Thanks for taking an interest.
The original data is probably generated in some Microsoft applications i.e. Word. I have no control over that.
Yes, the results look okay in query analyser, the problem occurs when I do SQL calls through an ODBC driver from a remote machine.
I don't think it's a driver problem because I get the correct characters when testing on SQL Server 7.
What has changed between 7 and 2000?
Help|||Ok,
That's a tricky one..
One of the things that changed in SQL 2000 is collations (the possibility to set collations on dB, tables and columns not just on the server).
and sometimes just change the collation on the table or columns or only the dB just ain't enough.
Some things you can do is:
Check the application, how/what does it when querying the dB, how do the question look like. (run SQL profiler) if you can't look in the code.
The collation on SQL 7 ?
How did you do the switch from SQL 7 to 2000 ?
Regional settings on the client. (? ? I'm not sure about this)
Anyone else have a succession ?
I can send you a proc that handles collations if you'll like.
Regards
Tommy|||Hi,
Basically we just send an SQLExecute command with a SELECT statement.
Of course I can parse out the & #8217 from the results but surely I shouldn't need to? (And also what about any other entities I may encounter?)
Anyway, thanks for the suggestions
The DB contains some french text e.g. ltranger stored in a nvarchar column.
When I query the DB the result contains the entity &# 8217; rather than the character itself. I don't want this and it doesn't happen in SQL Server 7.
Tried changing the collation from SQL_Latin1_General_Cp1_CI_AS but with no luck.
Does anyone have experience with this?
ThanksHi,
Did you change collation on the entire dB or on table and column ?
Which collation do you have as standard ?
Regards
Tommy|||Hi,
We've changed the collation of the individual dB/table, but not
the collation of the server (which is still SQL_Latin1_General_CP1_CI_AS), so as not to affect other dBs.
Is it likely to be a collation issue?|||Hi,
I'm not sure about that. I've tried to insert that text into a table with collation SQL_Latin1_General_CP1_CI_AS and the result in query analyzer is correct, have you tried select "column" from "table".
Is the result the same ?
Where did the dB data come from ?
You may check how it's inserted into the dB.
Let me know !
Tommy|||Hi,
Thanks for taking an interest.
The original data is probably generated in some Microsoft applications i.e. Word. I have no control over that.
Yes, the results look okay in query analyser, the problem occurs when I do SQL calls through an ODBC driver from a remote machine.
I don't think it's a driver problem because I get the correct characters when testing on SQL Server 7.
What has changed between 7 and 2000?
Help|||Ok,
That's a tricky one..
One of the things that changed in SQL 2000 is collations (the possibility to set collations on dB, tables and columns not just on the server).
and sometimes just change the collation on the table or columns or only the dB just ain't enough.
Some things you can do is:
Check the application, how/what does it when querying the dB, how do the question look like. (run SQL profiler) if you can't look in the code.
The collation on SQL 7 ?
How did you do the switch from SQL 7 to 2000 ?
Regional settings on the client. (? ? I'm not sure about this)
Anyone else have a succession ?
I can send you a proc that handles collations if you'll like.
Regards
Tommy|||Hi,
Basically we just send an SQLExecute command with a SELECT statement.
Of course I can parse out the & #8217 from the results but surely I shouldn't need to? (And also what about any other entities I may encounter?)
Anyway, thanks for the suggestions
Enterprise to Standard downgrade
We have a SQL 2000 server running Enterprise Edition. We also have a separate machine running SQL 2000, Standard edition. We then detached the database from the Enterprise server, copied the MDF and LDF files to the Standard server and reattached. Currently, a program running on the Standard Edition server is returning an error message when trying to access "systables". The questions are as follows:
1) is this error a result of the copy process?
2) is this a recoverable error, and if so, how?
3) are there any other problems and side-effects of which we need to be aware?I have moved databases between Standard and Enterprise several times before, and not had this issue, so it can be done. Without any other information, I can only guess as to why this is happening, but here is my guess:
The user-account being used by the program that is throwing the error probably has a different default database setting than on the Enterprise version. In other words, UserX on the Enterprise server probably has a default database pointing to the application database, and on the Standard edition has a default database of something like Master.
This would cause a problem in implicit database references. If the program issues a command like SELECT * FROM systables, thinking it is going to automatically be pointing to the application database, but is actually pointing to something else, it will not be able to find systables. The proper syntax for the query would explicitly state the table name SELECT * FROM [dbname].dbo.systables, in which case the default database setting of the user would not affect the code.|||The default database for the user is the same on both servers. Any other ideas? Is there any other information I could give that might be of assistance?
Originally posted by bpdWork
I have moved databases between Standard and Enterprise several times before, and not had this issue, so it can be done. Without any other information, I can only guess as to why this is happening, but here is my guess:
The user-account being used by the program that is throwing the error probably has a different default database setting than on the Enterprise version. In other words, UserX on the Enterprise server probably has a default database pointing to the application database, and on the Standard edition has a default database of something like Master.
This would cause a problem in implicit database references. If the program issues a command like SELECT * FROM systables, thinking it is going to automatically be pointing to the application database, but is actually pointing to something else, it will not be able to find systables. The proper syntax for the query would explicitly state the table name SELECT * FROM [dbname].dbo.systables, in which case the default database setting of the user would not affect the code.|||1) Are you sure the database you moved has the table systables, and that it is not in a different database?
2) Does the user account being used by the application have SELECT (etc) permissions for the table?
The exact error message might be helpful.|||check the service pack level|||We've found the issue. Basically, an error was made during the installation of the software. To everyone, thanks for the help.
1) is this error a result of the copy process?
2) is this a recoverable error, and if so, how?
3) are there any other problems and side-effects of which we need to be aware?I have moved databases between Standard and Enterprise several times before, and not had this issue, so it can be done. Without any other information, I can only guess as to why this is happening, but here is my guess:
The user-account being used by the program that is throwing the error probably has a different default database setting than on the Enterprise version. In other words, UserX on the Enterprise server probably has a default database pointing to the application database, and on the Standard edition has a default database of something like Master.
This would cause a problem in implicit database references. If the program issues a command like SELECT * FROM systables, thinking it is going to automatically be pointing to the application database, but is actually pointing to something else, it will not be able to find systables. The proper syntax for the query would explicitly state the table name SELECT * FROM [dbname].dbo.systables, in which case the default database setting of the user would not affect the code.|||The default database for the user is the same on both servers. Any other ideas? Is there any other information I could give that might be of assistance?
Originally posted by bpdWork
I have moved databases between Standard and Enterprise several times before, and not had this issue, so it can be done. Without any other information, I can only guess as to why this is happening, but here is my guess:
The user-account being used by the program that is throwing the error probably has a different default database setting than on the Enterprise version. In other words, UserX on the Enterprise server probably has a default database pointing to the application database, and on the Standard edition has a default database of something like Master.
This would cause a problem in implicit database references. If the program issues a command like SELECT * FROM systables, thinking it is going to automatically be pointing to the application database, but is actually pointing to something else, it will not be able to find systables. The proper syntax for the query would explicitly state the table name SELECT * FROM [dbname].dbo.systables, in which case the default database setting of the user would not affect the code.|||1) Are you sure the database you moved has the table systables, and that it is not in a different database?
2) Does the user account being used by the application have SELECT (etc) permissions for the table?
The exact error message might be helpful.|||check the service pack level|||We've found the issue. Basically, an error was made during the installation of the software. To everyone, thanks for the help.
Wednesday, March 21, 2012
Enterprise Manager takes 10+ min to open
Hi,
I've got a machine with about 750 databases on it, and growing.
Enterprise Manager is very slow coming up on this machine and I was
wondering what I could do about it. What's it doing, connecting to
every database?What version of SQL are you using? Also indicate the service pack
please.
For one thing make sure you don't have the databases set to autoclose.
>
That can take a long time.
>
>|||Johnny Ruin wrote:
Go in Options and uncheck the "Server state polling" option in the
General tab. Also in you server registration uncheck the "Display SQL
Server state in console" option.
This is the RTM (unpatched) release of SQL Server. I strongly suggest you
consider upgrading to SP4.
>>
>That can take a long time.
>>
>>
>
I've got a machine with about 750 databases on it, and growing.
Enterprise Manager is very slow coming up on this machine and I was
wondering what I could do about it. What's it doing, connecting to
every database?What version of SQL are you using? Also indicate the service pack
please.
Johnny Ruin wrote:
Quote:
Originally Posted by
Hi,
I've got a machine with about 750 databases on it, and growing.
Enterprise Manager is very slow coming up on this machine and I was
wondering what I could do about it. What's it doing, connecting to
every database?
You can start a profiler session, start EM, and just observe what is
going on under the hood.
--------
Alex Kuznetsov
http://sqlserver-tips.blogspot.com/
http://sqlserver-puzzles.blogspot.com/|||"Johnny Ruin" <schafer.dave@.gmail.comwrote in message
news:1161612846.335787.281480@.h48g2000cwc.googlegr oups.com...
Quote:
Originally Posted by
Hi,
I've got a machine with about 750 databases on it, and growing.
Enterprise Manager is very slow coming up on this machine and I was
wondering what I could do about it. What's it doing, connecting to
every database?
For one thing make sure you don't have the databases set to autoclose.
That can take a long time.
Quote:
Originally Posted by
>
Thanks for your replies. I checked the version on the production
machine, it's "Microsoft SQL Server 2000 - 8.00.194 (Intel X86) Aug
6 2000 00:57:48 Copyright (c) 1988-2000 Microsoft Corporation
Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4) "
The profiler idea was a good one. EM goes through it's 16 lines of
'get config stuff' that it does every time it starts, but then it
executes the following query many times. I didn't count the times,
but it looks like it's once per database.
select name, DATABASEPROPERTY(name, N'IsDetached'),
(case when DATABASEPROPERTY(name, N'IsShutdown') is null then -1 else
DATABASEPROPERTY(name, N'IsShutdown') end),
DATABASEPROPERTY(name, N'IsSuspect'),
DATABASEPROPERTY(name, N'IsOffline'),
DATABASEPROPERTY(name, N'IsInLoad'),
(case when DATABASEPROPERTY(name, N'IsInRecovery') is null then -1 else
DATABASEPROPERTY(name, N'IsInRecovery') end),
(case when DATABASEPROPERTY(name, N'IsNotRecovered') is null then -1
else DATABASEPROPERTY(name, N'IsNotRecovered') end),
DATABASEPROPERTY(name, N'IsEmergencyMode'),
DATABASEPROPERTY(name, N'IsInStandBy'),
has_dbaccess(name), status, category, status2 from
master.dbo.sysdatabases
As I paged through the profiler output (can't seem to make that filter
thing work correctly) I realized that a) there's a lot going on this
machine and b) I haven't got a basic sql performance monitoring in my
skill set. I'll work toward that and I'll checkout auto close too.
Thanks again.
On Oct 23, 7:01 pm, "Greg D. Moore \(Strider\)"
<mooregr_deletet...@.greenms.comwrote:
Quote:
Originally Posted by
"Johnny Ruin" <schafer.d...@.gmail.comwrote in messagenews:1161612846.335787.281480@.h48g2000cwc.g ooglegroups.com...
>
Quote:
Originally Posted by
Hi,
I've got a machine with about 750 databases on it, and growing.
Enterprise Manager is very slow coming up on this machine and I was
wondering what I could do about it. What's it doing, connecting to
every database?For one thing make sure you don't have the databases set to autoclose.
>
That can take a long time.
>
>|||Johnny Ruin wrote:
Quote:
Originally Posted by
Hi,
I've got a machine with about 750 databases on it, and growing.
Enterprise Manager is very slow coming up on this machine and I was
wondering what I could do about it. What's it doing, connecting to
every database?
Go in Options and uncheck the "Server state polling" option in the
General tab. Also in you server registration uncheck the "Display SQL
Server state in console" option.
Regards,
lucm|||Thanks for your replies. I checked the version on the production
Quote:
Originally Posted by
machine, it's "Microsoft SQL Server 2000 - 8.00.194 (Intel X86) Aug
6 2000 00:57:48 Copyright (c) 1988-2000 Microsoft Corporation
Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4) "
This is the RTM (unpatched) release of SQL Server. I strongly suggest you
consider upgrading to SP4.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Johnny Ruin" <schafer.dave@.gmail.comwrote in message
news:1161696467.830677.213770@.i42g2000cwa.googlegr oups.com...
Quote:
Originally Posted by
Hi everyone,
>
Thanks for your replies. I checked the version on the production
machine, it's "Microsoft SQL Server 2000 - 8.00.194 (Intel X86) Aug
6 2000 00:57:48 Copyright (c) 1988-2000 Microsoft Corporation
Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4) "
>
The profiler idea was a good one. EM goes through it's 16 lines of
'get config stuff' that it does every time it starts, but then it
executes the following query many times. I didn't count the times,
but it looks like it's once per database.
>
select name, DATABASEPROPERTY(name, N'IsDetached'),
(case when DATABASEPROPERTY(name, N'IsShutdown') is null then -1 else
DATABASEPROPERTY(name, N'IsShutdown') end),
DATABASEPROPERTY(name, N'IsSuspect'),
DATABASEPROPERTY(name, N'IsOffline'),
DATABASEPROPERTY(name, N'IsInLoad'),
(case when DATABASEPROPERTY(name, N'IsInRecovery') is null then -1 else
DATABASEPROPERTY(name, N'IsInRecovery') end),
(case when DATABASEPROPERTY(name, N'IsNotRecovered') is null then -1
else DATABASEPROPERTY(name, N'IsNotRecovered') end),
DATABASEPROPERTY(name, N'IsEmergencyMode'),
DATABASEPROPERTY(name, N'IsInStandBy'),
has_dbaccess(name), status, category, status2 from
master.dbo.sysdatabases
>
As I paged through the profiler output (can't seem to make that filter
thing work correctly) I realized that a) there's a lot going on this
machine and b) I haven't got a basic sql performance monitoring in my
skill set. I'll work toward that and I'll checkout auto close too.
Thanks again.
>
>
>
On Oct 23, 7:01 pm, "Greg D. Moore \(Strider\)"
<mooregr_deletet...@.greenms.comwrote:
Quote:
Originally Posted by
>"Johnny Ruin" <schafer.d...@.gmail.comwrote in
>messagenews:1161612846.335787.281480@.h48g2000cwc.g ooglegroups.com...
>>
Quote:
Originally Posted by
Hi,
I've got a machine with about 750 databases on it, and growing.
Enterprise Manager is very slow coming up on this machine and I was
wondering what I could do about it. What's it doing, connecting to
every database?For one thing make sure you don't have the databases set
to autoclose.
>>
>That can take a long time.
>>
>>
>
Monday, March 19, 2012
Enterprise manager settings migration?
Anyone knows if it is at all possible to Copy or Move the Server Registered under EM to another machine ?
ThanksOriginally posted by aashu
Anyone knows if it is at all possible to Copy or Move the Server Registered under EM to another machine ?
Thanks
but if have the registered server on ur EM then u can just use that to register the same servers on another instance of EM... or you could get the information for the server from the Client Network Utility: ipaddresses, servername etc.|||I am aware of that . Doing for 50 Servers will be a nightmare .. So , back to the question again , is there some ini file or EM setup file I could move over?
Thanks|||I know the information about registered servers is in the registry:
HKEY_CURRENT_USER\software\microsoft\microsoft sql server\80\tools\sqlew\registeredservers x
You should be able to export this key with regedt32. If you use regedit, you may only get the directory structure, and none of the data. Hope this helps.|||Thats what I was looking for !|||The same information is in HKEY_USERS\... But you have to guess at what your NT SID is. This is probably the more definitive place to get and store the information, as I think HKEY_CURRENT_USER is cleared when you log out.
As always, modifying your registry can have dire consequences, yadda, yadda, yadda.
ThanksOriginally posted by aashu
Anyone knows if it is at all possible to Copy or Move the Server Registered under EM to another machine ?
Thanks
but if have the registered server on ur EM then u can just use that to register the same servers on another instance of EM... or you could get the information for the server from the Client Network Utility: ipaddresses, servername etc.|||I am aware of that . Doing for 50 Servers will be a nightmare .. So , back to the question again , is there some ini file or EM setup file I could move over?
Thanks|||I know the information about registered servers is in the registry:
HKEY_CURRENT_USER\software\microsoft\microsoft sql server\80\tools\sqlew\registeredservers x
You should be able to export this key with regedt32. If you use regedit, you may only get the directory structure, and none of the data. Hope this helps.|||Thats what I was looking for !|||The same information is in HKEY_USERS\... But you have to guess at what your NT SID is. This is probably the more definitive place to get and store the information, as I think HKEY_CURRENT_USER is cleared when you log out.
As always, modifying your registry can have dire consequences, yadda, yadda, yadda.
Friday, March 9, 2012
Enterprise Manager has stopped working!
I am having a real problem opening a database on a SQL server through EM. The DB is on the machine as I can use EM on another machine and login from there. However, when I try to login to the DB via EM on the actual server I cannot and get an error saying 'Connection failed. Check SQL Server registration properties'.
Even if I change the reg properties it still will not let me access the database, it just keeps giving the same error.
Has anyone seen something like this before?What did you change in Registration properties?|||They're near shore in Ireland...and the Pub just opened...
I would what the code will look like after lunch...
Even if I change the reg properties it still will not let me access the database, it just keeps giving the same error.
Has anyone seen something like this before?What did you change in Registration properties?|||They're near shore in Ireland...and the Pub just opened...
I would what the code will look like after lunch...
Wednesday, March 7, 2012
Enterprise Manager Hangs
Everytime I try to use the Enterprise Manager tool to
access my SQL 2000 (sp3) server on a W2K3 Enterprise
machine it hangs (stops responding). The tool loads
correctly but when I dig down the tree to get at the
instance on the local machine it stops responding when
trying to Establish the Connection and checking Windows
Security.
The server is loading and running, but I can't make any
new databases.
I can stop and start the server.
I have tried reinstalling. I have checked that the
services are running correctly.Hi, please verify permissions on folder Microsoft SQL Server.
Verify if you services account have permissions on foder MSSQL
Verify the event viewer to view if you have more messages about mssqlserver
The problem is generally by permissions
I hope help you
Carlos Augusto
Bogot=E1 Colombia
>--Original Message--
>Everytime I try to use the Enterprise Manager tool to >access my SQL 2000 (sp3) server on a W2K3 Enterprise >machine it hangs (stops responding). The tool loads >correctly but when I dig down the tree to get at the >instance on the local machine it stops responding when >trying to Establish the Connection and checking Windows >Security.
>The server is loading and running, but I can't make any >new databases.
>I can stop and start the server.
>I have tried reinstalling. I have checked that the >services are running correctly.
>.
>
access my SQL 2000 (sp3) server on a W2K3 Enterprise
machine it hangs (stops responding). The tool loads
correctly but when I dig down the tree to get at the
instance on the local machine it stops responding when
trying to Establish the Connection and checking Windows
Security.
The server is loading and running, but I can't make any
new databases.
I can stop and start the server.
I have tried reinstalling. I have checked that the
services are running correctly.Hi, please verify permissions on folder Microsoft SQL Server.
Verify if you services account have permissions on foder MSSQL
Verify the event viewer to view if you have more messages about mssqlserver
The problem is generally by permissions
I hope help you
Carlos Augusto
Bogot=E1 Colombia
>--Original Message--
>Everytime I try to use the Enterprise Manager tool to >access my SQL 2000 (sp3) server on a W2K3 Enterprise >machine it hangs (stops responding). The tool loads >correctly but when I dig down the tree to get at the >instance on the local machine it stops responding when >trying to Establish the Connection and checking Windows >Security.
>The server is loading and running, but I can't make any >new databases.
>I can stop and start the server.
>I have tried reinstalling. I have checked that the >services are running correctly.
>.
>
Enterprise Manager Freezing up
Hi,
When I try to browse databases within Enterprise Manager on my SQL server,
the machine freezes up. It takes like 20 minutes to just see the list of
databases on the server.
Any ideas what's wrong and how to fix it.
thanks
rafaelAre you running any jobs on it or doing anything like rebuilding indexes?
Could be low on resources - not sure though, you didn't give any specs or
specific info. You can use Profiler to analyze further.
"Rafael Chemtob" <rchemtobb@.nospam.yahoo.com> wrote in message
news:umS%23fW4SFHA.3652@.TK2MSFTNGP15.phx.gbl...
> Hi,
> When I try to browse databases within Enterprise Manager on my SQL server,
> the machine freezes up. It takes like 20 minutes to just see the list of
> databases on the server.
> Any ideas what's wrong and how to fix it.
> thanks
> rafael
>|||If the DB's are set to autoclose, EM has to ask each one to start up to find
out it's properties. Check the SQL Event log for DB startup messages.
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/
"Rafael Chemtob" <rchemtobb@.nospam.yahoo.com> wrote in message
news:umS%23fW4SFHA.3652@.TK2MSFTNGP15.phx.gbl...
> Hi,
> When I try to browse databases within Enterprise Manager on my SQL server,
> the machine freezes up. It takes like 20 minutes to just see the list of
> databases on the server.
> Any ideas what's wrong and how to fix it.
> thanks
> rafael
>
When I try to browse databases within Enterprise Manager on my SQL server,
the machine freezes up. It takes like 20 minutes to just see the list of
databases on the server.
Any ideas what's wrong and how to fix it.
thanks
rafaelAre you running any jobs on it or doing anything like rebuilding indexes?
Could be low on resources - not sure though, you didn't give any specs or
specific info. You can use Profiler to analyze further.
"Rafael Chemtob" <rchemtobb@.nospam.yahoo.com> wrote in message
news:umS%23fW4SFHA.3652@.TK2MSFTNGP15.phx.gbl...
> Hi,
> When I try to browse databases within Enterprise Manager on my SQL server,
> the machine freezes up. It takes like 20 minutes to just see the list of
> databases on the server.
> Any ideas what's wrong and how to fix it.
> thanks
> rafael
>|||If the DB's are set to autoclose, EM has to ask each one to start up to find
out it's properties. Check the SQL Event log for DB startup messages.
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/
"Rafael Chemtob" <rchemtobb@.nospam.yahoo.com> wrote in message
news:umS%23fW4SFHA.3652@.TK2MSFTNGP15.phx.gbl...
> Hi,
> When I try to browse databases within Enterprise Manager on my SQL server,
> the machine freezes up. It takes like 20 minutes to just see the list of
> databases on the server.
> Any ideas what's wrong and how to fix it.
> thanks
> rafael
>
Friday, February 24, 2012
Enterprise Manager Cannot Display Table Records or Run Query
I have a new installation of SQL Server 2000 Dev Edition on a Win2K3 Standard Edition Server that I used for development. I just set this machine up in th last week and installed all Win2K3 patches and then installed SQL2K and SP3a. I have a single named instance. I just noticed today that I cannot view table data or use the Query part of EM. When I right click a table and select Open Table->Return All Rows it gives me an error dialog "An unexpected error happened during this operation". While the EM is diplaying this dialog the EM screen looks like Internet Explorer and says "Action Canceled - You might not have permission to view this directory or page using the credentials you supplied." I believe that this is a EM issue as I cannot view table content on other remote server. ANy ideas? Might this be an IE security patch disallowing some connectivity ?
--Frank
--
Message posted via http://www.sqlmonster.com"Frank Rizzo via SQLMonster.com" <forum@.SQLMonster.com> wrote in message
news:08f32b66479d4ddcbe5ab7a876ff377d@.SQLMonster.c om...
>I have a new installation of SQL Server 2000 Dev Edition on a Win2K3
>Standard Edition Server that I used for development. I just set this
>machine up in th last week and installed all Win2K3 patches and then
>installed SQL2K and SP3a. I have a single named instance. I just noticed
>today that I cannot view table data or use the Query part of EM. When I
>right click a table and select Open Table->Return All Rows it gives me an
>error dialog "An unexpected error happened during this operation". While
>the EM is diplaying this dialog the EM screen looks like Internet Explorer
>and says "Action Canceled - You might not have permission to view this
>directory or page using the credentials you supplied." I believe that this
>is a EM issue as I cannot view table content on other remote server. ANy
>ideas? Might this be an IE security patch disallowing some connectivity ?
> --Frank
> --
> Message posted via http://www.sqlmonster.com
A number of people seem to have had similar issues - if you Google the
newsgroups, you'll see that the usual response is to reinstall either the
MSSQL client tools (including SP3a) and/or the latest MDAC version.
Unfortunately, it doesn't always seem to solve the problem.
Simon
Enterprise Manager Can Not Connect to a Named Instance
I installed a new named instance of sql server on a machine called faoweb2k04. There are three instances on this machine: default, afosrio, & afosrio2 (which I can not connect to).
Any suggestions? aforio2 does not show up in the enterprise manager when I select the option [New SQL Server Registration...]
Interesting...
Are the services associated with those other instances running?
Rick Sawtell
MCT, MCSD, MCDBA
|||"sjsnraets" wrote:
> I installed a new named instance of sql server on a machine called faoweb2k04. There are three instances on this machine: default, afosrio, & afosrio2 (which I can not connect to).
> Any suggestions? aforio2 does not show up in the enterprise manager when I select the option [New SQL Server Registration...]
Start the New SQL Server Registration wizard
Type server name inmediatelly to available servers field (server name\aforio2) and click on add button. Click next ...
If server instance is running, the registration will be completed. (not need visible in list)
Andras Jakus
MCDBA
Any suggestions? aforio2 does not show up in the enterprise manager when I select the option [New SQL Server Registration...]
Interesting...
Are the services associated with those other instances running?
Rick Sawtell
MCT, MCSD, MCDBA
|||"sjsnraets" wrote:
> I installed a new named instance of sql server on a machine called faoweb2k04. There are three instances on this machine: default, afosrio, & afosrio2 (which I can not connect to).
> Any suggestions? aforio2 does not show up in the enterprise manager when I select the option [New SQL Server Registration...]
Start the New SQL Server Registration wizard
Type server name inmediatelly to available servers field (server name\aforio2) and click on add button. Click next ...
If server instance is running, the registration will be completed. (not need visible in list)
Andras Jakus
MCDBA
Enterprise Manager Can Not Connect to a Named Instance
I installed a new named instance of sql server on a machine called faoweb2k0
4. There are three instances on this machine: default, afosrio, & afosrio2
(which I can not connect to).
Any suggestions? aforio2 does not show up in the enterprise manager when I
select the option [New SQL Server Registration...]Interesting...
Are the services associated with those other instances running?
Rick Sawtell
MCT, MCSD, MCDBA|||"sjsnraets" wrote:
> I installed a new named instance of sql server on a machine called faoweb2
k04. There are three instances on this machine: default, afosrio, & afosrio
2 (which I can not connect to).
> Any suggestions? aforio2 does not show up in the enterprise manager when I select
the option [New SQL Server Registration...]
Start the New SQL Server Registration wizard
Type server name inmediatelly to available servers field (server name\aforio
2) and click on add button. Click next ...
If server instance is running, the registration will be completed. (not need
visible in list)
Andras Jakus
MCDBA
4. There are three instances on this machine: default, afosrio, & afosrio2
(which I can not connect to).
Any suggestions? aforio2 does not show up in the enterprise manager when I
select the option [New SQL Server Registration...]Interesting...
Are the services associated with those other instances running?
Rick Sawtell
MCT, MCSD, MCDBA|||"sjsnraets" wrote:
> I installed a new named instance of sql server on a machine called faoweb2
k04. There are three instances on this machine: default, afosrio, & afosrio
2 (which I can not connect to).
> Any suggestions? aforio2 does not show up in the enterprise manager when I select
the option [New SQL Server Registration...]
Start the New SQL Server Registration wizard
Type server name inmediatelly to available servers field (server name\aforio
2) and click on add button. Click next ...
If server instance is running, the registration will be completed. (not need
visible in list)
Andras Jakus
MCDBA
Enterprise Manager Can Not Connect to a Named Instance
I installed a new named instance of sql server on a machine called faoweb2k04. There are three instances on this machine: default, afosrio, & afosrio2 (which I can not connect to).
Any suggestions? aforio2 does not show up in the enterprise manager when I select the option [New SQL Server Registration...]Interesting...
Are the services associated with those other instances running?
Rick Sawtell
MCT, MCSD, MCDBA
Any suggestions? aforio2 does not show up in the enterprise manager when I select the option [New SQL Server Registration...]Interesting...
Are the services associated with those other instances running?
Rick Sawtell
MCT, MCSD, MCDBA
Friday, February 17, 2012
Enterprise Manager - Available Servers - remote instance not listed
When using the register available servers in Enterprise Manager, the
named instances on a remote machine are not listed. The unnamed
instance is listed and will register successfully.
I have tried manually typing the names of the remote NAMED instances;
then tried to authenticate and get the message "SQL server does not
exist or access denied".
Local machine; SQL Server 2000 SP4 (Developer Edition) installed.
2 Instances
Unnamed
DEV\DB1
On the remote machine SQL Server 2000 (MSDE Edition) installed
3 Instances;
Unnamed
REM\DB1
REM\DB2
Both machines are on the same domain. All SQL server instances are
running.
I have also used the svrnetcn.exe tool to make sure the Named Pipes
and TCP/IP protocols are enabled. The port on the TCP/IP protocol has
been changed to 1433 on all remote instances. (both machines were
rebooted)
What else can I check ?
Thanks
DOn Sep 18, 9:18 pm, do <dmc...@.gmail.com> wrote:
> When using the register available servers in Enterprise Manager, the
> named instances on a remote machine are not listed. The unnamed
> instance is listed and will register successfully.
> I have tried manually typing the names of the remote NAMED instances;
> then tried to authenticate and get the message "SQL server does not
> exist or access denied".
> Local machine; SQL Server 2000 SP4 (Developer Edition) installed.
> 2 Instances
> Unnamed
> DEV\DB1
> On the remote machine SQL Server 2000 (MSDE Edition) installed
> 3 Instances;
> Unnamed
> REM\DB1
> REM\DB2
Create an alias for the named instances on the client end & then try
registering...
> Both machines are on the same domain. All SQL server instances are
> running.
> I have also used the svrnetcn.exe tool to make sure the Named Pipes
> and TCP/IP protocols are enabled. The port on the TCP/IP protocol has
> been changed to 1433 on all remote instances. (both machines were
> rebooted)
> What else can I check ?
> Thanks
> D
named instances on a remote machine are not listed. The unnamed
instance is listed and will register successfully.
I have tried manually typing the names of the remote NAMED instances;
then tried to authenticate and get the message "SQL server does not
exist or access denied".
Local machine; SQL Server 2000 SP4 (Developer Edition) installed.
2 Instances
Unnamed
DEV\DB1
On the remote machine SQL Server 2000 (MSDE Edition) installed
3 Instances;
Unnamed
REM\DB1
REM\DB2
Both machines are on the same domain. All SQL server instances are
running.
I have also used the svrnetcn.exe tool to make sure the Named Pipes
and TCP/IP protocols are enabled. The port on the TCP/IP protocol has
been changed to 1433 on all remote instances. (both machines were
rebooted)
What else can I check ?
Thanks
DOn Sep 18, 9:18 pm, do <dmc...@.gmail.com> wrote:
> When using the register available servers in Enterprise Manager, the
> named instances on a remote machine are not listed. The unnamed
> instance is listed and will register successfully.
> I have tried manually typing the names of the remote NAMED instances;
> then tried to authenticate and get the message "SQL server does not
> exist or access denied".
> Local machine; SQL Server 2000 SP4 (Developer Edition) installed.
> 2 Instances
> Unnamed
> DEV\DB1
> On the remote machine SQL Server 2000 (MSDE Edition) installed
> 3 Instances;
> Unnamed
> REM\DB1
> REM\DB2
Create an alias for the named instances on the client end & then try
registering...
> Both machines are on the same domain. All SQL server instances are
> running.
> I have also used the svrnetcn.exe tool to make sure the Named Pipes
> and TCP/IP protocols are enabled. The port on the TCP/IP protocol has
> been changed to 1433 on all remote instances. (both machines were
> rebooted)
> What else can I check ?
> Thanks
> D
Enterprise Manager - Available Servers - remote instance not listed
When using the register available servers in Enterprise Manager, the
named instances on a remote machine are not listed. The unnamed
instance is listed and will register successfully.
I have tried manually typing the names of the remote NAMED instances;
then tried to authenticate and get the message "SQL server does not
exist or access denied".
Local machine; SQL Server 2000 SP4 (Developer Edition) installed.
2 Instances
Unnamed
DEV\DB1
On the remote machine SQL Server 2000 (MSDE Edition) installed
3 Instances;
Unnamed
REM\DB1
REM\DB2
Both machines are on the same domain. All SQL server instances are
running.
I have also used the svrnetcn.exe tool to make sure the Named Pipes
and TCP/IP protocols are enabled. The port on the TCP/IP protocol has
been changed to 1433 on all remote instances. (both machines were
rebooted)
What else can I check ?
Thanks
DHow about trying adding aliases from SQL Server Client Network Utility?
Add Aliases for your named instances and try connecting then.
You may obtain more info about this from the following link:
http://msdn2.microsoft.com/en-us/library/aa213780(SQL.80).aspx
You may want to have a look at the following article from BOL to learn more
about Browser Service of SQL Server 2005. This may be irrelevant however it
informs you about SS2000' s listening service too. It may give you an idea.
http://msdn2.microsoft.com/en-us/library/ms181087.aspx
--
Ekrem Önsoy
"do" <dmcb73@.gmail.com> wrote in message
news:1190189984.640820.24640@.o80g2000hse.googlegroups.com...
> When using the register available servers in Enterprise Manager, the
> named instances on a remote machine are not listed. The unnamed
> instance is listed and will register successfully.
> I have tried manually typing the names of the remote NAMED instances;
> then tried to authenticate and get the message "SQL server does not
> exist or access denied".
> Local machine; SQL Server 2000 SP4 (Developer Edition) installed.
> 2 Instances
> Unnamed
> DEV\DB1
> On the remote machine SQL Server 2000 (MSDE Edition) installed
> 3 Instances;
> Unnamed
> REM\DB1
> REM\DB2
> Both machines are on the same domain. All SQL server instances are
> running.
> I have also used the svrnetcn.exe tool to make sure the Named Pipes
> and TCP/IP protocols are enabled. The port on the TCP/IP protocol has
> been changed to 1433 on all remote instances. (both machines were
> rebooted)
> What else can I check ?
> Thanks
> D
>
named instances on a remote machine are not listed. The unnamed
instance is listed and will register successfully.
I have tried manually typing the names of the remote NAMED instances;
then tried to authenticate and get the message "SQL server does not
exist or access denied".
Local machine; SQL Server 2000 SP4 (Developer Edition) installed.
2 Instances
Unnamed
DEV\DB1
On the remote machine SQL Server 2000 (MSDE Edition) installed
3 Instances;
Unnamed
REM\DB1
REM\DB2
Both machines are on the same domain. All SQL server instances are
running.
I have also used the svrnetcn.exe tool to make sure the Named Pipes
and TCP/IP protocols are enabled. The port on the TCP/IP protocol has
been changed to 1433 on all remote instances. (both machines were
rebooted)
What else can I check ?
Thanks
DHow about trying adding aliases from SQL Server Client Network Utility?
Add Aliases for your named instances and try connecting then.
You may obtain more info about this from the following link:
http://msdn2.microsoft.com/en-us/library/aa213780(SQL.80).aspx
You may want to have a look at the following article from BOL to learn more
about Browser Service of SQL Server 2005. This may be irrelevant however it
informs you about SS2000' s listening service too. It may give you an idea.
http://msdn2.microsoft.com/en-us/library/ms181087.aspx
--
Ekrem Önsoy
"do" <dmcb73@.gmail.com> wrote in message
news:1190189984.640820.24640@.o80g2000hse.googlegroups.com...
> When using the register available servers in Enterprise Manager, the
> named instances on a remote machine are not listed. The unnamed
> instance is listed and will register successfully.
> I have tried manually typing the names of the remote NAMED instances;
> then tried to authenticate and get the message "SQL server does not
> exist or access denied".
> Local machine; SQL Server 2000 SP4 (Developer Edition) installed.
> 2 Instances
> Unnamed
> DEV\DB1
> On the remote machine SQL Server 2000 (MSDE Edition) installed
> 3 Instances;
> Unnamed
> REM\DB1
> REM\DB2
> Both machines are on the same domain. All SQL server instances are
> running.
> I have also used the svrnetcn.exe tool to make sure the Named Pipes
> and TCP/IP protocols are enabled. The port on the TCP/IP protocol has
> been changed to 1433 on all remote instances. (both machines were
> rebooted)
> What else can I check ?
> Thanks
> D
>
enterprise manager
Hi all,
I have setup a new test server running sql2k sp3 on sbs2003. I have my
client machine which is just running sql2k on windows 2000. Is it safe to
use enterprise manager on my machine (no sp installed) to connect to the
sql2k sp3 server? Or is it recommended I install sp3 on mine too?
thanks!
It is ideal to have your client utilitys at SP3 level also as there are
changes to the SQL-DMO dlls etc. which SEM uses
"RP" <rp@.nospam.com> wrote in message
news:eljLjGiIEHA.1944@.TK2MSFTNGP11.phx.gbl...
> Hi all,
> I have setup a new test server running sql2k sp3 on sbs2003. I have my
> client machine which is just running sql2k on windows 2000. Is it safe to
> use enterprise manager on my machine (no sp installed) to connect to the
> sql2k sp3 server? Or is it recommended I install sp3 on mine too?
> thanks!
>
I have setup a new test server running sql2k sp3 on sbs2003. I have my
client machine which is just running sql2k on windows 2000. Is it safe to
use enterprise manager on my machine (no sp installed) to connect to the
sql2k sp3 server? Or is it recommended I install sp3 on mine too?
thanks!
It is ideal to have your client utilitys at SP3 level also as there are
changes to the SQL-DMO dlls etc. which SEM uses
"RP" <rp@.nospam.com> wrote in message
news:eljLjGiIEHA.1944@.TK2MSFTNGP11.phx.gbl...
> Hi all,
> I have setup a new test server running sql2k sp3 on sbs2003. I have my
> client machine which is just running sql2k on windows 2000. Is it safe to
> use enterprise manager on my machine (no sp installed) to connect to the
> sql2k sp3 server? Or is it recommended I install sp3 on mine too?
> thanks!
>
enterprise manager
Hi all,
I have setup a new test server running sql2k sp3 on sbs2003. I have my
client machine which is just running sql2k on windows 2000. Is it safe to
use enterprise manager on my machine (no sp installed) to connect to the
sql2k sp3 server? Or is it recommended I install sp3 on mine too?
thanks!It is ideal to have your client utilitys at SP3 level also as there are
changes to the SQL-DMO dlls etc. which SEM uses
"RP" <rp@.nospam.com> wrote in message
news:eljLjGiIEHA.1944@.TK2MSFTNGP11.phx.gbl...
> Hi all,
> I have setup a new test server running sql2k sp3 on sbs2003. I have my
> client machine which is just running sql2k on windows 2000. Is it safe to
> use enterprise manager on my machine (no sp installed) to connect to the
> sql2k sp3 server? Or is it recommended I install sp3 on mine too?
> thanks!
>|||Hi Kathy,
There's a very simple workaround for the scripting error you're
encountering in Enterprise Manager.
Just right-click on the DB, click view, then click list to display the
DB objects. Go back, right-click on the DB, click view, then click
Taskpad. It will reset the web interface and it'll work again.
Yes, another stupid bug in MSSQL SQL Server.
Best Regards,
Chuck Lee
chucksql@.hotmail.com
chucklee
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message205074.html
I have setup a new test server running sql2k sp3 on sbs2003. I have my
client machine which is just running sql2k on windows 2000. Is it safe to
use enterprise manager on my machine (no sp installed) to connect to the
sql2k sp3 server? Or is it recommended I install sp3 on mine too?
thanks!It is ideal to have your client utilitys at SP3 level also as there are
changes to the SQL-DMO dlls etc. which SEM uses
"RP" <rp@.nospam.com> wrote in message
news:eljLjGiIEHA.1944@.TK2MSFTNGP11.phx.gbl...
> Hi all,
> I have setup a new test server running sql2k sp3 on sbs2003. I have my
> client machine which is just running sql2k on windows 2000. Is it safe to
> use enterprise manager on my machine (no sp installed) to connect to the
> sql2k sp3 server? Or is it recommended I install sp3 on mine too?
> thanks!
>|||Hi Kathy,
There's a very simple workaround for the scripting error you're
encountering in Enterprise Manager.
Just right-click on the DB, click view, then click list to display the
DB objects. Go back, right-click on the DB, click view, then click
Taskpad. It will reset the web interface and it'll work again.
Yes, another stupid bug in MSSQL SQL Server.
Best Regards,
Chuck Lee
chucksql@.hotmail.com
chucklee
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message205074.html
enterprise manager
Hi all,
I have setup a new test server running sql2k sp3 on sbs2003. I have my
client machine which is just running sql2k on windows 2000. Is it safe to
use enterprise manager on my machine (no sp installed) to connect to the
sql2k sp3 server? Or is it recommended I install sp3 on mine too?
thanks!It is ideal to have your client utilitys at SP3 level also as there are
changes to the SQL-DMO dlls etc. which SEM uses
"RP" <rp@.nospam.com> wrote in message
news:eljLjGiIEHA.1944@.TK2MSFTNGP11.phx.gbl...
> Hi all,
> I have setup a new test server running sql2k sp3 on sbs2003. I have my
> client machine which is just running sql2k on windows 2000. Is it safe to
> use enterprise manager on my machine (no sp installed) to connect to the
> sql2k sp3 server? Or is it recommended I install sp3 on mine too?
> thanks!
>
I have setup a new test server running sql2k sp3 on sbs2003. I have my
client machine which is just running sql2k on windows 2000. Is it safe to
use enterprise manager on my machine (no sp installed) to connect to the
sql2k sp3 server? Or is it recommended I install sp3 on mine too?
thanks!It is ideal to have your client utilitys at SP3 level also as there are
changes to the SQL-DMO dlls etc. which SEM uses
"RP" <rp@.nospam.com> wrote in message
news:eljLjGiIEHA.1944@.TK2MSFTNGP11.phx.gbl...
> Hi all,
> I have setup a new test server running sql2k sp3 on sbs2003. I have my
> client machine which is just running sql2k on windows 2000. Is it safe to
> use enterprise manager on my machine (no sp installed) to connect to the
> sql2k sp3 server? Or is it recommended I install sp3 on mine too?
> thanks!
>
Subscribe to:
Posts (Atom)