January 10, 2008 at 12:00 pm
Most of the servers I admister have one instance per server. We have encountered a purchased package that requires it's own instance but we want to put it on shared infrastructure.
Does anyone have any issues with putting multiple instances on one box, even if it is virtualized? Any administration issues I should be aware of?
Thanks!
January 10, 2008 at 1:02 pm
I work in a development shop, all of our SQL boxes have multiple instances of SQL Server. On the larger one we run 7 instances, a mix of 2000 and 2005.
We have not experienced any issues that would make us believe we should not be running in this way. You can even limit RAM and CPU cores on a per instance basis so one particular instance does not hammer the others.
January 10, 2008 at 1:05 pm
Adam Skelton (1/10/2008)
I work in a development shop, all of our SQL boxes have multiple instances of SQL Server. On the larger one we run 7 instances, a mix of 2000 and 2005.We have not experienced any issues that would make us believe we should not be running in this way. You can even limit RAM and CPU cores on a per instance basis so one particular instance does not hammer the others.
Actually, Adam - how do you limit the Cores in SQL 2005? I was looking for that in 2005 earlier, and I can't seem to find it where I used to (Options, Processors).
----------------------------------------------------------------------------------
Your lack of planning does not constitute an emergency on my part...unless you're my manager...or a director and above...or a really loud-spoken end-user..All right - what was my emergency again?
January 10, 2008 at 1:28 pm
You can use sp_configure to set an affinity mask for the server instance.
See:
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/5823ba29-a75d-4b3e-ba7b-421c07ab3ac1.htm
in Books Online for details.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
January 10, 2008 at 1:30 pm
Hi Matt,
I think you are looking in the right place. All I do is open SS Management studio right click the instance in question and look at the processor page.
The cores will show up as 'processors' so it will appear that you have more then you really do.
Adam
January 10, 2008 at 1:40 pm
So affinity mask set to 0 for a specific processor core means - don't use it? It's worded so very awkwardly. I hate when they tap-dance around the issue without ever ACTUALLY answering the d*** question.
At least 2000 had a "dedicate this CPU/use this CPU for SQL Server"....
What's up the licensing policy then? How To License SQL Server states that in per processor, you MUST license for all CPU's the OS can see (either the Physical CPU's a physical OS has, or - the virtual CPU's a virtual instance seess), NOT how many CPU's are assigned to running SQL server (which was the 2000 policy as I remember).
<sigh>
----------------------------------------------------------------------------------
Your lack of planning does not constitute an emergency on my part...unless you're my manager...or a director and above...or a really loud-spoken end-user..All right - what was my emergency again?
January 10, 2008 at 1:48 pm
If you licence SQL Server per processor it does not matter how many instances you run.
Just my $0.02
* Noel
January 10, 2008 at 1:51 pm
licensing is by processor not core I believe
January 10, 2008 at 2:15 pm
By the way the "free" "Instances" are only for Enterprise Edition...
* Noel
January 10, 2008 at 2:21 pm
noeld (1/10/2008)
By the way the "free" "Instances" are only for Enterprise Edition...
Under 2005 - that's not actually correct. Multi-instancing is allowed in a single OS instance under the same SQL license for Standard and better (Standard, Workgroup and Enterprise).
----------------------------------------------------------------------------------
Your lack of planning does not constitute an emergency on my part...unless you're my manager...or a director and above...or a really loud-spoken end-user..All right - what was my emergency again?
January 10, 2008 at 2:24 pm
Adam Skelton (1/10/2008)
licensing is by processor not core I believe
correct - but notice this little time-bomb:from "how to license"
A license is required for each physical or virtual processor accessed by an operating system environment running SQL Server. This license does not require any device or user client access licenses (CALs).
Notice that is said - "accessed by the OS". Meaning - you can limit SQL to use less than the max processors, but you STILL have to own processor licenses for all physical procs...strange.
----------------------------------------------------------------------------------
Your lack of planning does not constitute an emergency on my part...unless you're my manager...or a director and above...or a really loud-spoken end-user..All right - what was my emergency again?
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply