Re: SQL or Access DB
- From: "W.G. Ryan MVP" <WilliamRyan@xxxxxxxxxxxxxxxx>
- Date: Sat, 13 Aug 2005 11:50:32 -0400
Earl (in no way being contentious or argumentative) - I don't know about the
statement that MSDE is a bitch to deploy. It took me about a hour to
correctly write an installer project that installed MSDE correctly and set
everything up initially correctly. The first time through I'd say it's
about a 4 on a scale of 1 to 10, after that it's cake and I can easily whip
up an installer to install MSDE, set up the accounts and create the tables I
need in just a few minutes. Heck it takes longer to run than it does for me
to create the package.
THe problem with Access is concurrency mainly, but there are others. THe
non sql standard syntax like IsNull, the lack of any real db language,
security, backup and the like all make access a terrible choice in so many
respects. It was a great alternative in the early 90's, but now it's
nothing but headaches.
If the installation is a problem, drop me a line and I'll gladly walk you
through creating an installer that will include MSDE and set it up for you -
it's really simple and well worth the investment.
"Earl" <brikshoe@xxxxxxxxxxxxxxxxx> wrote in message
news:%23RFWxN9nFHA.420@xxxxxxxxxxxxxxxxxxxxxxx
> If the database design is normalized, then it's less likely that size will
> become an issue. A non-normalized database will grow exponentially.
>
> JET ("Access") could be used, as I have in the past for a small system
> with less than 10 users, but in time, you will sooner or later hit a
> locking issue and/or possible corruption.
>
> As noted by Cor, MSDE is a real bitch to deploy (the cynic in me says that
> was by design), so the best "free" choice for a networked solution would
> be SQL Express 2005. I'm not sure about the licensing issues in your
> scenario.
>
> Otherwise, for a small business, if you don't already have a server
> installed and plan to build a small network, you might consider buying
> Small Business Server Premium. It comes with SQL Server 2000 Standard.
>
> "DaveG" <newsgroup@xxxxxxxxxxxxxxx> wrote in message
> news:O9mdnbY3z-GFdWHfRVnzvA@xxxxxxxxxxxxxx
>> Hi all
>>
>> I am planning on writing a stock and accounts program for the family
>> business, I understand this is likely to take close to 2 years to
>> accomplish. The stock is likely to run into over a thousand items and
>> the accounting side will be used for hopefully many years so the
>> entries are likely to be vast.
>>
>> The delema is what is best to use ase the DB engine, Access I have as
>> part of Office 2002 or should I really be looking at SQL server??
>>
>> What are the pros and cons between the two??
>>
>> The DB will only be accessed by one client at this time but never more
>> than 2.
>>
>> If the choice is SQL Server is there a version available just for
>> single clients. I remember using MSDE when I did my ASP.Net book can
>> this be used to create the initial DB???
>>
>> Thanks for taking the time to read this, any advice would be very
>> helpfull to me at this planning stage.
>>
>> --
>> DaveG - Learning VB.Net slowly.
>> Skøyen - Oslo - Norway
>
>
.
- Follow-Ups:
- Re: SQL or Access DB
- From: Earl
- Re: SQL or Access DB
- References:
- SQL or Access DB
- From: DaveG
- Re: SQL or Access DB
- From: Earl
- SQL or Access DB
- Prev by Date: Re: SQL or Access DB
- Next by Date: Re: Looking for HTML to Text component
- Previous by thread: Re: SQL or Access DB
- Next by thread: Re: SQL or Access DB
- Index(es):
Relevant Pages
|
Loading
