Re: File size warning

You could write a simple utility in .NET using the directory watcher
component. It is very simple, and you could even have it run the compaction
by itself whenever the critical size is reached. You DON"T need to move to
SQL Server. The cost is over ten thousand dollars for a single processor
license. Why is it that Access is marketed as a database product, yet when
it gets used, they tell you to buy SQL server? If Access can't handle data,
then it should be taken off the market. The fact is, I've known people who
had Access databases grow to very large sizes, and then they simply split
them. Very simple, and cost affective. (You simply end up with 2 or more
smaller databases). Also, SQL Server or MSDE will tie you to a single
server. With access, you can drop the file on an external drive, or use it
on multiple computers. If you do need to access it from the network, you can
simply set up a datasource on the computer and have multiple computers use it
at the same time. It is pretty fast, and you won't have to hire a DBA just
to manage it.
Sorry to get on my soapbox, but not everyone can afford to buy SQL server, a
dedicated server, and all that. I think that Access is more than sufficient
for more than 70% of enterprise database needs, and in most cases, SQL Server
or Oracle 10g would be major overkill. With Access, all you need is Access.
With SQL server, you need to make sure you have a computer that can handle
it, plenty of memory, and (of course) pay a large license fee. Not only
that, but next someone will recomend that you deploy this on a Windows 2003
server. Access works fine on Windows 98. Backups with access are as simple
as making a copy of the .mdb file. In client server DBMS you must have a
plan for backups, and it is usually much more complicated than simply copying
the file to a backup storage location. My son can manage Access databases,
with no training, spending only a few minutes a day. He would have to go to
school to learn SQL Server. Which is really more cost effective?
I have been using databases since they existed. Now I use MySql, which is
more powerful than most databases, and is free. Plus, you can keep your data
in a MDB file, but it can grow to as large as your filesystem's file limit
is. Also, you can use it from windows 3.1 through XP. Your other
applications won't even know the difference. I hope you can solve your
problem. Let me know if you need help with a .Net application which will
monitor the file and notify you when it becomes massive. It can be done in a
couple of hours, and I would gladly write it for you in Visual Basic.NET
2005, and I would give you the source code.
--
Together, We CAN change the world to make it fair for us. We CAN elimanate
the digital divide and corect the indjustices and take back our country.
Visit http://www.naacp.org/unitedblacks


"Pegasus (MVP)" wrote:


"Herb" <HE@UK> wrote in message
news:%23nAa2gi6GHA.4996@xxxxxxxxxxxxxxxxxxxxxxx
On 06.10.2006 13:56 UK Time, Pegasus (MVP) wrote:

In any case, my aim is to implement some kind of 'warning system' so
that I can compact the database manually when the size reaches, say,
750
MB.
Herbert Eppel
--
www.HETranslation.co.uk

Use notepad.exe in order to create the file
c:\documents and settings\all users\start
menu\programs\startup\netlogon.bat

and place these lines inside:

@echo off
set MaxSize=750000000
for %%a in (d:\big.dbf) do if %%~za GTR %MaxSize% call :sub %%~za
goto :eof

:Sub
set /a S=%1/1000000
echo.
echo The size of the database is now %S% MBytes.
echo.
echo Press the Space Bar to close this window.
pause > nul

Because the file resides in the startup directory, it will execute
each time you log on.


Hello again,

at first this didn't work, but then I realised that I have to enclose
the path names in quotes because my path name contains a space!

It now works very well - thank you very much again for your time.

I guess the next step would be to automatically call up my third-party
translation memory database program (which, incidentally, is called Déjà
Vu - see http://www.atril.com/) and compact the file in question, but
I'm not sure whether the program allows compaction to be run from the
command line :-\

Perhaps I need to ask this question in the Déjà Vu support forum?

Regards

Herbert Eppel
--

Thanks for the feedback and yes, a Déjà Vu forum would be
the right place to ask this question.



.

Relevant Pages

  • shell script question
    ... each table in each database in a Sybase SQL Server, ... me why does function columns failes to print the output of sp_help. ...
    (comp.unix.shell)
  • Re: shell script question
    ... each table in each database in a Sybase SQL Server, ... me why does function columns failes to print the output of sp_help. ...
    (comp.unix.shell)
  • Re: shell script question
    ... each table in each database in a Sybase SQL Server, ... me why does function columns failes to print the output of sp_help. ...
    (comp.unix.shell)
  • Re: Delete in SQL Server
    ... Not that in any effect changes the validity of your statement from a user perspective: ... SQL Server does not remove the row from the page when a row is deleted. ... But a clean up process can do the compaction earlier then that (spid ... >> the Database Table? ...
    (microsoft.public.sqlserver.programming)
  • Re: MS Access DAO -> ADO.NET Migration
    ... William Vaughn ... Microsoft MVP ... Hitchhiker's Guide to Visual Studio and SQL Server ... My migration app works building a SSCE database file with imported data ...
    (microsoft.public.dotnet.framework.adonet)