Re: Why choose SQL Express over Access?
- From: "ljh" <Some@xxxxxxxxxx>
- Date: Thu, 1 Jun 2006 07:14:11 -0400
I thought of one myself.....
I am thinking of coding a data store that many store locations will use to
get national sales averages. Each location sends in its data in in XML
format and gets back the most current national averages. Keeping the XML as
presented to the service can help by finding errors in posted XML data.
It may even be useful in searching for common errors in the XML data
presented.
Thanks for your insight.
ljh
"Frans Bouma [C# MVP]" <perseus.usenetNOSPAM@xxxxxxxxx> wrote in message
news:xn0emyez94e2sm000@xxxxxxxxxxxxxxxxxxxxx
ljh wrote:
Just curious......can you tell me a situation where using XML as a
datatype would come into play in a database application?
Why would you store XML in its native format instead of breaking it
down into its component fields for storage and seaarch?
In general, people should avoid Xml typed fields to avoid
'table-in-table' syndrome, which effectively kills your relational
model. However there are situations where it can be helpful. One is the
situation where the user of your software is able to add custom fields
to a table. You can store these in XML and query them as well (although
it's not ideal, I admit)
Another can be to store xml data in an xml column, although you can
also use a Text column for that if you want to of course.
FB
"Cowboy (Gregory A. Beamer)" <NoSpamMgbworld@xxxxxxxxxxxxxxxxxx>
wrote in message news:O6q4onKhGHA.4144@xxxxxxxxxxxxxxxxxxxxxxx
Let's see:application >> to work) over the simplicity of an Access database
Ability to do asynch apps (Service Broker)
Server model instead of file system model
Complete support for stored procedures
Full SQL Server security model
Ability to run queries as another user, completely isolating the
database from the user
Better support for types in SQL Server than Access (in .NET)
Ability to schedule backups within the engine
Support for more types than Access
Ability to use XML as a datatype with querying capabilities
Is that enough, or should I go on?
--
Gregory A. Beamer
*************************************************
Think Outside the Box!
*************************************************
"ljh" <Some@xxxxxxxxxx> wrote in message
news:kP1fg.66184$MM6.44395@xxxxxxxxxxxxxxxxxxxxxxxxx
Why would you choose SQL Express (which requires an installed
which has no >> dependencies?
--
------------------------------------------------------------------------
Lead developer of LLBLGen Pro, the productive O/R mapper for .NET
LLBLGen Pro website: http://www.llblgen.com
My .NET blog: http://weblogs.asp.net/fbouma
Microsoft MVP (C#)
------------------------------------------------------------------------
.
- Prev by Date: Re: Why choose SQL Express over Access?
- Next by Date: Re: Why choose SQL Express over Access?
- Previous by thread: Re: Why choose SQL Express over Access?
- Next by thread: Re: Why choose SQL Express over Access?
- Index(es):
Relevant Pages
|