Re: DB or no DB?
- From: AlexDP <AlexDP@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 15 Feb 2006 23:03:27 -0800
Alright, thanks for the help.
"ZMan" wrote:
Probably better to ask the real experts in a SQL/Access forum/newsgroup for.
that one.
--
Zman
http://www.thezbuffer.com - News and information for Managed DirectX
"AlexDP" <AlexDP@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:5723BF54-379D-439D-A3FE-4BB2E3E47831@xxxxxxxxxxxxxxxx
Thanks for the replies, both of you.
I think the question about whether to use a DBMS has been answered. The
second part of the question remains though, and that is which DBMS to use.
Access or SQL Server Express? Basically the question is what disadvantages
does Access have in comparison to SQL Server Express, the advantages being
Access is easier to integrate with the program and is lighter in
comparison
with SQL Server Express. An important question regarding the disadvantages
of
Access is what is the limit on the number of records that can be entered
in
Access (and for that matter SQL Server Express)?
Thanks for your help so far, and again thank you for your future help.
"ZMan" wrote:
SQL Express (and before it SQL Server 2000 Personal Edition - see
http://www.microsoft.com/sql/techinfo/planning/ChoosEd.doc) are totally
designed to run on the client. That's their target audience. See
http://www.microsoft.com/sql/editions/express/default.mspx '...Easily
Embed
a Local Database for Your Application...'
The 'server' in their title is indeed a little confusing but that's just
the
way it is. They even have a Sql Server Mobile
http://www.microsoft.com/sql/editions/sqlmobile/default.mspx for phones
and
PDAs so obviously the 'server' in the name does not mean you can only run
on
a server.
As for using it, I disagree. If you have an application that needs to
store
and query structured data then a DBMS is a perfectly valid way of doing
it.
Depending on your requirements for storage and query it may be overkill
but
that's the developers decision to make. If you are a SQL expert then
maybe
using something you already know is a big productivity advantage rather
than
changing the way you think - and remember there are a *lot* of .Net
developers that know SQL very well. There is nothing that says databases
are
only for B2B applications. That is of course, just my opinion.
--
Zman
http://www.thezbuffer.com - News and information for Managed DirectX
"vidalsasoon" <kjobson@xxxxxxxxx> wrote in message
news:1139845093.651946.318680@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Well it's called SQL "Server" Express... I never worked with the
express version but I do know that the full version is indeed a
server...
Anyway, It's a bad idea unless maybe you're making a B2B application.
- References:
- Re: DB or no DB?
- From: vidalsasoon
- Re: DB or no DB?
- From: vidalsasoon
- Re: DB or no DB?
- From: ZMan
- Re: DB or no DB?
- From: vidalsasoon
- Re: DB or no DB?
- From: ZMan
- Re: DB or no DB?
- From: ZMan
- Re: DB or no DB?
- Prev by Date: Impossible to create a window size other than 640 x 480 using Sample Framework for DirectX 9.0
- Next by Date: Re: Impossible to create a window size other than 640 x 480 using Sample Framework for DirectX 9.0
- Previous by thread: Re: DB or no DB?
- Next by thread: Re: SurfaceLoader.FromSurface in 2.0
- Index(es):
Relevant Pages
|
