Re: Access vs SQL
- From: "lgbjr" <lgbjr@xxxxxxxxxxxxx>
- Date: Wed, 13 Apr 2005 22:06:05 +0800
Hi All,
LOL! I've quite enjoyed reading all of the posts in this thread. To get back
to the original topic for a second, I just wanted to let everyone know what
I decided to do.
I downloaded and installed MSDE 2000 (as well as DBAMgr2K). I did an upsize
from Access, tweaked my app a bit, and viola, everything works.
while downloading and installing MSDE 2000, my only thoughts were that
Access was simple (I'm always on a quest to keep things simple for my
users). MSDE 2000 adds a bit of complexity, but I have to say, compared to
the performance gains, it's well worth it. Two of the tables have OLEObject
(picture) fields (6 in one table, 8 in another). while running my app with
the "Jet or Access or MS Access" DB (wink), there was a noticeable delay in
retrieving and displaying records from the DB that had pictures. With MSDE,
pictures, or no pictures, retrieving records is fast!
thanks for all of the advice, and the entertainment!!
Lee
"lgbjr" <lgbjr@xxxxxxxxxxxxx> wrote in message
news:ORcBmJXPFHA.2680@xxxxxxxxxxxxxxxxxxxxxxx
> Hello All,
>
> Thank You for your responses! All of you have given me quite a bit to
> think about!
>
> Richard, I understand completely. A bit of background: Even though I am
> developing a software package, I would not, by any stretch of the
> imagination, consider myself a software developer. I'm an Engineering
> Consultant for the Mobile Communications Industry. For the past 10 years,
> I've been writing PERL apps (when necessary) to automate repetitive tasks
> and make my life easier. These apps were for my use only. Over the years,
> I have had several clients ask me to provide these small apps to them. So,
> I moved from writing plain code, to writing an app with a user-friendly
> interface. Now, my clients want more. And they're willing to pay for it
> (above and beyond what they pay for my engineering services). Fortunately,
> I knew enough to write a scope of work (basically for myself), just as I
> would do for a typical engineering project. So, I do understand 'creeping
> scope'.
>
> Regarding the ability to 'Plug and Play' a variety of DB engines, I have
> considered this as well. At the beginning of this project, I was using C1
> Express components (no data adapters, no datasets, just Express Tables and
> an Express connection (OLEDB)). While this was extremely easy to
> implement, I realized that there was no upgrade path (upgrade = rewrite).
> Now, still using C1 components, I know (think) I can upsize to MSDE or SQL
> Server with only minor code changes.
>
> Gerald, I agree. Rather than trying to decide which DB engine is better,
> it's safe to say that all are good, if used in the environment they were
> designed for. Right now, wihtout thinking about growth, I could deploy
> with Access (1-2 users performing updates, additional 3-4 users viewing
> data, approximately 1-1.5GB size). But, this, based on what I have read,
> and your comments, is near the upper limit of what Access was designed
> for.
>
> JL, though it may not seem so, I am in a similar situation regarding IT
> support. Even though all of the mobile operators have extensive IT
> departments, the engineering and IT departments are always fighting. So, I
> need my app to be self-maintainable.
>
> After posting this, I'm going to install SQL2KDesktop (MSDE) and try to
> get a feel for what it will take to do a migration (I already have SQL
> Server running on another machine). I like Richard's idea of allowing the
> client to decide which DB engine to use. Hopefully my coding and
> forward-thinking was robust enough to allow this with only some minor
> tweaks. However, if I get lost in a sea of errors, I think my backup will
> be to use MSDE.
>
> Again, thanks for your insights!!
>
> Regards,
> Lee
>
>
>
> "lgbjr" <lgbjr@xxxxxxxxxxxxx> wrote in message
> news:exGmoIPPFHA.2144@xxxxxxxxxxxxxxxxxxxxxxx
>> Hello All,
>>
>> I've been developing a VB.NET app that requires the use of a DB. Up to
>> now, I've been using Access. It's a bit slow, but everything works. I'm
>> at a point now where I need to decide if I should stay with Access or
>> move the DB to SQL. I'm trying to come up with a list of Pros/Cons for
>> such a move. My list is a bit lopsided, as I have very little experience
>> with SQL and quite a bit with Access.
>>
>> PROS for moving to SQL:
>> Increased Performance?
>> Increased Reliability?
>> Lifecycle of Access?
>> Future Access Version compatibility issues?
>>
>> CONS for moving to SQL:
>> My limited knowledge of SQL
>> Clients not required to have an SQL server
>>
>> I've added a few items to the PROS list, but with ?s, as I don't really
>> know.
>>
>> If there are a few Access advocates and SQL advocates out there that
>> could give me some viewpoints, I'd be more comfortable making a decision
>> based on the facts, rather than my limited knowledge.
>>
>> TIA
>> Lee
>>
>>
>>
>
>
.
- Follow-Ups:
- Re: Access vs SQL
- From: Scott M.
- Re: Access vs SQL
- References:
- Access vs SQL
- From: lgbjr
- Re: Access vs SQL
- From: lgbjr
- Access vs SQL
- Prev by Date: Re: Regex. Split or Split
- Next by Date: Re: MsgBox Problem
- Previous by thread: Re: Access vs SQL
- Next by thread: Re: Access vs SQL
- Index(es):
Relevant Pages
|
