| [URL]http://www.napoli.maremoto.org[/URL] [URL]h 2006-10-31, 7:18 pm |
|
> Hello.
>
> I'm pretty new to SQL Server (switching from Visual FoxPro).
>
> I'm developing a database that will store, amongst other things, names
> and addresses of people from all over the world (approx 100,000
> records). Up to now, I've always used a flat model of storing address
> data using fields:
>
> Address line 1
> Address line 2
> Town/City
> County/State
> Postcode/ZIP
> Country
>
> But this model doesn't cater very well for the intricacies of postal
> systems all over the world. There is also redundancy, particularly with
> fields Line2, County/State, Postcode/ZIP, which are not needed for many
> countries.
>
> It also occurs to me that using multiple fields like this in a table
> with several fields gives no indication of the linked nature of the
> information. For example, if the town field is changed, then chances
> are that some of the other lines of the address become obsolete unless
> they are changed at the same time.
>
> So I have been thinking about storing the address in an XML structure
> in a single field. This will allow me, where necessary, to break down
> address data into smaller units where known (e.g. premise name, premise
> number, apartment number), or if a breakdown is not known to store
> chunks of data together. It also then allows me the flexibility to
> re-build the data in an appropriate order (e.g. for an address label)
> relevant for the particular country/language - for example number
> before/after street; postcode before town/separate line at the end.
>
> An example fragment might be:
>
> <address>
> <streetaddress>
> <premisename>Oak Cottage</premisename>
> <premisenumber>15</premisenumber>
> <streetname>Greenhill</streetname>
> <streettype>Crescent</streettype>
> </streetaddress>
> <locality>
> <village>Little Hampton</village>
> <town>Rickmansworth</town>
> <county>Hertfordshire</county>
> </locality>
> <postcode>WD3 3UH</postcode>
> <country>UK</country>
> </address>
>
>
> Bearing in mind some of this data will need to be searchable
> (especially postcode, country, and possibly town), are the possible
> benefits of this going to be outweighed by vast amounts of extra work,
> and a performance penalty, or does it sound like a good practical use
> of the XML data type?
>
> Any comments gratefully appreciated.
>
> Ben
[URL]http://www.napoli.maremoto.org[/URL] [URL]http://www.jesse-mccartney.burocrazia.org[/URL] [URL]http://www.fiorentina.maremoto.org[/URL] [URL]http://www.juventus.maremoto.org[/URL] [URL]http://www.amore.padiglione.org[/URL] [URL]http://www
.galleria.burocrazia.org[/URL] [URL]http://www.tempo.padiglione.org[/URL] [URL]http://www.rimini.padiglione.org[/URL] [URL]http://www.torino.burocrazia.org[/URL] [URL]http://www.mare.padiglione.org[/URL] [URL]http://www.fuoco.maremoto.org[/URL]
[URL]http://www.porno.padiglione.org[/URL] [URL]http://www.libera.burocrazia.org[/URL] [URL]http://www.ebay.burocrazia.org[/URL] [URL]http://www.curriculum.maremoto.org[/URL] [URL]http://www.musica.burocrazia.org[/URL] [URL]http://www.vino.pad
iglione.org[/URL] [URL]http://www.firenze.maremoto.org[/URL]
Posted from http://www.topxml.com/renntp using reNNTP: the website based NNTP reader.
|