Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
bcanonica
Starting Member
35 Posts |
 Posted - 2009-04-21 : 08:12:10
|
| I am trying to migrate a Hierarchical database to Sql Server's Relational database. My problem is for example I have a CONTACT record that has multiple PHONENUMBERS, EMAILS, ect. How can I display that in a view without showing numerous extra records for the same CONTACT? Anyone have any experience with this kind of stuff and have any advice. As always thanks in advance,BC |
|
|
pootle_flump
1064 Posts |
Posted - 2009-04-21 : 08:24:48
|
| I've refactored legacy hierarchical databases to relational. I have no idea how the result would look in your hierarchical database, but you should not really worry about that sort of thing in a view. You want to ensure that your presentation layer handles that for you. Typically you would have a header in the report\ form for the contact name etc, and then repeated rows for all the different contact data rows. |
 |
|
|
bcanonica
Starting Member
35 Posts |
Posted - 2009-04-21 : 11:02:01
|
I see what you are saying, but I need to have CONTACT Grid where the users can sort and filter data based on the multiple phone numbers. A repeater won't give me what I want in this case, because it isn't easily sorted and filtered. Any other data layout ideas might improve this process for me? quote:
Originally posted by pootle_flump
I've refactored legacy hierarchical databases to relational. I have no idea how the result would look in your hierarchical database, but you should not really worry about that sort of thing in a view. You want to ensure that your presentation layer handles that for you. Typically you would have a header in the report\ form for the contact name etc, and then repeated rows for all the different contact data rows.
|
|
|
|
pootle_flump
1064 Posts |
Posted - 2009-04-22 : 03:26:14
|
quote:
Originally posted by bcanonica
I see what you are saying, but I need to have CONTACT Grid where the users can sort and filter data based on the multiple phone numbers. A repeater won't give me what I want in this case, because it isn't easily sorted and filtered. Any other data layout ideas might improve this process for me? quote:
Originally posted by pootle_flump
I've refactored legacy hierarchical databases to relational. I have no idea how the result would look in your hierarchical database, but you should not really worry about that sort of thing in a view. You want to ensure that your presentation layer handles that for you. Typically you would have a header in the report\ form for the contact name etc, and then repeated rows for all the different contact data rows.
I recommend you post in an ASP.NET forum (or similar). There are people here that could help you out, but it is not our speciality. This sort of thing is not something that SQL Server concerns itself with. |
|
|
|
wonn1377
Starting Member
3 Posts |
Posted - 2009-08-19 : 07:27:01
|
| I use data loader for migrating almost any data, it helps me to convert MSSQL to MYSQL, MS access to MSSQL, mysql, csv loader,foxpro and MSSQL to MS access,MYSQl, CSV, foxpro etc. In my view this is a best Data Migration Tool Download Free : http://www.dbload.com |
|
|
|
yonision
Starting Member
5 Posts |
Posted - 2009-08-25 : 13:43:35
|
| Hi,Not sure if the focus of your question is the re-arranging of data from hierarchical to rational model (which is a big subject and a full answer would require getting deep into your specifics) but if you are focusing on the actual migration, try this tool, wihch fully migrates hierarchical databases. You still need to write the queries, but its a big help in telling you the differences and migrating. (its still on beta so given out free)[url]http://www.nobhillsoft.com/Columbo.aspx[/url] |
|
|
|
|
|
|
|
|
Hierarchical database migration