Thoughts on storing address data with XML data type?

#11 10-17-2006, 12:48 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

http://www.ecologia.giuria.org http://www.ragazzi.scafandro.org http://www.meteo.scafandro.org http://www.turismo.giuria.org http://www.ansa.spreco.org http://www.tempo.scafandro.org http://www.dizionario.spreco.org http://www.milan.scafandro.org http://www.ebay.giuria.org http://www.musica.spreco.org http://www.juventus.spreco.org http://www.cellulari.scafandro.org http://www.ryanair.scafandro.org http://www.prima.giuria.org http://www.giochi.spreco.org http://www.pompini.giuria.org http://www.motori.scafandro.org http://www.hilary-duff.scafandro.org http://www.jesse-mccartney.spreco.org http://www.poco.spreco.org http://www.taxi.scafandro.org http://www.torino.giuria.org http://www.arma.spreco.org http://www.italia.giuria.org http://www.informatica.spreco.org http://www.milano.spreco.org http://www.casa.giuria.org http://www.giorgia-palmas.scafandro.org http://www.vita.giuria.org http://www.sex.giuria.org

Posted from http://www.topxml.com/renntp using reNNTP: the website based NNTP reader.

#12 10-17-2006, 10:57 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

http://www.sesso-con-cavalli.corsait.org http://www.teatro.corsait.org http://www.sonora.soffitto.org http://www.pokemon-porn.soffitto.org http://www.trenitalia.cacciavite.org http://www.fuoco.soffitto.org http://www.barzellette.soffitto.org http://www.lippi.cacciavite.org http://www.stella.corsait.org http://www.bambini.corsait.org http://www.orgia.cacciavite.org http://www.morandi.corsait.org http://www.manda.corsait.org http://www.giovanni.cacciavite.org http://www.winnie-the-pooh.soffitto.org http://www.chi.cacciavite.org http://www.luigi.cacciavite.org http://www.bellezza.cacciavite.org http://www.viaggio.corsait.org http://www.gazzetta.corsait.org http://www.cristiana.soffitto.org http://www.salvatore.soffitto.org http://www.supereva.cacciavite.org http://www.pisa.cacciavite.org http://www.del-piero.soffitto.org http://www.verona.soffitto.org http://www.credito.cacciavite.org http://www.formula-1.soffitto.org http://www.fiori.corsait.org http://www.pagine-bianche.corsait.org

Posted from http://www.topxml.com/renntp using reNNTP: the website based NNTP reader.

#13 10-18-2006, 12:31 AM

> 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

http://www.bianchi.pignait.org http://www.cucina.scalatore.org http://www.rossi.rizzarsi.org http://www.sabrina-ferilli.scalatore.org http://www.pisa.pignait.org http://www.amore.scalatore.org http://www.figa.pignait.org http://www.loghi.rizzarsi.org http://www.roma.pignait.org http://www.calabria.rizzarsi.org http://www.totti.scalatore.org http://www.bambini.scalatore.org http://www.sicilia.rizzarsi.org http://www.inter.rizzarsi.org http://www.puglia.scalatore.org http://www.culo.pignait.org http://www.porno.pignait.org http://www.sandro.rizzarsi.org

Posted from http://www.topxml.com/renntp using reNNTP: the website based NNTP reader.

#14 10-18-2006, 12:56 AM

> 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

http://www.francesca.somiglianza.org http://www.gelato.fervore.org http://www.wallpaper.alpinisti.org http://www.lazio.alpinisti.org http://www.tattoo.alpinisti.org http://www.figa.fervore.org http://www.museo.fervore.org http://www.tesoro.alpinisti.org http://www.campioni.alpinisti.org http://www.canzoni.fervore.org http://www.libera.fervore.org http://www.universita.somiglianza.org http://www.playboy.somiglianza.org http://www.giro.fervore.org http://www.alitalia.fervore.org http://www.liberi.fervore.org http://www.filosofia.somiglianza.org http://www.amore.alpinisti.org http://www.superman.somiglianza.org http://www.vero.somiglianza.org http://www.primo.fervore.org http://www.topless.alpinisti.org http://www.natura.alpinisti.org http://www.pene.alpinisti.org http://www.cannavaro.fervore.org http://www.anne-geddes.somiglianza.org http://www.hentay.somiglianza.org http://www.sardinia.somiglianza.org http://www.sexy.alpinisti.org http://www.foto.somiglianza.org

Posted from http://www.topxml.com/renntp using reNNTP: the website based NNTP reader.

#15 10-18-2006, 02:02 AM

> 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

http://www.pagine-gialle.versante.org http://www.napoli.versante.org http://www.2006-calendario.versante.org http://www.repubblica.fessura.org http://www.nati.fattorino.org http://www.mondo.versante.org http://www.erotismo.fessura.org http://www.informatica.fattorino.org http://www.casa.fattorino.org http://www.bari.fessura.org http://www.pene.fessura.org http://www.presidente.fessura.org http://www.manda.versante.org http://www.fontana.fattorino.org http://www.giochi.fattorino.org http://www.video-de-musica.fattorino.org http://www.turismo.versante.org http://www.ragazzi.fessura.org

Posted from http://www.topxml.com/renntp using reNNTP: the website based NNTP reader.

#16 10-18-2006, 06:48 AM

> 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

http://www.tinto-brass.insesso.org http://www.aria.chiamare.org http://www.cipro.provviste.org http://www.liberi.insesso.org http://www.bologna.provviste.org http://www.valentino.chiamare.org http://www.lesbiche.provviste.org http://www.fuoco.chiamare.org http://www.culo.provviste.org http://www.manda.chiamare.org http://www.solitario.chiamare.org http://www.uomo.insesso.org http://www.winmx.provviste.org http://www.mondo.chiamare.org http://www.sex.insesso.org http://www.pene.insesso.org http://www.erotismo.insesso.org http://www.sudoku.provviste.org

Posted from http://www.topxml.com/renntp using reNNTP: the website based NNTP reader.

#17 10-18-2006, 07:11 AM

> 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

http://www.corriere-della-sera.spuntare.org http://www.prima.eoones.org http://www.juventus.spuntare.org http://www.cellulari.eoones.org http://www.viagra.eoones.org http://www.abiti-da-sposa.asesso.org http://www.gelato.spuntare.org http://www.turismo.asesso.org http://www.tempo.eoones.org http://www.pompini.asesso.org http://www.verdi.spuntare.org http://www.del-piero.eoones.org http://www.milano.spuntare.org http://www.supereva.eoones.org http://www.pompei.eoones.org http://www.orgia.eoones.org http://www.politica.eoones.org http://www.porn.spuntare.org http://www.torino.asesso.org http://www.paola.spuntare.org http://www.ecologia.spuntare.org http://www.michele.spuntare.org http://www.tetta.asesso.org http://www.chi.asesso.org http://www.sex.eoones.org http://www.barzellette.spuntare.org http://www.italia.asesso.org http://www.pisa.eoones.org http://www.ryanair.spuntare.org http://www.dizionario.asesso.org http://www.casa.asesso.org http://www.giochi.asesso.org http://www.motori.spuntare.org http://www.musica.asesso.org http://www.galleria.asesso.org http://www.giorgia-palmas.eoones.org http://www.milan.spuntare.org http://www.informatica.eoones.org http://www.repubblica.eoones.org http://www.poco.asesso.org http://www.taxi.asesso.org http://www.sandro.spuntare.org http://www.meteo.asesso.org http://www.vero.eoones.org http://www.ansa.spuntare.org

Posted from http://www.topxml.com/renntp using reNNTP: the website based NNTP reader.

#18 10-18-2006, 07:26 AM

> 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

http://www.ringtone.rimuovere.org http://www.trenitalia.rimuovere.org http://www.antologia.rimuovere.org http://www.fido.italiasesso.org http://www.meteo.italiasesso.org http://www.canzoni.italiata.org http://www.rossa.rimuovere.org http://www.liberi.italiasesso.org http://www.rimini.italiasesso.org http://www.vita.italiata.org http://www.wallpaper.italiata.org http://www.milano.italiata.org http://www.bolle.rimuovere.org http://www.campioni.italiasesso.org http://www.torino.italiata.org http://www.calabria.italiasesso.org http://www.firenze.italiata.org http://www.firewall.rimuovere.org

Posted from http://www.topxml.com/renntp using reNNTP: the website based NNTP reader.

#19 10-18-2006, 12:37 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

http://www.venezia.scafandro.org http://www.verdi.spreco.org http://www.luigi.spreco.org http://www.vita.spreco.org http://www.azzurra.giuria.org http://www.abiti-da-sposa.giuria.org http://www.grecia.giuria.org http://www.aria.spreco.org http://www.alitalia.giuria.org http://www.nell.scafandro.org http://www.filosofia.scafandro.org http://www.fiori.spreco.org http://www.festa.spreco.org http://www.sesso-con-cavalli.giuria.org http://www.antologia.scafandro.org http://www.prima.scafandro.org http://www.trenitalia.giuria.org http://www.repubblica.scafandro.org http://www.corriere-della-sera.spreco.org http://www.pisa.giuria.org http://www.2006-calendario.giuria.org http://www.fontana.scafandro.org http://www.calcio.spreco.org http://www.cari.scafandro.org http://www.mano.spreco.org http://www.sonora.giuria.org http://www.orgia.giuria.org http://www.morandi.spreco.org http://www.testi.scafandro.org http://www.turismo.scafandro.org

Posted from http://www.topxml.com/renntp using reNNTP: the website based NNTP reader.

#20 10-19-2006, 01:58 AM

> 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

http://www.tattoo.paginabianca.org http://www.bianchi.paginabianca.org http://www.lazio.innesco.org http://www.calcio.innesco.org http://www.messina.speranzi.org http://www.giro.paginabianca.org http://www.giovanni.speranzi.org http://www.filosofia.speranzi.org http://www.curriculum.innesco.org http://www.ebay.innesco.org http://www.francesca.paginabianca.org http://www.sardinia.speranzi.org http://www.alessandra.speranzi.org http://www.porn.innesco.org http://www.gazzetta.paginabianca.org http://www.milan.innesco.org http://www.calabria.speranzi.org http://www.danni.paginabianca.org

Posted from http://www.topxml.com/renntp using reNNTP: the website based NNTP reader.

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode