RE: Where to keep the data?
- From: Leemi@xxxxxxxxxxxxxxxxxxxx (Lee Mitchell)
- Date: Tue, 07 Jun 2005 19:13:54 GMT
Hi Paul:
I have not strong feeling either way regarding storing a DBC on a server
verses storing the DBC locally. A lot depends on the amount of network
traffic you expect the site to have. If they have a busy network, you
might be better off storing the data locally. Also, you have to consider
the speed of their connection.
You mention the server might go down in certain cases. Have they
considered getting a UPS power backup for the machine?
You certainly keep some of the data in DBF file if you find that easier.
Doing so eliminates the need to access data via ODBC or OLE DB Provider and
will most likely be faster.
I hope this helps.
This posting is provided "AS IS" with no warranties, and confers no rights.
Sincerely,
Microsoft FoxPro Technical Support
Lee Mitchell
*-- VFP9 HAS ARRIVED!! --*
Read about all the new features of VFP9 here:
http://msdn.microsoft.com/vfoxpro/
*--Purchase VFP 9.0 here:
http://www.microsoft.com/PRODUCTS/info/product.aspx?view=22&pcid=54787e64-52
69-4500-8bf2-3f06689f4ab3&type=ovr
Keep an eye on the product lifecycle for Visual FoxPro here:
http://support.microsoft.com/default.aspx?id=fh;[ln];lifeprodv
- VFP5 Mainstream Support retired June 30th, 2003
- VFP6 Mainstream Support retired Sept. 30th, 2003
>I'm involved in migrating an existing multi-user application from FoxPro
>data on a file server to a SQL Server (MSDE actually) back end. The move
is
>desired partly for security reasons (the application will handle money and
>accounts eventually), partly to make the data more accessible (with
security
>provisions) to outside processes, and partly for data integrity concerns
>(the server is at some distance from the workstations, and there are
>occasional service outages due to hardware problems).
>I have two questions.
>1. Is it better for each installation to have its own local copy of the
dbc
>(I'm using only remote views, so far), or to keep the dbc shared on the
file
>server? Keeping it local has some advantages, speed for one because it can
>be opened exclusive, plus I don't have to keep track of where the database
>is.
>OTOH, I already have another client-server application that shares the dbc
>on a file server, and it has worked pretty well so far. (In this case, I
>have to do it this way because there is shared data that I am not allowed
to
>keep in the back end database). This approach does require that each
>workstation be set up with an ODBC source with the same name, so that the
>connection in the dbc can find it. Also, this makes installing new
versions
>of the database much easier.
>2. If I go with the shared-dbc-on-the-file-server approach, is there
>anything wrong with keeping "some" of the data in ordinary dbfs? Certain
>things, system preferences etc. don't need security or even special
>integrity, and are easier to browse and tweak if they're kept in a dbf.
>Suggestions or insights will be much appreciated.
.
- References:
- Where to keep the data?
- From: Paul Pedersen
- Where to keep the data?
- Prev by Date: Re: Where to keep the data?
- Next by Date: Re: Copy Structure to Cursor
- Previous by thread: Re: Where to keep the data?
- Next by thread: Re: Where to keep the data?
- Index(es):
Relevant Pages
|
