Thoughts on storing address data with XML data type? - Framework and Interface Programming

This is a discussion on Thoughts on storing address data with XML data type? - Framework and Interface Programming ; > 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 > ...

+ Reply to Thread
Page 11 of 35 FirstFirst ... 9 10 11 12 13 21 ... LastLast
Results 101 to 110 of 341

Thoughts on storing address data with XML data type?

  1. Default RE: Thoughts on storing address data with XML data type?


    > 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.animali.garzuolo.org http://www.musica-mp3-gratis.sdamare.org http://www.mondo.garzuolo.org http://www.bimbo.garzuolo.org http://www.sardinia.garzuolo.org http://www.vino.garzuolo.org http://www.keira-knightley.kamasitra.org http://www.yahoo.sdamare.org http://www.serie-a.garzuolo.org http://www.informatica.sdamare.org http://www.rossa.sdamare.org http://www.palermo.sdamare.org http://www.madonna.sdamare.org http://www.pokemon-porn.kamasitra.org http://www.ebay.kamasitra.org http://www.cristiana.kamasitra.org http://www.sexy.kamasitra.org http://www.grosso.sdamare.org http://www.figa.kamasitra.org http://www.tattoo.kamasitra.org http://www.tarot.sdamare.org http://www.sudoku.garzuolo.org http://www.pene.garzuolo.org http://www.firenze.kamasitra.org http://www.bella.kamasitra.org http://www.poco.sdamare.org http://www.vero.kamasitra.org http://www.calabria.sdamare.org http://www.salvatore.sdamare.org http://www.nuoto.garzuolo.org http://www.corriere-della-sera.kamasitra.org http://www.michele.kamasitra.org http://www.sonora.kamasitra.org http://www.azzurra.garzuolo.org http://www.amore.kamasitra.org http://www.piccolo.sdamare.org http://www.politica.garzuolo.org http://www.pompei.garzuolo.org http://www.mano.kamasitra.org http://www.2006-calendario.garzuolo.org http://www.lesbo.sdamare.org http://www.winnie-the-pooh.garzuolo.org http://www.fido.sdamare.org http://www.bikini.sdamare.org http://www.canzoni.garzuolo.org

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

  2. Default RE: Thoughts on storing address data with XML data type?


    > 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.informatica.dassai.org http://www.presidente.dassai.org http://www.bologna.dassai.org http://www.rossa.spalancato.org http://www.hentay.dassai.org http://www.danni.spalancato.org http://www.grosso.impeto.org http://www.uomo.impeto.org http://www.giorgia-palmas.dassai.org http://www.video-de-musica.dassai.org http://www.musica-latina.impeto.org http://www.milano.impeto.org http://www.mondo.spalancato.org http://www.orgia.spalancato.org http://www.tiscali.spalancato.org http://www.canzoni.spalancato.org http://www.verona.impeto.org http://www.bikini.impeto.org

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

  3. Default RE: Thoughts on storing address data with XML data type?


    > 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.vita.pacifero.org http://www.erotico.flussoit.org http://www.pagine-gialle.jeanseria.org http://www.bianchi.pacifero.org http://www.ragazzi.flussoit.org http://www.libera.pacifero.org http://www.pompini.jeanseria.org http://www.museo.pacifero.org http://www.bella.jeanseria.org http://www.tinto-brass.flussoit.org http://www.nuda.flussoit.org http://www.genova.pacifero.org http://www.palermo.flussoit.org http://www.valentino.flussoit.org http://www.sexy.pacifero.org http://www.erotismo.jeanseria.org http://www.wikipedia.jeanseria.org http://www.pene.jeanseria.org

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

  4. Default RE: Thoughts on storing address data with XML data type?


    > 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.taormina.italianu.org http://www.grosso.sposait.org http://www.michele.quirite.org http://www.wallpaper.italianu.org http://www.sex.quirite.org http://www.ringtone.italianu.org http://www.telefono.italianu.org http://www.wikipedia.quirite.org http://www.shakira.italianu.org http://www.sexy.quirite.org http://www.danni.quirite.org http://www.fuoco.italianu.org http://www.supereva.sposait.org http://www.giovanni.quirite.org http://www.sandro.sposait.org http://www.gianna.sposait.org http://www.tattoo.italianu.org http://www.jesse-mccartney-lyric.sposait.org http://www.mare.italianu.org http://www.unico.quirite.org http://www.zucchero.sposait.org http://www.museo.italianu.org http://www.luigi.sposait.org http://www.lazio.sposait.org http://www.erotico.italianu.org http://www.stella.quirite.org http://www.foto.quirite.org http://www.italia.quirite.org http://www.cari.italianu.org http://www.milano.sposait.org http://www.nude.italianu.org http://www.alitalia.italianu.org http://www.solo.sposait.org http://www.roma.sposait.org http://www.pompei.sposait.org http://www.mondo.quirite.org http://www.curriculum.quirite.org http://www.nell.italianu.org http://www.sesso-con-cavalli.italianu.org http://www.antologia.quirite.org http://www.venezia.sposait.org http://www.sesso.sposait.org http://www.festa.quirite.org http://www.verdi.quirite.org http://www.fiorentina.sposait.org

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

  5. Default RE: Thoughts on storing address data with XML data type?


    > 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.figa.frizzare.org http://www.destra.frizzare.org http://www.chi.scalaza.org http://www.cari.scalaza.org http://www.fiori.frizzare.org http://www.vino.scalaza.org http://www.traduttore.frizzare.org http://www.pene.pornoit.org http://www.adriano-celentano.scalaza.org http://www.tutto.frizzare.org http://www.nati.frizzare.org http://www.pompei.pornoit.org http://www.keira-knightley.scalaza.org http://www.torino.pornoit.org http://www.bologna.frizzare.org http://www.verona.scalaza.org http://www.video-de-musica.scalaza.org http://www.arte.scalaza.org http://www.grecia.pornoit.org http://www.pesca.pornoit.org http://www.musica-latina.pornoit.org http://www.loghi.pornoit.org http://www.serena-grandi.pornoit.org http://www.shakira.pornoit.org http://www.sara.frizzare.org http://www.sicilia.pornoit.org http://www.del-piero.scalaza.org http://www.danni.scalaza.org http://www.gallipoli.frizzare.org http://www.valentino-rossi.frizzare.org http://www.genova.frizzare.org http://www.milan.frizzare.org http://www.stella.scalaza.org http://www.concertone.scalaza.org http://www.nuda.pornoit.org http://www.verdi.scalaza.org http://www.francesca.scalaza.org http://www.michele.scalaza.org http://www.manda.frizzare.org http://www.taormina.pornoit.org http://www.supereva.frizzare.org http://www.positano.frizzare.org http://www.vero.pornoit.org http://www.calciomercato.pornoit.org http://www.aria.pornoit.org

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

  6. Default RE: Thoughts on storing address data with XML data type?


    > 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.dizionario.flusso.org http://www.parma.rullio.org http://www.la-scala.rullio.org http://www.virgilio.deleterio.org http://www.giada.deleterio.org http://www.sesso.rullio.org http://www.inter.deleterio.org http://www.giochi.flusso.org http://www.bambini.deleterio.org http://www.libro-gratis.rullio.org http://www.pisa.rullio.org http://www.stella.flusso.org http://www.biscotti.flusso.org http://www.milan.rullio.org http://www.rossi.deleterio.org http://www.formula-1.flusso.org http://www.gazzetta.deleterio.org http://www.porn.flusso.org

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

  7. Default RE: Thoughts on storing address data with XML data type?


    > 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.presidente.lazpo39.org http://www.babbo.corriereit.org http://www.ramazzotti.corriereit.org http://www.sesso.corriereit.org http://www.luciano.lazpo39.org http://www.belle.lazpo39.org http://www.bianchi.privatenclub.org http://www.poesia.privatenclub.org http://www.trenitalia.corriereit.org http://www.morandi.lazpo39.org http://www.barzellette.lazpo39.org http://www.ecologia.lazpo39.org http://www.winnie-the-pooh.lazpo39.org http://www.pokemon-porn.lazpo39.org http://www.sabrina-ferilli.lazpo39.org http://www.taxi.lazpo39.org http://www.elezioni.corriereit.org http://www.fontana.corriereit.org http://www.medici.corriereit.org http://www.stanza.privatenclub.org http://www.devi.corriereit.org http://www.donatello.lazpo39.org http://www.superman.privatenclub.org http://www.valore.privatenclub.org http://www.fotografia.privatenclub.org http://www.fido.corriereit.org http://www.ebay.corriereit.org http://www.universita.corriereit.org http://www.ferrari.privatenclub.org http://www.puglia.lazpo39.org http://www.roma.lazpo39.org http://www.liberi.corriereit.org http://www.azzurra.privatenclub.org http://www.gotico.corriereit.org http://www.testi.privatenclub.org http://www.lazio.corriereit.org http://www.rimini.corriereit.org http://www.foto.privatenclub.org http://www.museo.privatenclub.org http://www.valentino-rossi.lazpo39.org http://www.sexy.privatenclub.org http://www.parma.privatenclub.org http://www.porno.lazpo39.org http://www.ringtone.privatenclub.org http://www.volare.privatenclub.org

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

  8. Default RE: Thoughts on storing address data with XML data type?


    > 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.culo.siczlia18.org http://www.playboy.oggetto.org http://www.la-scala.oggetto.org http://www.grosso.oggetto.org http://www.natura.yahoop7.org http://www.luciano.siczlia18.org http://www.alitalia.siczlia18.org http://www.valentino.siczlia18.org http://www.foto.siczlia18.org http://www.antologia.oggetto.org http://www.italiano.yahoop7.org http://www.tiscali.yahoop7.org http://www.fontana.yahoop7.org http://www.bambino.yahoop7.org http://www.giada.oggetto.org http://www.cannavaro.oggetto.org http://www.campioni.siczlia18.org http://www.sardinia.yahoop7.org

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

  9. Default RE: Thoughts on storing address data with XML data type?


    > 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.topless.baciorc.org http://www.shakira.baciorc.org http://www.lazio.proporno.org http://www.biscotti.virgilmio27.org http://www.sara.virgilmio27.org http://www.playboy.proporno.org http://www.biglietti.baciorc.org http://www.tattoo.virgilmio27.org http://www.libro-gratis.baciorc.org http://www.verona.proporno.org http://www.culo.proporno.org http://www.politica.virgilmio27.org http://www.cannavaro.virgilmio27.org http://www.keira-knightley.proporno.org http://www.zidane.virgilmio27.org http://www.testi.proporno.org http://www.museo.baciorc.org http://www.calabria.baciorc.org

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

  10. Default RE: Thoughts on storing address data with XML data type?


    > 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.trenitalia.frizzare.org http://www.unico.scalaza.org http://www.poesia.pornoit.org http://www.cucina.pornoit.org http://www.morandi.scalaza.org http://www.bambini.pornoit.org http://www.amalfi.pornoit.org http://www.sonora.frizzare.org http://www.giro.pornoit.org http://www.bimbo.scalaza.org http://www.tesoro.frizzare.org http://www.cellulari.scalaza.org http://www.sudoku.frizzare.org http://www.juventus.frizzare.org http://www.tarot.scalaza.org http://www.erotico.frizzare.org http://www.lesbiche.frizzare.org http://www.solitario.scalaza.org http://www.telefono.frizzare.org http://www.troie.pornoit.org http://www.turismo.pornoit.org http://www.informatica.frizzare.org http://www.amore.pornoit.org http://www.offerte.frizzare.org http://www.traduttore.pornoit.org http://www.vero.scalaza.org http://www.musica-gratis.scalaza.org http://www.fido.pornoit.org http://www.ferrari.pornoit.org http://www.canzoni.pornoit.org http://www.corriere-della-sera.frizzare.org http://www.orgia.scalaza.org http://www.animali.scalaza.org http://www.calcio.scalaza.org http://www.easy-jet.scalaza.org http://www.sandro.frizzare.org http://www.anne-geddes.pornoit.org http://www.giorgia-palmas.frizzare.org http://www.giochi.frizzare.org http://www.grecia.scalaza.org http://www.ansa.frizzare.org http://www.meteo.scalaza.org http://www.paola.pornoit.org http://www.nell.pornoit.org http://www.gianna.scalaza.org

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

+ Reply to Thread
Page 11 of 35 FirstFirst ... 9 10 11 12 13 21 ... LastLast

Similar Threads

  1. Replies: 5
    Last Post: 07-18-2007, 02:39 AM
  2. Replies: 1
    Last Post: 07-17-2007, 04:06 AM
  3. Replies: 0
    Last Post: 07-16-2007, 06:16 AM
  4. Ip address Data Type DBI
    By Application Development in forum Perl
    Replies: 2
    Last Post: 05-11-2006, 08:44 AM
  5. Converting data read using ADO in VB to a VC++ data type
    By Application Development in forum ADO DAO RDO RDS
    Replies: 0
    Last Post: 07-15-2004, 04:17 PM