Re: SharePoint Services
- From: Salad <oil@xxxxxxxxxxx>
- Date: Wed, 15 Apr 2009 21:29:03 -0700
Earl Anderson wrote:
I didn't read/see anything in this thread about performance. Would placing the BE on SharePoint improve performance (speed)? I'm so frustrated and disappointed with our split db's slowness on the network that I am almost regret my championing the switch from an 'old' production db to the much more versatile Access app we are using now. All of the advantages of the many features and functions in the Access app are totally diminished by its 'slowness' on our network. I'm searching for ways to improve the performance such as having IT move all of the other folders/files one level down from our app so that it stands alone on the directory it's located. Yes, all of the updates, solid connections, patches, etc. are preformed by IT nightly thru their Radaii system. All of our queried fields are indexed. The auto name correct (or whatever it is called) is turned off as well as in the subforms.Lyle Fairfield wrote in the past...
I'm trying to convince IT to give (purchase) us our own server so that nothing else is on it but our app as this may speed queries, opening forms, and printing significantly..
Thus I was intrigued by this discussion here on the SharePoint possibility as our department has recently been introduced and given an IT -sponsored/supported SharePoint portal. Maybe this is the answer.
An insights and thoughts here are appreciated....
Earl
I run Office 2007 on a desktop with an Intel E6750 (dual) cpu and 2 gigs
of ram. It's fine, fast if not snappy.
But on other, older computers with a single processor it's been
gruesomely slow and I've uninstalled it and reinstalled Office 2000, 2002 or 2003 depending on what seemed suitable (for instance, Office 2000 on a Celeron 1.7).
If I were going to work with Office 2007 extensively I'd look at a quad
processor, and a 64 bit operating system so I could access several gigs
of ram. But maybe I'm doing something wrong.
http://groups.google.com/group/comp.databases.ms-access/browse_thread/thread/e44a1a555dd42ecd/5e60cd1cb832fe5e?q=speed+2007+group:comp.databases.ms-access#5e60cd1cb832fe5e
Have you followed tips at Allen Brownes or Tony Toews sites? Do you have NameAutocorrect on? Use long filenamea (over 8.3)? Deep folder structures?
http://allenbrowne.com/search.html
http://allenbrowne.com/VistaCPULoad.html
http://www.granite.ab.ca/access/performancefaq.htm
"Albert D. Kallal" <PleaseNOOOsPAMmkallal@xxxxxxx> wrote in message news:0GeFl.42403$ua7.25373@xxxxxxxxxxxxxxx.
"Don Leverton" <NoDamnSpam@xxxxxxxxx> wrote in message news:91eFl.22142$Db2.13250@xxxxxxxxxxx
Enter the SharePoint idea.
=====================
For the purposes of my app ... I'm under the impression that the data tables ("lists") can be uploaded to a SharePoint location, and that read / edit permissions could be enabled for different users???
Correct. Keep in mind there there are size (performance) limitations in terms of the size of these SharePoint linked tables. While you can stuff 80,000 rows into one of a share point lifts, I would suggest that if the using this over and the kind of general intranet connection, I would keep the size of those tables below 10,000 records, in fact in the 6000 record range is OK.
if you have some typical sable sizes with 50,000, or even 100,000 records, then I'll suggest that you use a SQL server as the backend and link that over the Internet in place of sharepoint.
Each location / user PC could have a run-time version and the MDE stored locally, and have these SharePoint "lists" (on the internet) as the BE?
correct, but keep in mind that the "offline" mode does not work for the runtime version. What this means is that once you link your tables to share point, if you have the full version of access, you can click on the offline mode, and then the traveling salesman can go on the road or go to some salmon are some of entropy is some location where they don't have a good Internet or any Internet at all. Once they back to some similar to Civilized palce like a good wifi connection at their local coffee shop, then they can go back "on line" and their changes are synchronized for automatically. so a big feature the full version as compared to the runtime version is is offline mode, which in effect is really recognize shun for you for free with no additional programming required.
Is there a charge for using these "SharePoint Services"?
This is kind of like asking is there a charge to host your web site? if you are to have some company servers with Internet server services running on them, then it won't cost you anything.
So if your company does not have SharePoint up and running now, then you'll have to purchase a setup and install share point services. Or you can use the "on-line" edition from Microsoft called office live.com. Office live is really great because it is ShaerPoint for free. The 1st 5 users and the first 50 megs of data storage is free. after that you can purchase additional users and additional storage. kind amazing that you get the setup for free. When I entered this computer business many years ago, a five user computer with a 20MB drive was about $35,000.00. Now it is free, and you can have it up and running and less time it takes for me to write this post to you.
Could I do the same thing using our existing "intranet"?
if your plan is to use sharepoint, and you have share point running in your company now, then yes you can (and should consider this). However if you do not have share point services setup, nor do you have the expertise and training and resource personnel to run and set up those servers + SharePoint, **if** you users NOW have some type of connection to you network (a vpn), then then I think the easiest and least amount of effort would be to simply put the backend database on SQL server and and link your front ends to that back end user. this approach is better than share point for seveal erasons:
- you don't have the same performance and table size limitations like you do and share point as I mentioned. also keep in mind that linked tables to share point to not have a reference will integrity to nor do they have cascade deletes like SQL server does.
- Far lower costs and less work because you don't have to learn share point. Setting up SQL server is free today and is very low cost, and quite easy to learn. so full of people are to have a connection to your network, then you can get them connected to SQL server quite easily.
- however don't underestimate the usefulness of share point, as it allows document sharing, allows you to share data + documents with customers. and as mention it supports the offline replication mode for access databases if you need this feature.
Office2007 also offers some sort of free file storage space, but it looks like only Word, Excel, and Powerpoint (?) documents can be opened and viewed directly online?
Not really...access tables can also be opened with a web browser. I'm tempted to publish and show you what an access table looks like from your web browser.....
I will need to be relatively careful, as my app will contain customer contact information, as well as vendor site logins / passwords ... so I don't want Joe Hacker having free access to this information either.
The above reasons one reason why share point is really good, The management of users and logons in granting permissions to view data is all built into share point in is quite easy to use. So the these details are made relatively easy for you. However, this is a moot issue if those people NOW have a connection to your corporate network. In this case, then SQL server is the most easy approach here.
So, if these people are outside of your corporate network now, then expertise and ability to set up secure connections to allow them to come into your corporate network and pull data from sql server is VERY seriuos issue. Again this type of scenario that supports the free online edition of share point, because then you don't expose your corporate network to these people and it's relatively easy to add a few users and connect them up to a shared linked table on SharePoint with "any" Internet connection and may have. Furthermore you don't have some complicated system in which these users have to be given access to your corporate network outside or when they're traveling on the road. so this issue really comes down to what kind of connection and what kind of access is they have now, or how easy you can get them access to corporate network.
As I said the beauty of "office live" on line share point is you can have SharePoint up and running and be testing a linked table in less time it takes for me to write up his post...
So, keep in mind that linked lists in share point are not as flexible as "related tables" we have in access or when we link to sql server. So, if you have a highly complex access application with many related tables and many rows in those tables, then I don't think sharepoint is the solution right now for you.
--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pleaseNOOSpamKallal@xxxxxxx
- References:
- SharePoint Services
- From: Don Leverton
- Re: SharePoint Services
- From: Albert D. Kallal
- Re: SharePoint Services
- From: Earl Anderson
- SharePoint Services
- Prev by Date: Re: SharePoint Services
- Next by Date: Re: SharePoint Services
- Previous by thread: Re: SharePoint Services
- Next by thread: Re: SharePoint Services
- Index(es):
Relevant Pages
|
