Resources for IT Professionals >
포럼 홈
>
Windows HPC Server Job Submission and Scheduling
>
What kind of licenses are required for Microsoft SQL Server?
What kind of licenses are required for Microsoft SQL Server?
- What kind of licenses are required for Microsoft SQL Server, in order to provide a high-performance back-end for Windows HPC Server's scheduler service?
We're currently running everything on the headnode, but we run a lot of jobs. Our database currently has 189993 jobs in the queue (most of them are finished) -- but we shuffled about 1.2 million records into an archive database earlier today. So, we're planning to offload the SQL service onto a dedicated database server.
So, my questions are as follows:
- Is the headnode the only machine who accesses the database directly? Or would all of the compute nodes need to access the database directly?
- We're thinking about Microsoft SQL Server Enterprise Edition, since we're likely to put this on a beefy 8-core box.
What licensing model would you use for an 8-core box (possibly appearing as 16 CPUs, with hyperthreading)?
Is there more than one licensing model for the "Enterprise" edition -- or is Enterprise Edition "unlimited"?
Would some other edition make sense?
Thanks,
-Luke
답변
- Hi Luke
I've investigated offloading the COMPUTECLUSTER database instance onto a dedicated resource myself, and to summarise I've found out that this is currently not a supported configuration in V2, but will "probably" be suported in V3. This information notwithstanding, it is of course possible to migrate the entire headnode infrastructure onto more substantial hardware.
It's difficult to be definitive when it comes to licensing questions, probably best to speak to the MS licensing guys direct as it can get quite complicated. My understanding, however, is that the 4 CPU limit on SQL Server Std edition relates to sockets rather than cores, so a dual socket, 8 core server requires only Standard edition. The license model depends on how many clients access the database instance, you'll need to balance the cost of per server + CAL for each user licensing against the alternative per processor model. Of course there is a tipping point at which using the per processor model becomes financially advantageous. Have a look at this document, particularly the first three sections for some insight into things:
http://www.microsoft.com/Sqlserver/2005/en/us/special-considerations.aspx
Enterprise edition is a significant outlay, particularly if you do not require the additional features it brings to the table.
Hope this helps
Dan- 답변으로 표시됨Josh BarnardMSFT, 소유자2009년 5월 28일 목요일 오후 7:02
- Dan is correct; the only supported scenario in HPC Server 2008 is to have the database on the HN. We do have some recommendations on how to configure the Database and HN hardware in this document: http://go.microsoft.com/fwlink/?LinkId=137791
In more direct response to your first question, only the head node of the cluster directly accesses the DB; any DB information touched by the CN's is done via internal API's.
Thanks,
Josh
-Josh- 답변으로 표시됨Luke Scharf 2009년 5월 28일 목요일 오후 7:38
- 답변으로 표시됨Luke Scharf 2009년 5월 28일 목요일 오후 7:38
모든 응답
- Hi Luke
I've investigated offloading the COMPUTECLUSTER database instance onto a dedicated resource myself, and to summarise I've found out that this is currently not a supported configuration in V2, but will "probably" be suported in V3. This information notwithstanding, it is of course possible to migrate the entire headnode infrastructure onto more substantial hardware.
It's difficult to be definitive when it comes to licensing questions, probably best to speak to the MS licensing guys direct as it can get quite complicated. My understanding, however, is that the 4 CPU limit on SQL Server Std edition relates to sockets rather than cores, so a dual socket, 8 core server requires only Standard edition. The license model depends on how many clients access the database instance, you'll need to balance the cost of per server + CAL for each user licensing against the alternative per processor model. Of course there is a tipping point at which using the per processor model becomes financially advantageous. Have a look at this document, particularly the first three sections for some insight into things:
http://www.microsoft.com/Sqlserver/2005/en/us/special-considerations.aspx
Enterprise edition is a significant outlay, particularly if you do not require the additional features it brings to the table.
Hope this helps
Dan- 답변으로 표시됨Josh BarnardMSFT, 소유자2009년 5월 28일 목요일 오후 7:02
- Dan is correct; the only supported scenario in HPC Server 2008 is to have the database on the HN. We do have some recommendations on how to configure the Database and HN hardware in this document: http://go.microsoft.com/fwlink/?LinkId=137791
In more direct response to your first question, only the head node of the cluster directly accesses the DB; any DB information touched by the CN's is done via internal API's.
Thanks,
Josh
-Josh- 답변으로 표시됨Luke Scharf 2009년 5월 28일 목요일 오후 7:38
- 답변으로 표시됨Luke Scharf 2009년 5월 28일 목요일 오후 7:38
