Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM Client/Server » View Thread |
Messages 1 to 8 of 8 total |
Server Machine Requirements |
Wed, Apr 26 2006 10:54 AM | Permanent Link |
"Johnnie Norsworthy" | I am going to be converting my existing customers to client/server from a
local access system (LAN-based). The new server data will be access over a LAN and by the internet. Is there a document describing server machine requirements available anywhere so I don't miss any points when I explain what is necessary for my customers' network support personnel? Things like: TCP/IP ports need to be open, forwarded to server machine Memory and other system requirements Thanks, Johnnie Norsworthy |
Wed, Apr 26 2006 11:01 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Johnnie,
<< Is there a document describing server machine requirements available anywhere so I don't miss any points when I explain what is necessary for my customers' network support personnel? >> There really aren't any requirements due to the fact that the database server will run in practically any configuration. It may not be optimal, but it will run. << Things like: TCP/IP ports need to be open, forwarded to server machine Memory and other system requirements >> Well, yes, the obvious things that need to be taken into account is that TCP/IP support must be on the machine and in working order, and the two ports used by the DBISAM database server must be open if you want to access both the standard data port (12005) and the admin port (12006) from outside of the server machine. As for memory, 512 megs or more is usually sufficient, but it really depends upon the number of expected concurrent sessions on the database server, which you didn't mention. -- Tim Young Elevate Software www.elevatesoft.com |
Wed, Apr 26 2006 11:34 AM | Permanent Link |
"Johnnie Norsworthy" | "Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
news:F4352102-C534-4E86-94A8-06FBB253E9E1@news.elevatesoft.com... > Johnnie, > > << Is there a document describing server machine requirements available > anywhere so I don't miss any points when I explain what is necessary for > my customers' network support personnel? >> > > There really aren't any requirements due to the fact that the database > server will run in practically any configuration. It may not be optimal, > but it will run. That's the kind of thing I mean. I know the Delphi IDE will run in a low amount of memory but it would be unbearable. I was just looking for a general idea considering the number of concurrent users, maybe increments like 1-5, 6-25, 26-50, 51-100. Though I have installations of almost 200 machines, I don't think there would ever be more than 50 concurrent users of my server. > > << Things like: > TCP/IP ports need to be open, forwarded to server machine > Memory and other system requirements >> > > Well, yes, the obvious things that need to be taken into account is that > TCP/IP support must be on the machine and in working order, and the two > ports used by the DBISAM database server must be open if you want to > access both the standard data port (12005) and the admin port (12006) from > outside of the server machine. As for memory, 512 megs or more is usually > sufficient, but it really depends upon the number of expected concurrent > sessions on the database server, which you didn't mention. I am going to organize my document into three parts: MACHINE REQUIREMENTS: OS, Memory, CPU speed, UPS system NETWORK REQUIREMENTS: TCP/IP, firewall/router setup PERFORMANCE: What can be done to improve LAN performance and remote internet performance such as increasing upload bandwidth How using the machine as a workstation might degrade performance or cause problems if other applications crash. If I get the document looking good enough, I'll post it to the binaries group for others in the DBISAM community to use as well. -Johnnie Tim, thanks so much for the great support here all the time. |
Wed, Apr 26 2006 12:10 PM | Permanent Link |
"Ralf Mimoun" | Johnnie Norsworthy wrote:
> I am going to be converting my existing customers to client/server > from a local access system (LAN-based). The new server data will be > access over a LAN and by the internet. > > Is there a document describing server machine requirements available > anywhere so I don't miss any points when I explain what is necessary > for my customers' network support personnel? > > Things like: > TCP/IP ports need to be open, forwarded to server machine > Memory and other system requirements I'd say, to be safe: - CPU: Pentium D or any other dualcore - RAM: 2 GB - HD: 2 fast ones, Seagate Spinpoint JJ or WD Raptor, mirrored - Gigabit ethernet - Windows Server, because Prof. has a limitation of 10 concurrent TCP/IP connections. That should be more than enough for most installations, and it's standard stuff. If you only have 5 users and there is not much to do for the server, you can live with a cheap Sempron 3000+, 512 MB machine with Win2k Prof. Ralf |
Thu, Apr 27 2006 11:00 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Johnnie,
<< That's the kind of thing I mean. I know the Delphi IDE will run in a low amount of memory but it would be unbearable. I was just looking for a general idea considering the number of concurrent users, maybe increments like 1-5, 6-25, 26-50, 51-100. Though I have installations of almost 200 machines, I don't think there would ever be more than 50 concurrent users of my server. >> The basic equation is to take the amount of memory used per table, multiply it by the projected number of open tables per session, and finally multiply that by the concurrent number of sessions expected on the database server. The amount of memory per table is controlled by the TDBISAMEngine properties below: http://www.elevatesoft.com/dbisam4d5_tdbisamengine_maxtabledatabuffersize.htm http://www.elevatesoft.com/dbisam4d5_tdbisamengine_maxtableindexbuffersize.htm http://www.elevatesoft.com/dbisam4d5_tdbisamengine_maxtableblobbuffersize.htm That will give you a ballpark estimate on memory needs. << If I get the document looking good enough, I'll post it to the binaries group for others in the DBISAM community to use as well. >> Fantastic, thanks very much. << Tim, thanks so much for the great support here all the time. >> No problem. I wish I could be more "verbose" lately, but I'm trying to balance a lot right now and I have to be brief with my responses. -- Tim Young Elevate Software www.elevatesoft.com |
Fri, Apr 28 2006 5:40 PM | Permanent Link |
"B Miller" | > - Windows Server, because Prof. has a limitation of 10 concurrent TCP/IP
> connections. Where is this limitation? I thought this had more to do with the number of connections to the machine for share acces, not a DBISAM server. I have many more users than 10 accessing a XP Professional machine. Bill |
Fri, Apr 28 2006 5:58 PM | Permanent Link |
Jason Lee | From my research (using Google and spending hours reading), it
*appears* to me that there is no limit of 10 connections enforced for non-MS software (e.g. DBISAM database server). However, you *may* be violating the MS license agreement for WinXP Pro/Home or Win2000Pro. Jason B Miller wrote: >>- Windows Server, because Prof. has a limitation of 10 concurrent TCP/IP >>connections. > > > Where is this limitation? I thought this had more to do with the number of > connections to the machine for share acces, not a DBISAM server. I have > many more users than 10 accessing a XP Professional machine. > > Bill > > |
Mon, May 1 2006 2:30 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Bill,
<< Where is this limitation? I thought this had more to do with the number of connections to the machine for share acces, not a DBISAM server. I have many more users than 10 accessing a XP Professional machine. >> You are correct. The 10-user limitation has to do with other machines accessing shares on one machine, not TCP/IP connections via Winsock. I think the socket limit for Winsock is 64K (or possibly even higher now). -- Tim Young Elevate Software www.elevatesoft.com |
This web page was last updated on Tuesday, September 17, 2024 at 04:19 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |