Should not cause any specific issues; partition the SAN so the database gets disk spindles to itself; probably best to configure them in individual mirrors or a striped/ mirrored. If you're using Linux make sure you get SAN hardware that plays nicely with it. My various comments about the server architecture still stand if you use a SAN. Unless you have massive transaction volumes, a well- tuned database will serve a pretty large user base off quite mundane intel hardware.
-----Original Message----- From: Mark Thomas [mailto:[EMAIL PROTECTED] Sent: Wednesday, 27 August 2003 4:51 a.m. To: SAPDB General Subject: RE: High-end hardware and SAPDB That's what I figured about the blades. We might be going with a SAN anyway for some of our other storage requirements, and I'm still wondering what issues I might encounter if I try to store a SAPDB database on one. Does anyone know whether the 64-bit AMD procs will be supported anytime in the forseeable future? Most of our servers are SuSE Linux. Thanks. -- Mark Thomas United Drugs -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Nigel Campbell (DSL AK) Sent: Monday, August 25, 2003 6:38 PM To: '[EMAIL PROTECTED]'; 'Mark Thomas' Subject: RE: High-end hardware and SAPDB You really need a SMP machine with a shared memory space. SAP-DB isn't designed to run in a cluster (so blade servers aren't really a good choice to run it on), although it can replicate to a standby server (there's a HOWTO for this on the net). Bear in mind that a fairly ordinary 2 or 4-way Xeon box has quite a lot of computing power. You can fit a machine like that with 4GB or more of RAM and 20 or 30 disk spindles without needing exotic (read: expensive) hardware like fibre-channel SANs. With reasonable tuning this kit will support a couple of thousand punters on most TP applications. A useful strategy for keeping workload off databases is to move reporting onto a subsidiary machine and replicate some or all of the database. Your TP system should really only be doing a handful of directly operational status reports that really need up-to-the minute data. The rest can be done off a data mart that is updated nightly from your TP box. This should further reduce the workload on your TP system. If you need more than 4GB of shared space in the database you should go to a 64-bit architecture like a sun (and arguably can afford it if you've got that many users). Also, I presume an AMD-64 port of SAP-DB will make its appearance at some point; This will let you use >4GB sized instances on hardware in roughly the same price as a Xeon. Nigel. -----Original Message----- From: Mark Thomas [mailto:[EMAIL PROTECTED] Sent: Tuesday, 26 August 2003 10:11 a.m. To: SAPDB General Subject: High-end hardware and SAPDB Hello, all. We are shopping for some hardware to upgrade the server on which our SAPDB installation resides. Has anyone had any experience running SAPDB on a blade server? What about on a SAN? I would be most interested in hearing about your experiences. I am also interested in any thoughts from the SAPDB developers on the subject. Thanks. -- Mark "T.C." Thomas United Drugs _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
