Re: Access and Terminal Server????

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Albert D. Kallal (PleaseNOOOsPAMMkallal_at_msn.com)
Date: 05/17/04 

Date: Mon, 17 May 2004 13:23:46 -0600

Using TS means that if your current system performs well, then I see NO
reason to upgrade to sql server.

However, some issues of growth etc are important. (and, how well does the
system run now?).

And, I assume that you always installed, and ran the access front end on
each pc..right? (it should not be shared).

180 megs is not large (is that the size after doing a compact"). However,
180 megs after compacting is a nice chunk of data.

If your current system performance well right now..then moving to TS would
clearly work just great..and in fact, would likely increase reliability of
your system. (and, it could very also increase performance of your access
system also).

So, I would certainly "consider" sql server for the future...but if your
current system runs well now..then you have time on your side to make the
decisions to move the back end to sql server. If it works well now..then you
don't have to "hurry" to move to sql server. If growth of data and users is
in the future..then again sql server makes sense...but no hurry!

However, using TS does not really change this issue much. Also, that font
end of 30 megs again sounds large (any graphics on screens etc?). I have
medium sized application with 160 forms, about that many reports..and lots
of code. The total size of the mde file (you are using a mde for your users
..right??)...is only 6 megs in my case.... 

-- 
Albert D. Kallal   (Access MVP)
Edmonton, Alberta Canada
pleaseNOOSpamKallal@msn.com
http://www.attcanada.net/~kallal.msn

Relevant Pages

  • Re: What Hardware?
    ... OK, I'll leave you to do the sums, do you know what the database growth ... You should plan your hardware for growth three years down ... > have this information you will be able to plan your disk, RAM, and CPU ... >>SQL Server 2000 Operations Guide: ...
    (microsoft.public.sqlserver.server)
  • Re: Alter Table for 39 million rows
    ... Sometimes SQL Server will change all the ... NO TABLE GROWTH ... Moving from a fixed character type charto charforced the ... Moving from smalldatetime to datetime caused growth and was slow as ...
    (microsoft.public.sqlserver.programming)
  • Re: tempdb size
    ... SQL Server will not log the growth of any database in system tables. ... provide a higher Tempdb MDF and LDF size; so as auto growth will not happen. ... i want to put tempdb on some realy fast device, ...
    (microsoft.public.sqlserver.setup)
  • Re: Generating one table with a terabyte of data
    ... I've locked SQL server to 1/3 physical memory usage. ... DB growth is 512Meg ... > I've locked SQL server to 1/3 physical memory usage. ... > chunks. ...
    (microsoft.public.sqlserver.dts)
  • MS Access with Linked tables Security Issue
    ... ..mde file with the linked tables with SQL Server with ODBC connection. ... I have six users each has user id and password to access SQL Server. ... There is no authentication on the front end (.mde file). ... file since they can create a mdb file and have access to all the data. ...
    (microsoft.public.access.forms)