Aaron Daniels's questions

When setting up a linked server in SQL Server (we're on 2005), you can set two server options:

• Rpc
• Rpc Out

Looking at the MSDN article, all it states is:

RPC - Enables RPC from the specified server.

RPC Out - Enables RPC to the specified server.

My question is, why would I need to set these options? What can I do / not do by enabling Rpc on a linked server? Does setting these options to true have any drawbacks?

EDIT:

But to execute the remote stored procedure, you'd need the "RPC Out" setting enabled. When would you ever need the "RPC" setting enabled?

One of our SQL Servers, which has been running stable for quite some time (years), has recently been throwing insufficient memory errors. From the Application Event Log, we see:

Event ID: 701

Description: There is insufficient system memory to run this query.

Our team that manages this server is made up of mostly developers that double up on the sysadmin duties. However, our primary expertise is development. That being said, we are at a loss on how we go about troubleshooting this. We've been scouring forums and whatnot and haven't found anything that matches

So, here are some more details to aid in troubleshooting:

• Our Minimum server memory is set to 0.
• Our Maximum server memory is set to 2000.
• Total Physical Memory is 3,325.85 MB (from sysinfo).
• Total Virtual Memory is 7.10 GB (from sysinfo).
• We were not using AWE to allocate memory, but we are now to see if it makes a difference.
• This error was thrown by a job that was backing up a transaction log, not running a query.
• We have many linked servers. The types of RDBMS on the other side are SQL Server (2005 and 2000), Oracle 10g, and OSI PI systems.
• It is intermittent at this point. We cannot seem to correlate any time or event to the errors.
• Of course, rebooting seems to make it go away for a while, which makes sense due to the nature of the error message.
• This server triples as an application server (a couple of Windows Services) and a web server, as well as the database server.

EDIT:

We are on SP3. Most of the posts we found were pre SP1, which doesn't apply to us.

SELECT  SERVERPROPERTY('productversion'), SERVERPROPERTY ('productlevel'), SERVERPROPERTY ('edition')

returns

9.00.4035.00 SP3 Standard Edition

One of our server administrators set up 1 web site per web application. This is mainly to have different host headers per application. (We also create DNS entries per application, allowing the web application to be moved across servers without having to change links or bookmarks.) Is there any overhead or performance issues in doing this?

In other words, are there any major issues with having 500 websites with 1 web application each instead of 1 web site with 500 web applications?

EDIT:

Let's assume each web site always has its own application pool. My question is really:

Is a web site just another configuration option with no overhead, or does creating many web sites decrease performance? (at all, even if it is minuscule?)