Slow access to Links

P

Peter F

Hi All,

I need some information to resolve problems which we are experiencing these
are explained fully below.

Management are attempting to drive down the cost of legacy via the
accelerated closure of some infrastructure core nodes 1 & 5.

Basically this gives two problems to solve:

1. Rehoming of last 100 or so live User accounts on CN1 and CN5
2. Finding an alternative home for the shared data currently held in file
store at each core node - a new WSS Farm has been setup at CN4
Progress so far:
All user accounts on CN1 successfully rehomed. Every reason to believe that
same process will work for user accounts on CN5
Migration of CN5 not yet commenced following the identification of issues
below:
1. Access databases
There are over 2000 access databases on CN5 totalling around 9GB in size. A
number of these are obsolete and the user base are doing some house keeping.
A number of these are deemed business critical - these are known as Registry
or CDC databases. Basically, these databases contain hyperlinks to various
documents and I believe that this is the way in which users find documents.
The main users of this approach are locally based and hence are local to the
data. Some of these databases were copied to CN4 for trial purposes and the
performance of opening these database is deemed unacceptable. Not a total
surprise for access databases over the WAN.
2. Static Hyperlinks from Access Databases
The CDC databases identified above contain absolute rather relative
hyperlinks - hence moving the data will cause the link to fail
3. Static Hyperlinks in Documents
Similarly the documents contain absolute rather relative hyperlinks - hence
moving the data will cause the link to fail
4. Network Performance & Capacity
We have investigated loading on the appropriate Service Deliver Points and
also bandwidth across the channel - none of these are overloaded at present,
although we would need to uplift the bandwidth of the CN4 SDP to cater for
the additional traffic if the CN5 data was to be moved there. Network
latency on the cross channel link has recently been measured as quite high
(150ms). Local Users have done some trials on different file types at CN4
Word, Excel, Powerpoint and are generally unhappy.
We've had some loose discussions around can we hold the access databases
locally? Maybe the users could replace the hyperlinks in access databases
with relative via find and replace. We have no idea what to do about
hyperlinks in documents. The user have recognised that static hyperlinks are
not the way forward, and are happy to proceed with relative hyperlinks going
forward if someone solves the "today" problem.

My initial conclusions are
That there are outline options which would lead to the closure of CN5 - my
suspicion is that there is a "Minimum Operable Solution " which would allow
the users to continue to operate (albeit with some pain) and will allow the
closure on CN5. There is probably one or more solutions which would cost
more, take longer, but provide more benefits to the users.

I would be interested if anyone on this forum has come across or could offer
any advise.
 
S

Stefan Hoffmann

hi Peter,

Peter said:
Management are attempting to drive down the cost of legacy via the
accelerated closure of some infrastructure core nodes 1 & 5.
[..]
Not a total surprise for access databases over the WAN.
If you're really running on a WAN, then your performance issues arise
from its lower bandwith. Not from the (hyper-)links per se. The
(hyper-)links may trigger your problem insofar name resolution is
required and latencies may add up to an point where usability is no
longer given.
I would be interested if anyone on this forum has come across or could offer
any advise.
Honestly, 2000+ databases means a lot of work. Depending on the
importance I would say: get some professional assistance.
We've had some loose discussions around can we hold the access databases
locally? Maybe the users could replace the hyperlinks in access databases
with relative via find and replace.
Consolidate your backends respectivly your data. Evaluate SQL Server
2008 and its FILESTREAM data type. It can handle files stored in the
"database" quite nice. Indeed it saves them as files but you can backup
them easily using the built-in features.
We have no idea what to do about hyperlinks in documents.
Hyperlinks in Office documents can be manipulated via Automation in VBA.


mfG
--> stefan <--
 
N

NICOLHOLAS JAMES BEGGS

plames for my work in satash in ESSEX molland line 109 south Ockondon
 
P

Peter F

Hi Steffan, Thanks VM for the reply.

Do you have further information on SQL etc and in particular you mention
FILESTREAM? What exactly is that and where can i get information on this.

Can you also elaborate on Office documents can be manipulated via automation
in VBA. Can you offer any examples of this.

Any information would be greatly appreciated.

--
Flinty


Stefan Hoffmann said:
hi Peter,

Peter said:
Management are attempting to drive down the cost of legacy via the
accelerated closure of some infrastructure core nodes 1 & 5.
[..]
Not a total surprise for access databases over the WAN.
If you're really running on a WAN, then your performance issues arise
from its lower bandwith. Not from the (hyper-)links per se. The
(hyper-)links may trigger your problem insofar name resolution is
required and latencies may add up to an point where usability is no
longer given.
I would be interested if anyone on this forum has come across or could offer
any advise.
Honestly, 2000+ databases means a lot of work. Depending on the
importance I would say: get some professional assistance.
We've had some loose discussions around can we hold the access databases
locally? Maybe the users could replace the hyperlinks in access databases
with relative via find and replace.
Consolidate your backends respectivly your data. Evaluate SQL Server
2008 and its FILESTREAM data type. It can handle files stored in the
"database" quite nice. Indeed it saves them as files but you can backup
them easily using the built-in features.
We have no idea what to do about hyperlinks in documents.
Hyperlinks in Office documents can be manipulated via Automation in VBA.


mfG
--> stefan <--
 
S

Stefan Hoffmann

hi Peter,

Peter said:
Do you have further information on SQL etc and in particular you mention
FILESTREAM? What exactly is that and where can i get information on this.
http://technet.microsoft.com/en-us/library/bb933993.aspx

Can you also elaborate on Office documents can be manipulated via automation
in VBA. Can you offer any examples of this.

http://msdn.microsoft.com/en-us/library/aa221980(office.11).aspx
http://msdn.microsoft.com/en-us/library/aa212507(office.11).aspx


mfG
--> stefan <--
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top