Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Should I utilize citrix for this application ? 2

Status
Not open for further replies.

DaveSH

Technical User
Aug 21, 2000
62
US
I am posting this question in multiple forums due to the various issues involved. I am looking for any experiences and or suggestions to help me make decisions.

I currently have an Acess mdb for document control in our engineering group running at 2 different sites. One in PA and one in AZ.

Architecture:

-The 2 sites have NT networks and are now connected via T1
-We have a citrix server running at the AZ location to support the companies main business operating software. This could be used.

Goals

-I want to combine the tables of the 2 separate databases, and begin to run out of a common database.

-I would like to stick with access if I can.

-Primary administration will be done from PA.

Basic Info:

-The usage of this database is relatively low.
-It is only edited for a few minutes at a time usually by a handful of users.
-Another 10 or so users may acces it read only 15 minutes a day or so.
- Current size of front end is about 1 meg.
- Current size of back end is 800K in PA and 500K in AZ
- I estimate back end size to grow steadily at about 1-2 meg per year.

The main questions I have at this point are:

1 Where to store the Tables ?

2 THe database contains OLE links to CAD drawings The Cad drawings will be stored on networks at both sites. Should I / can I create some sort of local table to store these links.

3 What is the best method of combining the tables where an autonumber PK field is used as a foreign key in relationships without disrupting the relationship.

4 Should I run the database on the AZ server and utilize the Citrix server.
Dave
gallagherd@earthlink.net
 
Since I have a slight bias towards Citrix, I will answer from this perspective;

I would recommend storing the tables on a fileserver - possibly a BDC, if your setup is relatively small, or a server which already performs this function.

If the CAD drawings are large, ie >5mb, then there will be a noticable time lag using Citrix, since the data will be squeezed down a 20k pipe. I would be surprised if you couldn't create a table of links for these in Access.

I won't attempt to answer the foreign key question - it's been too long since I last played with Relational Databases!

The fileserver containing the database is better off on the same network as the Citrix server, since the Citrix server will act as a client to the database. I have installed many similar setups, and found this to be a particularly good scenario for a Citrix solution.

I hope this helps
 
I would have thought that this is a bit of a dodgy scenario for Citrix, being as my understanding of Access is that a client queries the db and downloads the data for processing then sends the whole lot back. i.e. your Citrix server will be doing the maths for you db server, for each client it hosts. Also you will be squeezing all this data up and down the network along with those intense CAD images.

Can you not redesign you db for SQL, which is more of a client-server db, in that the maths are done on the db server and not by the client host. I appreciate thatyou say the db has low usage, but I feel that your main business software will suffer the 'surges' and can you be sure it will remain low?

Incidently are we to assume you have the one Citrix server, already hosting the main software? 10 clients is relatively quite a lot of additional users when talking Citrix.

You will also need to think about the spec stuff, how much available girth does your Citrix have? the other server, what are your client PCs? how good is the network?
pritch
 
I have set up many such Access databases - and even a few Oracle databases to run over Citrix. There IS a performance hit - but you'd need to take that into account.

The processing is still done at the server, so the main areas to look at are RAM useage (an extra 8Mb per user at least) and processor useage (around 5 users per processor less if all users access the database, with adjustments as necessary for actual user numbers). If 10 users are accessing it for 15 minutes per day, I don't think the hit would be significant.

The clients are, in my experience, irrelevant - I have run Access databases on Psion handhelds over a wireless connection, with Outlook open in the background.

Your point about the server muscle is good, though, pritch.

I still maintain that this scenario is almost tailor-made for a Citrix solution ;-)

The key word (one of my favorites, in fact) is TEST.

I hope this helps
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top