MICROSOFT##SSEE blocks Surface Area Configuration in SQL 2005?

I am running a Windows Small Business Server with SQL Server 2005 on it. I am having a problem in that one of the applications I'm running needs to acess the xp_cmdshell component which is disabled by default. The problem I'm running into is, trying to run the Surface Area Configuration Wizard to turn this on fails because the system is unable to access the MICROSOFT##SSEE instance on the machine.

I dont want to modify the MICROSOFT##SSEE instance, I want to modify a different instance but the wizard detects ALL instances of SQL and craps out trying to access the MICROSOFT##SSEE instance.

Is there a way for me to activate the xp_cmdshell component on other instances without the wizard?

Hi,

Run this code in your query window:

Code Snippet

sp_configure 'xp_cmdshell', 1

reconfigure

Regards,

Janos

|||

I get the following message:

Msg 15123, Level 16, State 1, Procedure sp_configure, Line 51

The configuration option 'xp_cmdshell' does not exist, or it may be an advanced option.

|||

Hi Ron,

First you need to switch on the advanced options, then configure the xp_cmdshell.

run this please:

Code Snippet

sp_configure 'show advanced options', 1

reconfigure

sp_configure 'xp_cmdshell', 1

reconfigure

regards,

Janos

|||Thank you, that did the trick... now I just have to get my code to work <grin>

Microsoft##EESS and MSDE SQL 2000 on Windows 2003 Small Business Server

Currently a server running 2003 small business operating system has MSDE 2000 and Microsoft##SSEE.

A memory problem exists with SQL consuming over 50% of RAM. Total RAM is 4GB.

There is a SQL 2000 patch for this type of problem. However, it calls for SQL to be upgraded to SP4.

Problem:
Can this MSDE 2000 be upgraded with SP4 and have memory patch applied with Microsoft##SSEE also on this box?

Please let me know. Thank you.

Yes.

You might also investigate setting the MAX memory setting for both SQL instances.

|||

Hi,

Yes you can update with SQL Server SP4.

Refering to SQL Server memory architecture it goes upto maximum limit specify by you, and if not specified it can eat up all the memory it can access and freed up as N when require by another resources. I think below articles are good enough to clear it

http://sqljunkies.com/Tutorial/0D4FF40A-695C-4327-A41B-F9F2FE2D58F6.scuk

http://msdn2.microsoft.com/en-us/library/ms187499.aspx

HTH

Hemantgiri S. Goswami