XPost: comp.databases, comp.databases.sybase, comp.databases.ms-sqlserver   
   From: mpeppler@peppler.org   
      
   On Mon, 03 Nov 2003 07:08:07 -0800, Alex_Bxl wrote:   
      
   > I'm wondering how to design that part, should I store all information   
   > on the web host only ? miror that DB every evening on some local DB   
   > server to be able to use the data without eating up lots of bandwith ?   
   > separate the database in 2 parts ? how to sync and assure integrity   
   > then ? having a local DB will also mean the company will have to pay a   
   > licence for the DBMS ...   
      
   I'd use Sybase, and I'd use replication server to move data from the   
   production server (in co-location facility) to the reporting server (in   
   the office).   
      
   But you can do similar things with Oracle, MS-SQL, etc., although I'd   
   personally stay away from MS-SQL due to its being Microsoft-centric (i.e.   
   can't scale beyond Intel/Windows type machines)   
      
   Michael   
   --   
   Michael Peppler                              Data Migrations, Inc.   
   mpeppler@peppler.org                 http://www.mbay.net/~mpeppler   
   Sybase T-SQL/OpenClient/OpenServer/C/Perl developer available for short or   
   long term contract positions - http://www.mbay.net/~mpeppler/resume.html   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)