Re: Converting from JET database to a true C/S Database
From: JD (jdoramedk_at_hotmail.com)
Date: 02/10/05
- Next message: Joel Whitehouse: "Re: Preferred method"
- Previous message: Ralph: "Re: Migrate Microsoft Application (Visual basic) Apps to Unix O.S"
- In reply to: MikeB: "Re: Converting from JET database to a true C/S Database"
- Next in thread: Jeff Beem: "Re: Converting from JET database to a true C/S Database"
- Reply: Jeff Beem: "Re: Converting from JET database to a true C/S Database"
- Reply: Jeff Johnson [MVP: VB]: "Re: Converting from JET database to a true C/S Database"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 10 Feb 2005 07:28:00 -0800
Depending upon how large your database will be, and how many users are going
to be hitting it. You may want
to look at and review MSDE. This is the "FREE" version of MS SQL Server
and currrently will handle a 2GIG DB.
Depending upon your architecture you may be able to just point your application
at the SQL Server after upsizing
the Access DB to SQL Server. Check out this link for more information http://www.microsoft.com/sql/msde/default.asp.
Hello MikeB" m.byerleyATVerizonDottieNettie,
> "Ralph" <msnews.20.nt_consulting32@spamgourmet.com> wrote in message
> news:u2wQl03DFHA.1260@TK2MSFTNGP12.phx.gbl...
>
>> "B&B Musmon" <barrym@tdstelme.net> wrote in message
>> news:qhsm011fvp053sqenc2bi2smbdke2s6838@4ax.com...
>>
>>> I have an application for a user that I started about 8 years ago.
>>> Since then we have added functionality and the database has really
>>> grown. At the time even though it had serious limitations I went
>>> with JET, mostly because I didn't know what else to recommend and a
>>> real database is quite expensive. I have always told the client
>>> "what we are using will someday be inadequate" and in fact we have
>>> had to do some real awkward work arounds to keep it running. Well
>>> now the client is asking and thinking it is time. I am going to be
>>> on a steep learning curve on every aspect of this task. I don't
>>> have a clue what is the best database to choose, how to accomplish
>>> conversion, what processes to leave on the client side and what to
>>> move to the server or even how the procedures are written. For the
>>> moment I need to concentrate on the scope of the project so I can at
>>> least present a somewhat intelligent overview on what it will take
>>> and the approximate cost. I am hoping to find books, papers, web
>>> sites or any sources of information on the subject. Any suggestions
>>> where to look.
>>>
>>> Also if anyone has done this and can recommend an economical
>>> Database, that would be nice. I don't want to scare them off with a
>>> $10k starting point for just the Database. Some one suggested
>>> PostgreSQL 8.0. Which does have some appeal, it may be a little
>>> trickier but I can bill the client reasonably and make a little
>>> money.
>>>
>>> Thanks
>>> Barry
>> May I suggest that you are really chewing on the wrong end in your
>> search for a solution. The key here is "C/S". The actual data storage
>> is secondary or even tertiary. There are many good examples of the
>> 'good' that client/server designs can deliver, but why are YOU in
>> need of a distributed system?
>>
>> The real power of most RDBMS is the fact they bring a 'database
>> server' to into the solution domain. MSAccess is a file-based
>> database and thus somewhat limited in its 'out-of-the-box'
>> capabilities in a client/server environment. However, with the
>> judicious creation of 'services' an MSAccess database/s can be quite
>> adequate for amazingly large data stores and a high number of users.
>> If properly designed.
>>
>> Without an adequate upgrade (or redesign) of your network and
>> platform, it is highly unlikely a database 'upgrade' is going to
>> provide more than a brief, temporary solution (and yet another round
>> of 'work-arounds').
>>
>> As it sounds like you have to add, at a minimum, an additional server
>> to your domain, the $10k sounds like a reasonable opening bid. To
>> badly paraphrase Bruce McKinney - "It doesn't matter how cheap it is,
>> if it doesn't work." <g>
>>
>> If you are currently a predominately MS environment, then I would
>> suggest SQLServer and XP 2003 server as the best upgrade. SQLServer
>> offers the
>>
> for up to 50 users, look at the Small Business Server version that has
> Sql Server prepackeged to leverage your cost basis.
>
>> biggest bang for the buck out there.
>>
>> -ralph
>>
- Next message: Joel Whitehouse: "Re: Preferred method"
- Previous message: Ralph: "Re: Migrate Microsoft Application (Visual basic) Apps to Unix O.S"
- In reply to: MikeB: "Re: Converting from JET database to a true C/S Database"
- Next in thread: Jeff Beem: "Re: Converting from JET database to a true C/S Database"
- Reply: Jeff Beem: "Re: Converting from JET database to a true C/S Database"
- Reply: Jeff Johnson [MVP: VB]: "Re: Converting from JET database to a true C/S Database"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|