enumerating registered sqlservers does not fill datatable complete

I've tried to enumerate sqlservers using two different methods and have the
same results... only the server name is returned, I am unable to get the
instance name so user will be unable to connect to selected server if it is
a
named instance (i.e. "Server"\SQLEXPRESS)...
Dim dt As DataTable
dt = SmoApplication.EnumAvailableSqlServers(False)
OR
Dim dt As DataTable
Dim instance As Sql.SqlDataSourceEnumerator =
Sql.SqlDataSourceEnumerator.Instance
dt = instance.GetDataSources
However I can go into SQL Server Management Studio, browse for servers and
every instance for every server (local and network) is listed... I assume
(foolishly) that MS Apps utilize thier own sdk's, if so why does it work
there but not for meOK I think I've found the culprit... the "Windows Firewall/Internet
Connection Sharing (ICS)" service
When I stop this service the enumerations return the Instance name and
Version of the SQL Servers... Hooray but what if Users have this service
running during my application installation? I'm suprised this isn't more of
a
known issue... I'm able to duplicate the issue on 2 machines both running XP
sp2 where one has SQL Server Express 2005 then other has SQL Server Express
2005 SP1, same results. Has anyone heard or exprienced this?

> I've tried to enumerate sqlservers using two different methods and have th
e
> same results... only the server name is returned, I am unable to get the
> instance name so user will be unable to connect to selected server if it i
s a
> named instance (i.e. "Server"\SQLEXPRESS)...
> Dim dt As DataTable
> dt = SmoApplication.EnumAvailableSqlServers(False)
> OR
> Dim dt As DataTable
> Dim instance As Sql.SqlDataSourceEnumerator =
> Sql.SqlDataSourceEnumerator.Instance
> dt = instance.GetDataSources
> However I can go into SQL Server Management Studio, browse for servers and
> every instance for every server (local and network) is listed... I assume
> (foolishly) that MS Apps utilize thier own sdk's, if so why does it work
> there but not for me|||On Tue, 13 Jun 2006 14:17:02 -0700, rqcoder
<rqcoder@.discussions.microsoft.com> wrote:
in <EF3759A0-3FE7-4839-B10E-E892752C02AB@.microsoft.com>

>OK I think I've found the culprit... the "Windows Firewall/Internet
>Connection Sharing (ICS)" service
>When I stop this service the enumerations return the Instance name and
>Version of the SQL Servers... Hooray but what if Users have this service
>running during my application installation? I'm suprised this isn't more of
a
>known issue... I'm able to duplicate the issue on 2 machines both running X
P
>sp2 where one has SQL Server Express 2005 then other has SQL Server Express
>2005 SP1, same results. Has anyone heard or exprienced this?
It happens on any machine that's running the firewall. It looks like
the tolerance window for the enumerations is extremely small - less than
a second. If anything hampers that initial query in the slightest then
the instance names don't show up. And I'm describing SQLDMO behavior
using VB6 but the enumerations code is most likely the same or extremely
similar.
What works well for me is Kerio Personal Firewall with specific rules
but that doesn't always wash well in the general user community.
Stefan Berglund

Enterprise Manager very slow on XP Pro

Hi,
I have SQL 2000 Personal Edition / SP3 on XP Pro, P4/HT. I also have the
same version of SQL installed on W2K / P3. The Enterprise Manager seems to
run much slower on XP than on W2K. A simple click in the left pane (e.g. on
'databases') results in 20-30 second wait (the disk led is lit solid during
that time).
Could anyone please give me any suggestions as to what I should be looking
for on the XP machine?
Thanks,
Bogdan
> I have SQL 2000 Personal Edition / SP3 on XP Pro, P4/HT. I also have the
> same version of SQL installed on W2K / P3. The Enterprise Manager seems
to
> run much slower on XP than on W2K. A simple click in the left pane (e.g.
on
> 'databases') results in 20-30 second wait (the disk led is lit solid
during
> that time).
Do please check if your databases have the autoclose option turned on. This
is default for Personal edition, and it takes time to open all databases.
Dejan Sarka, SQL Server MVP
Associate Mentor
www.SolidQualityLearning.com
|||Also verify that you have no ODBC tracing turned on.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Dejan Sarka" <dejan_please_reply_to_newsgroups.sarka@.avtenta.si > wrote in message
news:u2kKHRKRFHA.3704@.TK2MSFTNGP12.phx.gbl...
> to
> on
> during
> Do please check if your databases have the autoclose option turned on. This
> is default for Personal edition, and it takes time to open all databases.
> --
> Dejan Sarka, SQL Server MVP
> Associate Mentor
> www.SolidQualityLearning.com
>
|||Neither of the databases had auto-close enabled. The ODBC tracing was not
enabled (although I'm not using ODBC to connect to any of the databases and
I hope that Enterprise Manager does not use it either).
What seemed to work was SP3a. I applied it last night and things appear to
be 'normal' now.
Dejan, Tibor: thanks for your responses.
Bogdan
"Bogdan" <someone@.domain.com> wrote in message
news:%237JkLWIRFHA.1416@.TK2MSFTNGP10.phx.gbl...
> Hi,
> I have SQL 2000 Personal Edition / SP3 on XP Pro, P4/HT. I also have the
> same version of SQL installed on W2K / P3. The Enterprise Manager seems
> to run much slower on XP than on W2K. A simple click in the left pane
> (e.g. on 'databases') results in 20-30 second wait (the disk led is lit
> solid during that time).
> Could anyone please give me any suggestions as to what I should be looking
> for on the XP machine?
> Thanks,
> Bogdan
>
|||> I hope that Enterprise Manager does not use it either).
Both EM and QA uses ODBC.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Bogdan" <someone@.domain.com> wrote in message news:e3FUs4URFHA.3944@.TK2MSFTNGP10.phx.gbl...
> Neither of the databases had auto-close enabled. The ODBC tracing was not enabled (although I'm
> not using ODBC to connect to any of the databases and I hope that Enterprise Manager does not use
> it either).
> What seemed to work was SP3a. I applied it last night and things appear to be 'normal' now.
> Dejan, Tibor: thanks for your responses.
> Bogdan
>
> "Bogdan" <someone@.domain.com> wrote in message news:%237JkLWIRFHA.1416@.TK2MSFTNGP10.phx.gbl...
>
|||Dejan Sarka wrote:
> Do please check if your databases have the autoclose option turned
> on. This is default for Personal edition, and it takes time to open
> all databases.
I've had a laptop that's been slow for months with QA and SQL EM and
it's been driving me crazy. Even pressing the Cancel button from the
Database properties in SQL EM caused undue database and disk activity.
Checked the databases, and sure enough, there was one user database that
mysteriously had Auto Close turned on. Probably turned it on for testing
and forgot to turn it off.
You fixed me. Thanks.
David Gugick
Imceda Software
www.imceda.com
|||If you want fast access to your database try SQL Admin Studio from
www.simego.com as this tool is just amazingly fast at connecting and
browsing SQL Server Databases.
"Bogdan" <someone@.domain.com> wrote in message
news:%237JkLWIRFHA.1416@.TK2MSFTNGP10.phx.gbl...
> Hi,
> I have SQL 2000 Personal Edition / SP3 on XP Pro, P4/HT. I also have the
> same version of SQL installed on W2K / P3. The Enterprise Manager seems
> to run much slower on XP than on W2K. A simple click in the left pane
> (e.g. on 'databases') results in 20-30 second wait (the disk led is lit
> solid during that time).
> Could anyone please give me any suggestions as to what I should be looking
> for on the XP machine?
> Thanks,
> Bogdan
>
|||Another way that I've seen autoclose turned on is when
moving a database from MSDE to MSSQL.
MSDE, IIRC, defaults to autoclose on.
jg

Quote:

Originally posted by David Gugick
Dejan Sarka wrote:
> Do please check if your databases have the autoclose option turned
> on. This is default for Personal edition, and it takes time to open
> all databases.
I've had a laptop that's been slow for months with QA and SQL EM and
it's been driving me crazy. Even pressing the Cancel button from the
Database properties in SQL EM caused undue database and disk activity.
Checked the databases, and sure enough, there was one user database that
mysteriously had Auto Close turned on. Probably turned it on for testing
and forgot to turn it off.
You fixed me. Thanks.
David Gugick
Imceda Software
www.imceda.com