By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,946 Members | 697 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,946 IT Pros & Developers. It's quick & easy.

Slow backend due to long server name

P: n/a
Hi,

My company's backend is located at a location with a long address,
something like -

//our_servers/server_number_one/our_department/our_devision/
our_results/our_databases/backend.be

I have tested the very same backend on another server with a sort path
location at it works fine, but at the location above it is extremely
slow. I've also tested the speeds of both servers and they are the
same with regard to coping to and downloading files from each.

I've asked to get the backend moved but I have been met with a wall of
beurocracy since our servers are organised in this departmental
fashion. Today someone even remarked that surely there is a patch for
this problem and that I shouldn't be wasting their time asking to have
files relocated...

So, my question is, is there a patch or an alternative solution to
this problem since the only solution I have found is to move the
database.

Thanks,

Barry.
Dec 12 '07 #1
Share this Question
Share on Google+
6 Replies


P: n/a

<bg***@yahoo.comschreef in bericht news:4e**********************************@r29g2000 hsg.googlegroups.com...
Hi,

My company's backend is located at a location with a long address,
something like -

//our_servers/server_number_one/our_department/our_devision/
our_results/our_databases/backend.be

I have tested the very same backend on another server with a sort path
location at it works fine, but at the location above it is extremely
slow. I've also tested the speeds of both servers and they are the
same with regard to coping to and downloading files from each.

I've asked to get the backend moved but I have been met with a wall of
beurocracy since our servers are organised in this departmental
fashion. Today someone even remarked that surely there is a patch for
this problem and that I shouldn't be wasting their time asking to have
files relocated...

So, my question is, is there a patch or an alternative solution to
this problem since the only solution I have found is to move the
database.

Thanks,

Barry.
I am NOT a network guy but...
Ask 'them' to make a share of the directory 'our_databases' (eg 'our_data')
You could then try to link to \\our_servers\our_data\backend.be

Arno R
Dec 12 '07 #2

P: n/a
On Wed, 12 Dec 2007 12:58:48 +0100, "Arno R"
<ar****************@planet.nlwrote:

Would it also help to map a drive letter to that deep path, and link
to x:\backend.mdb?

-Tom.

>
<bg***@yahoo.comschreef in bericht news:4e**********************************@r29g2000 hsg.googlegroups.com...
>Hi,

My company's backend is located at a location with a long address,
something like -

//our_servers/server_number_one/our_department/our_devision/
our_results/our_databases/backend.be

I have tested the very same backend on another server with a sort path
location at it works fine, but at the location above it is extremely
slow. I've also tested the speeds of both servers and they are the
same with regard to coping to and downloading files from each.

I've asked to get the backend moved but I have been met with a wall of
beurocracy since our servers are organised in this departmental
fashion. Today someone even remarked that surely there is a patch for
this problem and that I shouldn't be wasting their time asking to have
files relocated...

So, my question is, is there a patch or an alternative solution to
this problem since the only solution I have found is to move the
database.

Thanks,

Barry.

I am NOT a network guy but...
Ask 'them' to make a share of the directory 'our_databases' (eg 'our_data')
You could then try to link to \\our_servers\our_data\backend.be

Arno R
Dec 12 '07 #3

P: n/a
On Wed, 12 Dec 2007 02:27:39 -0800 (PST), bg***@yahoo.com wrote:
>Hi,

My company's backend is located at a location with a long address,
something like -

//our_servers/server_number_one/our_department/our_devision/
our_results/our_databases/backend.be

I have tested the very same backend on another server with a sort path
location at it works fine, but at the location above it is extremely
slow. I've also tested the speeds of both servers and they are the
same with regard to coping to and downloading files from each.

I've asked to get the backend moved but I have been met with a wall of
beurocracy since our servers are organised in this departmental
fashion. Today someone even remarked that surely there is a patch for
this problem and that I shouldn't be wasting their time asking to have
files relocated...

So, my question is, is there a patch or an alternative solution to
this problem since the only solution I have found is to move the
database.

Thanks,

Barry.
There is no patch for this problem. It is a Windows/SMB
characteristic, not an Access bug. Windows needs to authenticate at
each directory layer in the share, so the deeper it is, the slower it
is.

As others have suggested, about the only solution is to get them to
create a share much lower in the directory structure.
Dec 12 '07 #4

P: n/a
On Dec 12, 10:43 am, Arch <send...@spam.netwrote:
On Wed, 12 Dec 2007 02:27:39 -0800 (PST), bg...@yahoo.com wrote:
Hi,
My company's backend is located at a location with a long address,
something like -
//our_servers/server_number_one/our_department/our_devision/
our_results/our_databases/backend.be
I have tested the very same backend on another server with a sort path
location at it works fine, but at the location above it is extremely
slow. I've also tested the speeds of both servers and they are the
same with regard to coping to and downloading files from each.
I've asked to get the backend moved but I have been met with a wall of
beurocracy since our servers are organised in this departmental
fashion. Today someone even remarked that surely there is a patch for
this problem and that I shouldn't be wasting their time asking to have
files relocated...
So, my question is, is there a patch or an alternative solution to
this problem since the only solution I have found is to move the
database.
Thanks,
Barry.

There is no patch for this problem. It is a Windows/SMB
characteristic, not an Access bug. Windows needs to authenticate at
each directory layer in the share, so the deeper it is, the slower it
is.

As others have suggested, about the only solution is to get them to
create a share much lower in the directory structure.
For more than ten?? years I have had users' frontend databases linked
to backends so deep I don't even think about remembering the path. And
the servers themselves are in the basement catacombs; rumour is that
if you get lost and stumble into one of these rooms you are never
permitted to leave (well, they're so cold that you freeze to death
pdq).
The names of the folders are not especially short. Toss in "Employee
Services Personnel Manager Class I Teaching Staff" and one can get
some long strings.

The front end is instantaneous in retrieving data from the backend,
and in sending data to the backend. I've fooled around with the
backend on a local machine, and there is no noticeable difference in
the speed of the applications under that condition.

I am nothing of a network geek, but surely Windows does not run
thorugh a full authentication routine everytime I press the down arrow
when browsing a continous form, or run a simple select or update
query?

My guess is that the database and the interface are poorly designed
and that IT knows this and is unwilling to throw any more of its time
at making it work properly.

I'm sorry and apologise if this is an affront to the original poster;
I have no evidence that this is so. I am probably unduly influenced by
the 17 386 249 other posts here which blame anything but themselves
for their problems.


Dec 12 '07 #5

P: n/a

"Tom van Stiphout" <no*************@cox.netschreef in bericht news:6f********************************@4ax.com...
On Wed, 12 Dec 2007 12:58:48 +0100, "Arno R"
<ar****************@planet.nlwrote:

Would it also help to map a drive letter to that deep path, and link
to x:\backend.mdb?

-Tom.
Yes that would help also I guess ...
I did not suggest that because I prefer UNC path's.
I have had 'issues' with mappings before ...
(like one user mapping to X, and another mapping to Y)

Arno R

Dec 12 '07 #6

P: n/a
lyle wrote:
On Dec 12, 10:43 am, Arch <send...@spam.netwrote:
>>On Wed, 12 Dec 2007 02:27:39 -0800 (PST), bg...@yahoo.com wrote:
>>>Hi,
>>>My company's backend is located at a location with a long address,
something like -
>>>//our_servers/server_number_one/our_department/our_devision/
our_results/our_databases/backend.be
>>>I have tested the very same backend on another server with a sort path
location at it works fine, but at the location above it is extremely
slow. I've also tested the speeds of both servers and they are the
same with regard to coping to and downloading files from each.
>>>I've asked to get the backend moved but I have been met with a wall of
beurocracy since our servers are organised in this departmental
fashion. Today someone even remarked that surely there is a patch for
this problem and that I shouldn't be wasting their time asking to have
files relocated...
>>>So, my question is, is there a patch or an alternative solution to
this problem since the only solution I have found is to move the
database.
>>>Thanks,
>>>Barry.

There is no patch for this problem. It is a Windows/SMB
characteristic, not an Access bug. Windows needs to authenticate at
each directory layer in the share, so the deeper it is, the slower it
is.

As others have suggested, about the only solution is to get them to
create a share much lower in the directory structure.


For more than ten?? years I have had users' frontend databases linked
to backends so deep I don't even think about remembering the path. And
the servers themselves are in the basement catacombs; rumour is that
if you get lost and stumble into one of these rooms you are never
permitted to leave (well, they're so cold that you freeze to death
pdq).
The names of the folders are not especially short. Toss in "Employee
Services Personnel Manager Class I Teaching Staff" and one can get
some long strings.

The front end is instantaneous in retrieving data from the backend,
and in sending data to the backend. I've fooled around with the
backend on a local machine, and there is no noticeable difference in
the speed of the applications under that condition.

I am nothing of a network geek, but surely Windows does not run
thorugh a full authentication routine everytime I press the down arrow
when browsing a continous form, or run a simple select or update
query?

My guess is that the database and the interface are poorly designed
and that IT knows this and is unwilling to throw any more of its time
at making it work properly.

I'm sorry and apologise if this is an affront to the original poster;
I have no evidence that this is so. I am probably unduly influenced by
the 17 386 249 other posts here which blame anything but themselves
for their problems.
I'm not sure if this addresses the issue at all.
http://support.microsoft.com/?kbid=891176. There's also
http://support.microsoft.com/kb/889588/.

It might have been at Tony Toews site or else he had a pointer to a kb
article that mentioned moving the folders close to the root.
Dec 13 '07 #7

This discussion thread is closed

Replies have been disabled for this discussion.