Select to view content in your preferred language

Installing ArcSDE 10.1 Steps

792
4
Jump to solution
10-22-2012 06:52 AM
ElizabethB
Deactivated User
Hello All-
Does anyone have a streamlined list or workflow, etc of how a new installation of ArcSDE 10.1 should go? We are currently using 9.3 & I was told we would be upgrading to 10.1 (which seemed fairly straightforward). Now I am being told we are going to get a new server so in essence we will be installing 10.1, not upgrading, however we have these existing connections & datasets.  We have an Enterprise GIS here, with topology & versioning. Our server will have SQL Server Management Studio, am not sure of version, possibly 2008 R2, we also have Windows 7 OS.

I am not an sde admin but have sql experience.  I???ve read through the help docs & still have some questions.

First, do I install ArcSDE first or create the geodatabase first? I assumed SDE went first but read online that I need to have a geodatabase created first. Which is it? Also, is this the basic sequence of steps:

1) ensure SQL server & ArcCatalog is installed on new server
2) install ArcSDE on new server. Configure connections using old connection properties.
3) detach 9.3.1 database from old server using Mgmt Studio
4) copy db over to new server
5) attach db
6) run the upgrade gdb tool to upgrade the 9.3 db over to 10.1


Am I on the right track? I???m kind of panicking because I was told ???oh we???re upgrading??? but actually we are not upgrading we are installing a newer version & only upgrading the database. I haven???t read anything specifically geared to this situation, any help is greatly appreciated!

Thanks in advance.
Elizabeth
0 Kudos
1 Solution

Accepted Solutions
VinceAngelo
Esri Esteemed Contributor
You might find it easier thinking of this as two processes -- porting a 9.3.1 db to
a new server, and upgrading the new db to 10.1 (though you can't really do it
that way because 2008 R2 isn't supported by 9.3.1).

Your step 2 is the only incorrect part -- you can't change connection properties
until there's a database ready for connection -- but I'd recommend some missing
steps:

A) Ensure SQL server & ArcGIS Destop is installed on new server
B) Perform extra backup on old server
C) Remove all active client connections
D) Reconclile and post as much as possible
E) Stop 931 service (if running)
F) Detach 931 database from old server
G) Copy all filegroup files to new server
H) Attach old files to new server (make sure to upgrade the database level)
I) Perform any necessary user/login synchronization (sp_change_users_login)
J) Install 10.1 ArcSDE application server (no postinstall)
K) Apply 10.1 SP1 (optional -- due out real soon now)
L) Run the upgrade gdb tool to upgrade the 9.3 db over to 10.1
M) Use 'sdeservice' to create a new application server service (optional)
N) Update connection files to use the new server connection properties
(if you have the luxury of using a DNS name, consider doing this, since
future upgrades would just be a DNS change)

Keep in mind that 10.0 post-SP1 clients can connect to 10.1 servers, but
9.3.1 clients cannot, so all the clients that need to connect should be
in supported range before stating upgrade.

- V

View solution in original post

0 Kudos
4 Replies
VinceAngelo
Esri Esteemed Contributor
You might find it easier thinking of this as two processes -- porting a 9.3.1 db to
a new server, and upgrading the new db to 10.1 (though you can't really do it
that way because 2008 R2 isn't supported by 9.3.1).

Your step 2 is the only incorrect part -- you can't change connection properties
until there's a database ready for connection -- but I'd recommend some missing
steps:

A) Ensure SQL server & ArcGIS Destop is installed on new server
B) Perform extra backup on old server
C) Remove all active client connections
D) Reconclile and post as much as possible
E) Stop 931 service (if running)
F) Detach 931 database from old server
G) Copy all filegroup files to new server
H) Attach old files to new server (make sure to upgrade the database level)
I) Perform any necessary user/login synchronization (sp_change_users_login)
J) Install 10.1 ArcSDE application server (no postinstall)
K) Apply 10.1 SP1 (optional -- due out real soon now)
L) Run the upgrade gdb tool to upgrade the 9.3 db over to 10.1
M) Use 'sdeservice' to create a new application server service (optional)
N) Update connection files to use the new server connection properties
(if you have the luxury of using a DNS name, consider doing this, since
future upgrades would just be a DNS change)

Keep in mind that 10.0 post-SP1 clients can connect to 10.1 servers, but
9.3.1 clients cannot, so all the clients that need to connect should be
in supported range before stating upgrade.

- V
0 Kudos
ElizabethB
Deactivated User
Vince-
Wow, thanks for this. You've listed things I had overlooked.  I'm going to print out your answer & study it. For Step I (user/login synchs), can you point me to a white paper or some doc that will walk me through that? Am not sure what that entails.


Elizabeth
0 Kudos
VinceAngelo
Esri Esteemed Contributor
Search both these forums and the web in general on "sp_change_users_login"
for background.  Basically, when you attach a database, the login-user match
might not be right, and that will create a situation where users don't have read/
write access to their own tables.

- V
0 Kudos
ElizabethB
Deactivated User
Okay, thanks so much, I will.
0 Kudos