slow connection to geodatabase

[HaniuHokkaido]

Hi,

I have to access a geodb on the database server at branch office... I use Direct Connect. It takes >20 seconds just to open the connection. Then I connect to the database server directly using SQL Server Mgmnt Std and open up the Activity Monitor.
My questions:
1. How do you determine the factors that affecting this slowness ? What tool do I have to use to find out the factors ? I need to justify the process.
2. How can i use the Activity Monitor ?
3. How to speed up the connection to geodb in the branch office ?

Environmet: sql server 2005 enterprise.

Thanks

[VinceAngelo]

1) The number of tables visible by the user (and the time it takes to describe that table)
dictates connection speed
2) You can't
3) You can't (without reducing table count or improving network speed)

- V

[HaniuHokkaido]

Thanks for the reply...

"1) The number of tables visible by the user (and the time it takes to describe that table)
dictates connection speed" >> so are you saying that ArcCatalog *fully* reads all the visible tables eventhough it not yet opened ?

If I open the database straight from Management Studio it takes me 1-3seconds to open up... So if I open the connection in ArcCatalog and it takes up >20s then its normal due arccatalog reads all the visible tables. Correct ?

thanks alot Vince

[VinceAngelo]

It doesn't "read" the tables, but it does need to construct the catalog view, so it needs
compile the list of tables, and to determine which column is the geometry column for
each table, and what topology class, and whether it's part of a feature dataset,...
And that inventory *isn't* done by a simple database connect (which, at worst, just
needs the list of tables).

- V

[HaniuHokkaido]

Thanks for the explanation Vince.. 🙂

[GISGroup]

hi,

I am using arccatelog10.1 to connect arcsde 9.3 using oracle direct connect. It took more than 60 sec to connect.  I set up intercept log and found that tablelisttables command took 32 sec. under this command, i can see all tables which user has access in the database.

I think as vangelo points out that it took time to read and analyse all tables. How can I improve?
Through sql, i can connect in 2-3 sec.

regards
Kumar

[VinceAngelo]

If you have a large number of tables, I don't think you can improve, though a
3 second SQL connect indicates that your client might not be robust enough
to manage a Direct Connect.  A 10.1 geodatabase would usually be faster to
connect than the equivalent 9.x instance, but all my testing has been with
very fast clients with at least 4Gb RAM.

- V