Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
Sitka
Aged Yak Warrior
571 Posts |
 Posted - 2004-07-29 : 09:39:10
|
| Hi we have about 30 fat client ERP applications running that use a single application user to connect to SQL2000, maybe another 20 other assorted Windows Application installs with various databound controls (some written in Delphi) and about 400 users across a couple plants that access SQL driven web pages. Total PC's (devices) is around 250. For a dual proc server is this close to the bubble for going to per user/device licencing or is the cost effective option per processesor.I thought I understood it when I read this but now I'm not so sure..http://www.tek-tips.com/gfaqs.cfm/pid/962/fid/5153<miny rant>Microsoft seems to emphasise a notion of "not accross firewalls" in their latest how to buy scenerios. WTF does that matter.</miny rant>It is a rich creamy color with a high fat content of 5-7 percent. Being so high in fat, it is usually processed into butter, cheese, or yogurt. An average cow will produce 110 kg. Milk in a lactation period of an average of 149 days |
|
|
MuadDBA
628 Posts |
Posted - 2004-07-29 : 09:57:48
|
| If you're on Enterprise edition, this is true...at around 250 users, the prices start to even out and then you end up spendign more on CALs than if you would have just bought a per-processor license in the first place. (With standard edition you should have switched over much earlier) Also keep in mind that this is at the Microsoft MSRP. If you don't buy your CALs at their exhorbitant markup, you need to redo the calculations.The questions you should ask yourself are:1) Did you already buy a bunch of CALs? (ie do you have 240 and now you have about 250 users, meaning only 10 more to buy)2) What is your projected CAL growth rate? (ie if you aren't going to get much past the point where the cost starts to be more for the CAL method before you upgrade to Yukon, don't bother with per processor, as you're going to be starting over again very soon) |
 |
|
|
Sitka
Aged Yak Warrior
571 Posts |
Posted - 2004-07-29 : 10:09:22
|
| Hmm I didn't include enough details. The cals exist(ed) as a part of the MS partner ERP purchase. SQL7This will become SQL Standard 2000 dual in the above mentioned situation.Yeah timing of Yukon sucks. I think my MSDN is going to run out before I can get my copy; the way things go around here Yukon is two years away at least as far as going productionSo 1.) No there are not already a bunch of CALS.2.) Projected, 10 more a year but we have taken over some small companies +20 +30 so to speak.Thanks.It is a rich creamy color with a high fat content of 5-7 percent. Being so high in fat, it is usually processed into butter, cheese, or yogurt. An average cow will produce 110 kg. Milk in a lactation period of an average of 149 days |
|
|
|
MuadDBA
628 Posts |
Posted - 2004-07-29 : 12:15:26
|
| Well if you are going to be on Standard edition with 250 users, I think you're going to be better off licensing per processor and just be done with it.Keep this in mind, though...a CAL is a per-device thing. If you buy a device CAL, it works for ANY SQL Server. In other words, if 240 of your 250 devices already have a SQL 2K CAL for another app, you don't have to buy them another one to connect to yours...so you might not need to do per processor. |
|
|
|
Sitka
Aged Yak Warrior
571 Posts |
Posted - 2004-07-29 : 12:40:12
|
| Excellent. Thanks crazyjoe.It is a rich creamy color with a high fat content of 5-7 percent. Being so high in fat, it is usually processed into butter, cheese, or yogurt. An average cow will produce 110 kg. Milk in a lactation period of an average of 149 days |
|
|
|
derrickleggett
Pointy Haired Yak DBA
4184 Posts |
Posted - 2004-07-29 : 14:34:47
|
| Also, crazyjoe alluded to this, but you need to take what your actual cost will be for the per processor option as well. It's just like paying for CAL's. Nobody pays the full price for either option, unless they just like giving money away. :)We ended up paying $12,000 for Enterprise per processor. We didn't have much of a choice since we have tons of internet and internal users.MeanOldDBAderrickleggett@hotmail.comWhen life gives you a lemon, fire the DBA. |
|
|
|
|
|
|
|
|
Licence for ERP intranet