3.6.0 MxDB for SQL Server Installation and Administration Guide (5697-7088, December 2007)

Chapter 3: Install SQL Server Instances 32
Copyright © 1999-2007 PolyServe, Inc. All rights reserved.
The following script is a template to set the maximum RAM for a
particular SQL instance. If multiple instances are installed on the node,
you can divide 85% by the number of instances. The exact memory
allocation should be studied and defined for your particular
environment—some instances may require more memory than others.
--Set physical memory limit
exec sp_configure 'show advanced options',1
reconfigure with override
GO
declare @percent int, @mem int
--Set the reserved %
set @percent=15
create table #tmp([Index] int,
[Name] sysname,
[Internal_Value] int null,
[Character_Value] sysname null)
insert #tmp
exec master..xp_msver
select @mem=(1-(@percent/100.))*Internal_Value
from #tmp
where [Name]='PhysicalMemory'
drop table #tmp
exec sp_configure 'max server memory',@mem
reconfigure with override
GO
Requirement for BUILTIN\Administrators Group
PolyServe uses Windows authentication (LocalSystem) to connect to SQL
Server to make changes. This means that the BUILTIN\Administrators
local NT group should be enabled on the primary instance and be part of
the SQL Server SysAdmin role. If the BUILTIN\Administrators group
must be removed from SQL Server, the following script must be run to
explicitly allow LocalSystem account access to SQL Server.
-- Giving LocalSystem account access to sqlserver