Select to view content in your preferred language

Copy a section of SDE Tables from gdb to another gdb

502
3
Jump to solution
07-06-2022 08:45 AM
TomDonovan-Brady1
Emerging Contributor

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. 

1 Solution

Accepted Solutions
VinceAngelo
Esri Esteemed Contributor

"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

View solution in original post

0 Kudos
3 Replies
VinceAngelo
Esri Esteemed Contributor

More details needed:

  1. What version of ArcGIS?
  2. Using which RDBMS?
  3. If non-Oracle, is the database name going to be the same?
  4. At what release is the geodatabase?
  5. Are all the tables non-versioned?
  6. What happens after the move? (Does the old database go away?  Do they need to be kept in sync?)

Note that the current term of art is "enterprise geodatabase" (hasn't been "SDE" since 8.0 was released)

- V

TomDonovan-Brady1
Emerging Contributor

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 

0 Kudos
VinceAngelo
Esri Esteemed Contributor

"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

0 Kudos