Results 1 to 3 of 3

Thread: Minimum amount of RAM??

  1. #1

    Thread Starter
    Hyperactive Member compuGEEK's Avatar
    Join Date
    May 1999
    Location
    Mpls,MN,USA
    Posts
    281

    Question

    Hopefully someone will agree with me on this....

    My boss wrote a lengthy, bulky program that uses
    the Data Environment designer and a stored procedure
    that queries several tables. Most users of this program
    reside here on our local NT network.

    This program writes data to a SQL 7.0 database. It also
    performs full-text searches. Our users have NT Workstations, ver 4.0 and systems with 64 Megs of RAM or less.

    There is roughly around 15 - 30 simultaneous users of this program, some access it remotely, through an internet connection.

    At this point, re-writing the program is not an option.

    The users here on our local network are experiencing
    EXTREMELY slow results from the program. I suggested that
    the users of the program should have more RAM installed and need AT A MINUMUM, 64 Megs of RAM just to run the operation system, let alone a bulky program!

    My boss disagree's with me and insists that 48 to 64
    Megs is plenty of RAM and that there should be no performance issues at all!

    Surely someone must agree with me!! Does anyone know of
    some documentation or something that I can show him to
    prove my point?


  2. #2
    PowerPoster 2.0 Negative0's Avatar
    Join Date
    Jun 2000
    Location
    Southeastern MI
    Posts
    4,367

    How are you connecting to SQL???

    How are you connecting to the SQL database.

    I have found that ADO can be slow connecting to the SQL database. If you are using ADO try opening any recordsets with
    Code:
    rs.Open SQL, DB, adOpenForwardOnly, adLockReadOnly
    I do agree with your boss that the RAM they have is sufficient to run the program.

    Just a thought

  3. #3
    Guest
    Check the SQL in the stored procedures, make sure he is using the most efficent SQL Possible, Verify the indexes used , make sure he's not querying unnecessary fields, stuff like that. If the SQL is poorly written no ammount of memory can polish it.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width