Len Kally
asked on
SQL 2012 + shared storage
what is the best practice for memory confirmation of SQL 2012 when the server is using shared/LUN storage?
Thanks
Thanks
ASKER
No this is not a clustered environment. This server is going to be a test server so it will be a stand alone server.
The SQL server will be virtual using Hyper-V. This will be a single instance.
The SQL server will be virtual using Hyper-V. This will be a single instance.
I do not understand what your question is.
Do you mean what is the memory configuration for the VM ?
Physical system spec, presumably the shared storage/lun will be from hyper-v host or is it going to be from a SAN outside the host?
Do you mean what is the memory configuration for the VM ?
Physical system spec, presumably the shared storage/lun will be from hyper-v host or is it going to be from a SAN outside the host?
ASKER
All I am asking for is, I am building a SQL server in a test environment.
What is the best practice for configuring proper memory management for the SQL server.
-- It will have shared storage
-- SQL 2012 R2
-- Server 2012 R2
-- It will not be clustered, it will be stand alone server.
What is the best practice for configuring proper memory management for the SQL server.
-- It will have shared storage
-- SQL 2012 R2
-- Server 2012 R2
-- It will not be clustered, it will be stand alone server.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
what is the best practice for memory confirmation of SQL 2012 when the server is using shared/LUN storage?There's no relation between the storage and memory configuration.
Could you provide detail to make the setup clearer.
Is this a clustered install? Is this an active/active setup meaning each node will have an active instance serving a databases while the other serves up another instance with another database. One node has to handle both instances if it is the remaining node running.
In this scenario the SQL instance can only be allocated as much memory leaving space for the OS as well as the other instance if it were to failover to this node.