+ 0 Votes By CAL? BOUND4DOOM 6 years ago I have never heard of licensing by CAL for SQL server, doesn't mean it doesn't exist, but I never bothered with it. You can license SQL server by CPU which is what I do. Simplifies things a whole lot, this allows for as many users as you want and as many databases in the SQL server you want. Especially if you plan on growing, this would be the best way to go when you can then capitalize it and depreciate it over time. While also I agree dual procs will get great performance. What you should do is buy a server with 2 processors, however only license 1 processor in sql server. You can set SQL server to only use one processors when it installs. This is also perfectly legal. Then see how things perform. However get a ton of RAM and Hard Drive space. Typically the Operating system will then use one processor and then SQL server will use the other. From what you are describing you really do not sound like you are really even going to be tasking the machine that much. However if you find performance lagging you can always buy another proc license later and go into SQL server and tell it to use both processors. I find SQL server extremely well behaved and well performing compared to a lot of databases, some of my dual processors servers easily run 80-90 large databases, large I consider 5 gig +, with 6000-7000 users easily processing thousands of queries a second. However it is all going to depend what you are running on these databases, like if your using SQL reporting and application services etc. If the developer is really good then he should be able to tweak for maximum performance or at least get creative to save you some money. That's the problem with most programmers these days it that they do not make things performs like they did in the old days when hardware was limited. They just throw more hardware at the problem. I could be wrong about your situation but I see this a lot. I do a lot for the new bankrupt auto industry so I am used to building high scale performing applications that need to run on low budget hardware. Anyway by getting creative and tweaking I would question why reindexing couldn't be done in the middle of the night or at a time when there are less users on. Example if this is factory based systems, then break time or lunch times, again good programmers should take advantage of everything to squeeze the most out of performance and not interrupt the users. Jobs or other things could me moved out of SQL server to run as windows services on low priority threads again then taking advantage of both CPU's because the programmer built the windows service it is not licensed. See what I mean really get creative. I would suggest calling a Microsoft Licensing rep and asking them what is best in your situation explain to them what you want to do and if you want to grow and change in the future. You might be surprised they are very helpful they might even be able to be more creative and make other arrangements, like if you decide to go by cal you can buy like 100 and if you find your not using it then return 50 or so for your money back later or go under a software assurance model where you pay over time or something like that.