Migration Meta Data Storage

Hi All,
I am doing a migration from different systems to SQL Server 2005. I want to
have the mapping from source to destination mapped some where. What is the
best method of representation of these mapping?
I am now using "extendedproperties"
Thanks...ShafHi
What do you meant by "mapping from source to destination mapped some where"?
A database structure, an object structure, Login's mapping to User?
Ho do you do a migration?
"Shaf.Khalidh" <itsprobablyme@.msn.com> wrote in message
news:OGqNTomnGHA.776@.TK2MSFTNGP04.phx.gbl...
> Hi All,
> I am doing a migration from different systems to SQL Server 2005. I want
> to have the mapping from source to destination mapped some where. What is
> the best method of representation of these mapping?
> I am now using "extendedproperties"
> Thanks...Shaf
>|||Mapping of source table (foxpro, access, xls, file) column to a destination
table (sql server) column.
Just a representation which shows which source column is going to store in
the sql server table.column.
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:%23DprnBnnGHA.1076@.TK2MSFTNGP03.phx.gbl...
> Hi
> What do you meant by "mapping from source to destination mapped some
> where"? A database structure, an object structure, Login's mapping to
> User?
> Ho do you do a migration?
>
> "Shaf.Khalidh" <itsprobablyme@.msn.com> wrote in message
> news:OGqNTomnGHA.776@.TK2MSFTNGP04.phx.gbl...
>|||Hi
Have a look at SSIS . (DTS in SQL Server 2000)
"Shaf.Khalidh" <itsprobablyme@.msn.com> wrote in message
news:udaCxPnnGHA.3532@.TK2MSFTNGP04.phx.gbl...
> Mapping of source table (foxpro, access, xls, file) column to a
> destination table (sql server) column.
> Just a representation which shows which source column is going to store in
> the sql server table.column.
>
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:%23DprnBnnGHA.1076@.TK2MSFTNGP03.phx.gbl...
>

Migrating Systems

I am to be involved in moving 3 clusters soon from one data center in the
Northeast to Texas. The main requirement is to have the shortest cutover
period possible via some kind of replicated technologies.
System 1 - 64-bit SQL Server 2000 SP4 to a like environment. I see no
issue with that one. Stage the new server, restore a backup and put it in
log shipping or use a product like Double-Take to keep things in sync.
System 2 - 32-bit SQL Server 2000 SP3a to 64-bit SQL Server 2000 SP4. This
instance has over 200 databases on it. Don't think log shipping is an
option here. It's not indexed well enough for replication and because the
environments aren't like I don't think Double-Take will work. Ideas?
System 3 - 32-bit SQL Server 7 SP4 to a 64-bit SQL Server 2000 SP4. The SQL
7 cluster is currently on Windows NT. Same scenario as System 2.
Ideas?
I think the fastest way to do this is to migrate all dependencies and
accounts, and then detach and reattach the databases on the new server. Copy
the database don't move them.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Cathy Soloway" <CathySoloway@.discussions.microsoft.com> wrote in message
news:8C4A9E42-D424-4DF9-A5ED-1C3821F2E033@.microsoft.com...
>I am to be involved in moving 3 clusters soon from one data center in the
> Northeast to Texas. The main requirement is to have the shortest cutover
> period possible via some kind of replicated technologies.
> System 1 - 64-bit SQL Server 2000 SP4 to a like environment. I see no
> issue with that one. Stage the new server, restore a backup and put it in
> log shipping or use a product like Double-Take to keep things in sync.
> System 2 - 32-bit SQL Server 2000 SP3a to 64-bit SQL Server 2000 SP4.
> This
> instance has over 200 databases on it. Don't think log shipping is an
> option here. It's not indexed well enough for replication and because the
> environments aren't like I don't think Double-Take will work. Ideas?
> System 3 - 32-bit SQL Server 7 SP4 to a 64-bit SQL Server 2000 SP4. The
> SQL
> 7 cluster is currently on Windows NT. Same scenario as System 2.
> Ideas?
>