I have a question concerning the ridiculous quagmire of SQL Server licensing…
How is SQL Server licensed when used to store session state information?
Is MS claiming that this is an end user use of SQL Server functionality?
Or, can we be realistic and say that I need a server license plus a device license for each web server?
Personally, I like everything about SQL Server except the licensing.
Management at my company has already said that we’ll most likely be moving to either Firebird or Postgres after they found out how much it would cost to move from SQL 2k to SQL 2005.
If MS wants us to buy processor licenses for SQL state servers, I guarantee we’ll be doing something else there as well.
I wonder if Microsoft has any clue how much business they’re losing.
Not just in SQL Server, but in their OS business as well.
The 2.0 version of ASPSTATE is slightly different than the 1.1 version in that one table has one additional column and another table uses a different data type and size for the key. The 2.0 version also has a couple additional stored procedures.
We'd like to manage just one session state database if possible so we're trying to figure out if Microsoft supports using the new schema for 1.1 session state access (it seems to work, but our testing has been very light).
Is there any official support line on this? If not, can anyone comment on whether or not you'd expect it to work and why?
If SQL Server 2000 is loaded onto a 8 processor machine, can I legitimately load Standard Edition, which will only use 4 of the 8 processors, or as some interpretations of the license suggest, must I purchase Enterprise Edition (i.e. you are not permitted to load SQL Server on a machine which has more processors than the Product is capable of using) ?.
I know the "reasonable" answer, but what is the legal position ?
My company is embarking on a data warehousing project. We are going to purchase a Windows 2003 server. It would be a dual processor. The specs are not certain yet so cannot give more details on that.
1. The data in the warehouse would be close to 150 GB. 2. There will be maximum of 10 users needs a SQL Server license. 3. Do not need analysis services.
What edition do I go with -Enterprise OR Standara? I want the least priced edition. I looked up the various links on Books Online but I am still not able to decide.
Say I need only 2 GB of RAM. Then here are my questions.
1. Since we are going with a dual-processor, do I need to purchase processor license for each of the two? Why can't I have one license on one processor only? What are the implications of this?
2. The 10 users that I am talking about will be remotely connecting to this Windows 2003 server and accessing the databae.
3. What exactly is Failover clustering? Do I really need it for my warehousing project?
4. Please help me pick the correct license. Here is the link -
Is there a way to find the SQL Server licensing information after the software is installed? I mean is there a way to say that it was licensed per cpu or per cal?
I have a Windows 2000 Operating System with 4 processor, out of which I'm planning to use only one Processor for the SQL Server and leave the rest of the three processor for the OS. My question is that do I need to buy the license for all the 4 processors or I can do with the only 1 that will be used for running the SQL?
I am a DBA and I have a SQL Server 2005 license for each server. To manage the servers, I want to install SQL Server 2005 on my local desktop. Do I need a license for it as well?
I have a three server network. One SQL Server, One Web Server, and a backup.
The web server is ASP.NET, and uses the database. I do not track the number of users hitting the web server.
What type of sql server license is needed? Processor? Device CAL? User CAL? I have read all the white papers and licensing info and can't find an aswer to this question.
What kind of license do I need to run a single web site on a web server that needs SQL server to operate? it's a public site that runs DotNetNuke but it's the only site on that box.
I am a DBA and I have a SQL Server 2005 license for each server. To manage the servers, I want to install SQL Server 2005 on my local desktop. Do I need a license for it as well?
I am a developer in need of setting up a SQL Server test environment for many users.
Can the Dev Edition be used as a back-end to handle this type of testing? Are my limited to one connection from my development machine?
As you can tell, <sarcastic tone>i am having a real fun time with this one</sarcastic tone>. Licensing terms are an area that i tried but sometimes cann't stay out of.
Hello, I am very confused about the licensing of SQL Server 2000 and 2005 (various editions), and any light you can shed will be greatly appreciated. I am learning VS2005, and need to build a website. 1. I know what a Client Access License (CAL) is. 2. I know what a processor license is. My ASP.NET website might have 10 users, 100, or maybe 1,000 (I don't know at this point).They will have anonymous access to a main page from which they will have to log in, and from that point on be using SSL for anything they do. I am getting conflicting information regarding licensing. Questions: 1. Can SQL Server 2005 Express support what I need to do? (possibly many users) 2. Other than some of the fancy replication, analysis, etc that Express does not have, is there a good reason not to use Express Edtion? 3. Regarding SQL Server 2000 or 2005 (NOT Express): Does a single web application act as a single user thus the web application requires only one CAL. In other words: I am the only person who has direct access to the database. The ASP.NET web application will also have access to parts of the database. Will this scenario count as 2 "CALs"?
In order to use Replication, sql server installation must use per seat licensing. What if I have per server licensing, how can I change the licensing to per seat so I can use replication Ahmed
I am so confused and I am getting no help from the Microsoft, two months and only stammering from their representatives. I need to set up a Sql Server database that will allow internet access. This is not an e-commerce situation. At most there will be 10 known users of this system accessing statistical data. I had priced this system to use Backoffice, but as I now read this is not legal for internet use. It also appears that a processor license is required for internet access (not entirely clear on this). Access and MSDE also don't appear to be legal for internet access. The customer is on a shoe string budget. If I use stand-alone components the budget only covers an one processor SQL Server 2000 license. I don't like the idea of setting up a database system with only one processor. Is there another Sql Server based option I am not aware of? Its looking like a linux/mysql option - Yikes!
Sorry in advance for the potentially boneheaded question: I would like to purchase SQL Svr 2005 Std Edition in a 2 proc licensing config. All my retailer has is 1proc and doesn't have answers for 2proc... Can I buy a 1proc and upgrade thru MSFT? If not, how do I buy a 2proc copy...? Thanks! JohnWoo
How do I tell what SQL licensing option (processor, device CALS or user CALS) was taken when the server was installed? I have taken over a SQL 2005 server and I would like to check how many CALS (if any) it is licensed for.
I have a SQL Server 2005 Standard per processor license (My server has a dual core processor). How many client machines can I install the SQL management studio so they can register the SQL Server and query data if need be?
I couldn't decide where in the forums to ask this question.. So I hope there's someone here who can help or you could suggest where I might go.
I have a client with around 5 standard PCs in the office. They want an application to run the business and are trying to decide if SQL Server or Access is the best way to go. My suggestion has been SQL Server, considering the plans they have for the business and the software. But their main issue is the cost.
They don't currently have a Windows Server... Just a bunch of shared drives on win XP which suits them well. Can anyone suggest the database configuration they should be going for? Minimising cost is their main issue and they don't want to go through the trouble of setting up a full windows server.
Are there licensing and legal issues to install one of the workstations with SQL Server Express with a VB.Net application running on potentially 2 machines?
I'm a little confused about the licensing of SQL Server 2005 Express Edition. I'd like to know whether:
Suppose I build a VB app which requires a centralised database, and I bundle SQL Server Express as the app's db engine, is this allowed in the licensing?
Suppose that the previous scenario is allowed, can my client opt to have me use the bundled SQL server express to be installed in my machine to host the database for him?
I apologise if this is not the right place to post this question. If that is the case, can someone point me out in the right direction? I have tried calling MS support lines, but they don't seem to know the answer as well.
Is this change possible without re-installing SQL 7.0? if so, how? The install was completed by a network guy who thought he knew enough about SQL and now I have to fix it, but all I know is that we use the per server mode in our company. Help Please!!!
Hello,Our company has developed several Access applications for our clientsand we wish to expand to use a database server. We wish to use Accessas the front end application and SQL Server 2005 as the back endDatabes Server. Making a Server-Client application database.I'm very new to SQL Server so my concern is how the licensing worksfor a developer like us. I am aware that we can purchase the Developeredition for $49 USD. Our clients will then have to purchase a theirrespective licensing option.We do not have an issue with this, but i would like a betterunderstanding of how this works.1) The developer edition (DE) is the same as the Enterprise edition.Would our clients have to buy the Enterprise edition ($24,999) if wedevelop the SQL server in the DE? Or can they purchase the Standardor Workgroup edition if the workload allows it?2) If the client already has the Enterprise Edition on the Server wewish to use, will they have to buy the license again if we create theDatabase? Can they import our Database to thier SQL Server, and ourapplication connects to thiers?3) Is there other options that would require a cheaper option for ourclients?4) With just the DE, can we develope applications and use theappropriate edition for our clients whatever it is?5) To test our products we thought of using the Trial version tosimulate a multi-user test environment? Since thats just a 180 daytrial, perhaps the Worgroup Edition or the Light weight Edition mightwork. But these editions might not be compatible with our clients'requirements. The DE doesn't seem to handle multi-user environments,so we cant effectively test how the application will perform in the"real world". Any advices here?Our clients range from small bussiness to nation-wide to multi-national companies.Thanks,- GL
I have 2 Windows 2003 r2 servers with a SQL failover cluster installed across the 2 node. Generally I have been running off node1 with node2 as the failover partner. I have purchased the correct licensing for noe1 and from the following I do not need to purchase a license for node2:
Failover clustering is a process where the operating system and SQL Server 2005 work together to provide availability in the event of an application failure, hardware failure, or operating-system error. Failover clustering provides hardware redundancy through a configuration in which critical resources are transferred automatically from a failing machine to an equally configured server to help ensure continuity of service.
When doing failover support, a server is designated as the passive server. The purpose of the passive server is to absorb the data and information held in another server that fails. A passive server does not need a license if the number of processors in the passive server is equal to or less than the number of processors in the active server. The passive server can take the duties of the active server for 30 days. Afterwards, it must be licensed accordingly
1) If I switch my cluster instace to point to node2 for testing node2 in case of a failover, would I need to purchase another licence ? This means I am not doing the repointing because of an 'event of an application failure, hardware failure, or operating-system error' ? Can you please provide information from MS ?
2) How are SQL Licences bound to the windows install in a SQL Server failover cluster configuration ? For instance if node1 legitimately fails due to an 'event of an application failure, hardware failure, or operating-system error' and you failover to node2. Then you think, stuff (forget about) node1 as I have 1 set of licences for SQL Enterprise already and therefore can run with a legitimate licence on node2. Can you please clarify ?
3) I have heard that only one server needs a license in a failover cluster. Then how does this fit in with any of the questions from above:
'The passive server can take the duties of the active server for 30 days. Afterwards, it must be licensed accordingly' ?
In the event of a legitimate failure, node2 would be running off the license purchased. So why are MS restricting the use of it for 30 days ?
I've recently purchased a number of SQL Server licenses, one was a single processor enterprise license with 2 years SA/Step-Up. The reason I purchased the SA/Step-up was that we plan to move to 2008 when it is released and I was given advice from our suppliers that the step-up would allow us to do this.
However, I've read a few things in the past few days that have made me questions this. Namely a comment that read: "SA Step Up is normally only used if you have for e.g. SQL Server Standard with SA and wish to turn it into SQL Enterprise..a completely different product"
What I'm now wondering is whether I've wasted money purchasing a step-up license. Can it be used to upgrade to 2008 when it is released? I'm going to buy another enterprise license shortly with the same upgrade intentions but if SA isn't going to help then I see no point buying it.
Could someone pl explain how is SQL Server mobile 2005 licensed. Do we need to buy license for each device ? or CAL?
In my app, I need a database which is accessed by .net compact framework app. synchronization is also done by our own app, no direct communication from sql server mobile to sql server db. we have a server side .net app which talks to the sql server and a windows mobile app which talks to the sql mobile db, these two .net apps talk to each other like:
sql server mobile db <--->.net compact framework app <--->.net desktop app <-->sql server 2005
Needless to say, there would be multiple devices having the above setup. However only one desktop side app and database. In this scenario, how would licensing be calculated?
