Hello,
I have a Production SDE Database with 2000 Feature Classes. I have a list of 1400 that I need to move to a new SDE Database. what is the best way to achieve this. Thanks.
Solved! Go to Solution.
"SQL" is a language, not an RDBMS; do you mean "Microsoft SQL Server"?
Changing database names is going to limit your options -- You can't use a backup/restore or detach/reattach, so you'll need to reconcile/post/compress all your versions to get the source database as close to a zero state as you need, then copy all the feature classes you want to keep (one by one, in a script) and reversion all the tables you need versioned.
If you use the same database name, then you have many more options (and many more potential complications).
- V
More details needed:
Note that the current term of art is "enterprise geodatabase" (hasn't been "SDE" since 8.0 was released)
- V
Hi Vince,
1. 10.6 Desktop and 10.5.1 Enterprise
2. SQL
3.Database name is different
4.10.6
5.mix of versioned and non-versioned
6. old one stays on the other VM and no they do not need to synced
ohh that is really helpful to know that the lingo has changed. thanks.
Tom
"SQL" is a language, not an RDBMS; do you mean "Microsoft SQL Server"?
Changing database names is going to limit your options -- You can't use a backup/restore or detach/reattach, so you'll need to reconcile/post/compress all your versions to get the source database as close to a zero state as you need, then copy all the feature classes you want to keep (one by one, in a script) and reversion all the tables you need versioned.
If you use the same database name, then you have many more options (and many more potential complications).
- V