Re: Access DB grows too fast.

From: William \(Bill\) Vaughn (billvaRemoveThis_at_nwlink.com)
Date: 06/29/04


Date: Mon, 28 Jun 2004 17:49:37 -0700

Be advised that the current version of MSDE is limited to 2 GB as well--per
database. However, I suspect that this will not be an issue. Ask me again
about this after TechEd... I think MSDE will be far (far) better suited to
your needs. Remember, it's really SQL Server. The easiest approach to get
started is to pick up the $35 ($49 SRP) Developer Edition that has all the
tools you'll ever need.

hth

-- 
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
"Nate Clark" <ntclark@attglobal.net> wrote in message
news:40E0B620.60504@attglobal.net...
> Thanks very much for the advice Bill. It helps me more than you might
know.
>
> I didn't even know about MSDE. A quick search found it and that is
> something I think I can really use.
>
> This particular application is one that I inherited a few months ago and
> it had been completely built with an Access database. Thare are huge
> processing requirements all throughout the application that are done in
> SQL over Access and quite frankly bring it (Access), to it's knees.
>
> Even though this application is in that stage between Beta test and
> delivery, I think that given the circumstances and problems I've been
> encountering with the more "real world" data sets, having any different
> client only DB is going to ward off substantial problems in the future.
> Not the least of which is this "rumor" of problems with an Access DB
> over 2 GB. It is certainly worth a try !
>
> I also have another system that makes heavy use of a client side DB for
> which I've had to dance around it's limitations for 5 years now,
> currently using the precursor to Adapaptive Server Anywhere for this
> system. I have been wanting to replace it's client side DB and this
> looks like just the ticket !
>
>
> Thanks again !
>
> Nate Clark
>
>
> William (Bill) Vaughn wrote:
> > I expect that there's some "modifying" going on. I don't recommend
> > SQLPrepare for SQL Server as all of the more recent drivers/providers
don't
> > need it. If I were you I would switch to MSDE where the operations can
be
> > more closely monitored and it's designed for more throughput.
> >
>


Relevant Pages

  • Re: MSDE advice required... Moving from Interbase -> MSDE
    ... > MSDE. ... > Interbase 6.0 database. ... a Windows server edition, but MSDE can runs on Win98 too, but I have no ... If the same server hosting the MSDE instance acts as a UI client as well, ...
    (microsoft.public.sqlserver.msde)
  • Re: Data corruption with SQL server installed
    ... I noticed that the rogue Primary key that appeareed with the .AddNew method ... The installation of MSDE comes after the installation of MDAC 2.8, ... you could create an empty database and import everything into ...
    (microsoft.public.access.tablesdbdesign)
  • Re: vb.net/sql server speed issue
    ... Well this is my concern and that of my client... ... dataadapter hit the database build a dataset and drop the connection.... ... > MSDE is the same engine as SQL Server but it has 2 major limitations. ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Put database on Internet
    ... > Once you will be able to connect to MSDE or to SQL-Server, ... > and ADP in the same time as frontends to your database. ... >> will be able to serve as SQL server. ...
    (microsoft.public.access.dataaccess.pages)
  • Re: Connect to Access Data from various regional locations
    ... All users will be connecting via broadband. ... When using MSDE ... > Dim rf As DAO.Recordset ... > There is a wizard to split your database into a FE and a BE; ...
    (microsoft.public.access.externaldata)