1. August 2007 AIMS Coordinators Meeting SQL Server 2005 & ArcSDE 9.2 Scott Rice GIS DBA

2. August 2007 AIMS Coordinators Meeting Background Olathe ArcSDE Installations August, 2005 – ArcSDE 8.3, SQL Server 2000

3. August 2007 AIMS Coordinators Meeting Background Timeline –November, 2006: ESRI Certifies SQL Server 2005 for ArcSDE 9.2 –March, 2007: City of Olathe upgrades SDE to 9.2 and SQL Server from 2000 to 2005 –May, 2007: An ESRI tech answers a post in the support forum saying that there are performance issues with SQL Server 2005

4. August 2007 AIMS Coordinators Meeting Main Issue – Connection Speed, or lack of Bug: Connecting to ArcSDE is very slow after upgrading to SQL Server 2005 Article ID:32762 –Ensure that the SQL Server 2005 database compatibility level is 90. –Install ArcSDE 9.2 Service Pack 2. Result: Nothing –Did both these things and there was no improvement

5. August 2007 AIMS Coordinators Meeting Connection Speed DEMO Connect to Olathe SDE Connect to AIMS SDE

6. August 2007 AIMS Coordinators Meeting Other Issues May 08, 2007 Support forum: http://forums.esri.com/Thread.asp?c=93&f=987&t=22119 1#678636 http://forums.esri.com/Thread.asp?c=93&f=987&t=22119 1#678636 3 Separate issues –1. Connections appear to be made, but no data is visible. Workaround: use Direct Connect –2. DB Compatibility level is not set to 90 Fix: Set DB level to 90 –3. 9.2 introduced support for IPV6 networks, but performance is slow on networks with older components. Workaround: use Direct Connect Result: Nothing, again

7. August 2007 AIMS Coordinators Meeting ESRI Response On support forum –“I have had no problems with the editing speed of ArcGIS Desktop 9.2 and ArcSDE 9.2 on SQL Server 2005. Ray Carnes, ESRI Technical Marketing. “ –In other words, it works for me so what’s the problem?

8. August 2007 AIMS Coordinators Meeting Customer Response On support forum (same thread) –“We're experiencing a similar problem here. We were on SQL 2005 back when we had 9.1 installed and it worked fine, so we know the problem isn't with SQL Server 2005. However, once we upgraded to 9.2 we started experiencing the same EXTREMELY SLOW editing issues you described. “ Specific to editing in 9.2 with SQL Server 2005, but still speaks to the same issue of connection speed.

9. August 2007 AIMS Coordinators Meeting Other May not be SQL 2005 related, but we have had them –Archiving –GeoProcessing Scripts

10. August 2007 AIMS Coordinators Meeting ARCHIVING Apply any patch, then upgrade DB, any Archive FC do not get updated. Precision: Archive FC’s don’t get updated when upgrading the spatial reference “Duplicate shape column”

11. August 2007 AIMS Coordinators Meeting Geoprocessing Several Python scripts, update SDE feature classes –No single script operates on large number of feature classes –Slower performance noticeable, but still work SDE Backup Python script –Copies almost all FC to PGDBs

12. August 2007 AIMS Coordinators Meeting Geoprocessing SDE Backup Python script –Copies almost all FC to PGDBs –Close to 400 FC, Annotation, Views –2 Hours (9.1, SQL 2000) –Test server with 9.2 & SQL 2005 49 Hours to complete Never ran old script on test server Attributed mostly to slower test server 28 Hours on production server

13. August 2007 AIMS Coordinators Meeting Geoprocessing SDE Backup Python script –Daily backup, so 28 hours too long –Service Pack 2 helped a little, cut time in half –Had to remove some FC from backup –Currently takes 6 ½ hours –Only copying about 200 FC total –Have to rely on SQL Server backups for all other feature classes In 24 months been DBA, only had to restore database from backup once

14. August 2007 AIMS Coordinators Meeting Questions? srice@olatheks.org