One important performance enhancement that is present in Enterprise Edition and not other editions is EE makes better use of prefetch. According to the Microsoft article below:

"SQL Server Enterprise...

How large (# pages) is the secondary index? If it's only 10 pages (like in your example), than the fragmentation pct. reported will not be accurate.

Ray,

You don't mention which platform DB2 is running on, is it Z/OS, Unix or something else?

Nevertheless, the -805 means that the packages that the client is calling are not found...

Thanks Lynn! I'll give that a try and see how it works.

I'm getting the exact same error only with a maintenance plan doing log backups. It also only occurs very intermittently. Also using SQL 2005 SP2.

Getting a similiar type of intermittent error with a SSIS maintenance plan job that backs up transaction logs. This is with SQL 2005 SP2:

Executed as user: DMZ\!svc.sql. Microsoft (R) SQL...

Look in the registry under the following:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP

I would agree you should talk with your DB2 DBAs. However, you only need DB2 Connect to reach a Z/OS mainframe or AS/400 not a Sun/Solaris box.

The answer to your first question would be yes. And within SSMS you can do both within the same task. See below.

For the second question: I would recommend using SSMS,...

Looks like the recommended RAM of 1GB could be causing the warning.

From the link http://technet.microsoft.com/en-us/library/ms143506.aspx: 

3SCC will warn the user but will not block Setup if the minimum or recommended RAM...

See this good article "Leverage your Microsoft SQL Server 2000 Skills to Learn DB2 UDB Version 8"

Here's the  link: http://www-128.ibm.com/developerworks/db2/library/techarticle/0307chong2/0307chong2.html

I think DB2 has SQL Server beat on this one!

Here's a hotfix that takes care of this problem. I've installed it and it does work.

 http://support.microsoft.com/kb/918644

I hate those page peel ads, I'd prefer a less intrusive way of advertising. 

The short answer is encrypted stored procedures can not be replicated.