Re: How should I store city, state values for addresses, please help.
From: JBLi (newsgroup_at_lidesigners.com)
Date: 02/25/04
- Next message: Andreas Klemt: "HowTo UNION multiple exec GetTables ?"
- Previous message: Vishal Parkar: "Re: Difference between create table #temp and ##temp ?"
- In reply to: Bob Boran: "Re: How should I store city, state values for addresses, please help."
- Next in thread: Petrik Salovaara: "Re: How should I store city, state values for addresses, please help."
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 24 Feb 2004 20:41:35 -0500
Hi Bob,
Thanks. your suggestion properly work great for initial data transfer.
Please read my reply to Petrik for my additional concerns.
Thanks,
JB
"Bob Boran" <mcsdsmurf@hotmail.com> wrote in message
news:%23DzuYMx%23DHA.3668@TK2MSFTNGP09.phx.gbl...
> One option you have is to import all the old data before you start
creating
> new records, when you do that turn identity_insert on for the table as you
> import the data. This will retain the current identity values and all the
> old relationships will still be intact.
>
>
> "JBLi" <,, newsgroup@lidesigners.com> wrote in message
> news:eyS#8Ax#DHA.392@TK2MSFTNGP12.phx.gbl...
> > Hi All,
> >
> > I am writting an real estate website for a company. I need some
> > advices on how should I store fields like city, and state for addresses.
> >
> > Originally, I was thinking to store the city and state as numeric
> > fields (in the main Houses table) and having extra one table for cities
> and
> > one table for states; such that the city and state fields contains the
> > identity (column) values from the tables.
> >
> > The problem is that my client already has an old website database
> which
> > using the same idea as above. I need to of course, transfer all the
> > property records from the database to my new database. So if the
cities
> > and states tables are recreated in my new database, the indentity column
> > values will not match those (tables) in the old database, which were
> already
> > in use in the property records of the old database (the Houses table).
> That
> > is, let say one property record's city field value is 123 (which is an
> > identity column value in the old database for the city, Brooklyn). And
let
> > say I create the cities table in my new database and having a city
record
> > for Brooklyn with value 456. If I transfer the property record to the
new
> > database, as you can see, the city value 123 is not the same as 456. I
> > cannot really lookup by the city name at this point since the old
database
> > may contain bad city name spellings.
> >
> >
> > Thanks for any suggestions. I may consider to store Cities and
> states
> > as plain strings to avoid future problems.
> >
> >
> > Regards,
> >
> > JB
> >
> >
>
>
- Next message: Andreas Klemt: "HowTo UNION multiple exec GetTables ?"
- Previous message: Vishal Parkar: "Re: Difference between create table #temp and ##temp ?"
- In reply to: Bob Boran: "Re: How should I store city, state values for addresses, please help."
- Next in thread: Petrik Salovaara: "Re: How should I store city, state values for addresses, please help."
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
