Why does SQLBrowseInfo call take so long?
- From: Cameron_C <CameronC@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sun, 11 Jan 2009 08:24:00 -0800
I was using the call to iterate over all SQL Servers available, and then
iterating over all of the databases available on each server.
That way I was able to present a combo box to the end User to simply choose
the Server they wish to access for the SQL database.
However, the call takes so long I reworked the code to use a CDataBase
object, and pop the ODBC Manager dialog. This is much faster. (Seconds versus
minutes.)
The down side of this approach is that it presents an interface that is a
bit more technical than my end Users are likely to understand, which means
more support calls for us to contend with.
Does anyone know either how I may speed up the SQLBrowseInfo call, or how I
can simplify the ODBC Dialog interface?
Or even, if there is some other approach to listing all available databases
for all available servers?
BTW, I presume this is an MFC question, even though it relates to SQL
DataBase information access.
Once again, any thoughts or information would be greatly appreciated.
.
- Follow-Ups:
- Re: Why does SQLBrowseInfo call take so long?
- From: Joseph M . Newcomer
- Re: Why does SQLBrowseInfo call take so long?
- Prev by Date: Re: DoModal()
- Next by Date: RE: MFC command bar problem
- Previous by thread: Digitally sign my own DLL?
- Next by thread: Re: Why does SQLBrowseInfo call take so long?
- Index(es):
Relevant Pages
|
