Select to view content in your preferred language

SDE 9.3.1 on Windows Server 2008 R2 with Postgres?

1016
4
06-15-2010 11:54 AM
StefanOffermann
Deactivated User
Hi,
I know that this combination is not officially supported by ESRI, but I want to get ArcSDE 9.3.1 running on a machine with Windows Server 2008 R2 (64bit) and a Postgres database. Has anyone tried this combination yet?

A more generel question: If a combination of SDE, operating system and DBMS is not officially supported by ESRI, does this mean that there is not a chance to get it running?

Best regards, Stefan
0 Kudos
4 Replies
VinceAngelo
Esri Esteemed Contributor
There is no 64-bit PostgreSQL or ArcSDE for PostgreSQL build, just 32-bit. You'd
probably be *way* better off configuring that host as a Linux server.

There's a number of degrees of functionality between "certified" and "won't work".
The likelihood of complete failure depends on how far you stray from the support
umbrella.

- V
0 Kudos
StefanOffermann
Deactivated User
My approach was to install the 32 bit Versions of Postgres 8.3 and ArcSDE 9.3.1 on the 64 bit machine, I don't know if thats running me into big problems.

One thing I found out by testing is that all tables are created in the schema "sde" instead of the user-schemas. Can I assume that this a specific error arising of Windows Server 2008 R2?

Setting up another operating system is a solution, but this is not in my hands. Hope the admins will have mercy with me 😉

Best regards, Stefan
0 Kudos
VinceAngelo
Esri Esteemed Contributor
That's pretty bizarre behavior.  I can't lay it at the feet of Windows 2008 R2 wtihout
knowing whether you're using the PostgreSQL 8.3.0 which ships in the ArcSDE install
media.

It is generally unwise to use a database or OS which wasn't available when the
"current" ArcSDE service pack was produced (figure two months before release).
9.3.1 SP2 release is imminent; you might have better luck with that.

- V
0 Kudos
StefanOffermann
Deactivated User
Shame on me, it works now. I actually entered the user "sde" in the sde connection file.... my fault.
0 Kudos