Quick licensing question...If I am developing an asp.net application using sql server 2005...what is the licensing situation? Do I need just the one CAL for the server with IIS that is hosting the application? or is it one CAL per database connection? One CAL for every person using my application? I'm not sure and I want to make sure that I comply with the licensing for my application. Thanks in advance!Phil
Is there a way to get Licensing information(product key) off an installed version of SQL Server 2005? Most Microsoft Software has the product key in the about dialog box, but SQL Server doesn't have this anywhere. Thanks,
I'm going crazy trying to find out the license deal for SQL Server 2000 Developer Edition. It seems that here (in the UK) the Developer edition exists and you can buy it but, Micrisoft (UK) and various resellers etc don't know the licensing deal!!!
Now, i've read a snippet somewhere about the developer edition that for a fixed price of around $499 you get a server license limited to 8 connections and you don't have to buy any CALs! However my reseller thinks that you still have to buy CALs up to maximum of 8? Well, i don't think so!!
We are about to deploy an application that uses SQL Server 7.0. Enterprise edition running on a dual processor machine. We expect a maximum concurrent usage of about 500 users, normally about 150/200. Could anyone advise me what the cheapest license arrangement would be, I've had conflicting views from Microsoft and two third party software suppliers? We intend to use the machine in future for other applications but as yet have very little idea of usage. Joe
Can any one please clear my confusion. when we install 2000 it always give option ofr licence (processor or per seat) but i installed 2005 couple of times but can' see any option in whole installation about type of licenscing. any one have any idea where and how to choose type of licence for SQL Server 2005.
Web Server = Windows 2003 Server Standard Edition running IIS
All the website hosted on this server will be available to the public.
Question 1.How do i licenses Windows 2003 Server Standard Edition? Question 2.Do i need a CAL for every single person browsing to any of the websites hosted on the above server. As far as i know you can not get a PER CPU license for Windows 2003 Server, is this true. Question 3. Where would a CAL be required. Question 4. How about remote desktop to the above server? that requires a CAL.
I know that I can have up to 2 GB RAM for the Standard Edition of SQLServer, but if I had two instances, can I have 2 GB per instance, say for 2instances which would equal 4 GB, or is it 2 GB for that installation of SQLServer and all of it's instances?Thanks.
Hello We have a sql server 2005 Enterprise Edition installed on one of our servers where we gor processor license. The question is can i install a second instance of Sql Server 2000 with out buying any extra licenses or should we buy licenses for this second instance seperately.
Obviously I'm missing something here (Like a brain??), but from the documentation I'm somewhat confused as to the licensing aspect of the everywhere edition.
Scenario: I have a client (small business for example) and I'm updeating their MS Access application, currently having the front and back ends seperate. May I substitute SQL Everywhere edition in place of the data back-end without further licensing, or will a CAL be required?
The company I work for has the latest MSDN subscription which has the SQL 2005 Standard edtion, as well as others, and I am trying to figure out what the license is for the SQL. I.E. Processor or what. Any help would be greatly appreciated.
I need to know if I have to buy an extra license for my subscriber server in the following two scenarios. I have checked similar threads in the forum but could not find an exact answer.
Scenario 1 :
Server A : Publisher - SQL Server 2005 Standard Edition.
Server B : Subscriber - SQL Server 2005 Standard Edition
Server B has ONLY the replica of one or more DBs of Server A
I have already purchased SQL Server processor license for Server A
Replication Type : Transaction Replication
Scenario 2 :
Server A : Publisher - SQL Server 2005 Standard Edition.
Server B : Subscriber - SQL Server 2005 Standard Edition
Server B has the replica of one or more DBs of Server A plus one or more operational (mostly reporting) DBs
I have already purchased SQL Server processor license for Server A
Hi...First, I am not sure whether I put this post correctly or not. My issue is I developed one simple web application with using ASP.Net 2.0, VB 2005 and SQL express. I wonder that if i install it to my customer's pc, do they need to pay for SQL express's licensing since it is free now.. Thanks in advance.Regards, Anson
The MSDE licence says that it can be used for up to 5 concurrent users. My app is an ASP.NET app, so won't I just be using one user - the ASP.NET account? I'm wondering whether we can get away with just buying a new server and sticking MSDE on it rather than shelling out for another £5000 SQL server licence...
I expected to find loads of posts regarding licensing but surprising not.
I have SQL Server Developer Edition, which I believe gives me the right to build and distribute applications which use MSDE (http://www.microsoft.com/sql/msde/howtobuy/msdeuse.asp).
Is there any requirement for the end user to purchase any microsoft product or license?
Hello all, I did explore the archives on this one, but could'nt find anything that closely matched my issue. I'm running SQL 7.0 Server (Desktop version) on my laptop and when I try to use DTS to transfer data from a SQL Server 7.0 running on NT Server 4.0 in the SAME NT domain. The error I get says that the licensing arrangement I have does not permit me to use DTS.
Does SQL 2000 standard edition support replication if it would be configured as a subscriber. Is SQL 2000 Enterprise Edition required for a Publisher and Distributor or can you get away with standard edition. In a web site environment how many CALs are needed when users access the database via webservers and middleware.
I've got 5 user licensing with MS SQL Server 7. I would like to know does the licensing refer to the connection with SQL Server. I've developed an application using VB which have multiple connection (more then 5) with SQL Server. Will there be any problem?
I have a laptop that currently runs Windows 98. I have loaded SQL Server 7.0 Desktop Edition onto this computer. I am getting a DTS licensing error when I attempt to transform data using DTS between remote SQL Servers. The only workaround I have found is to create a DTS package and perform the transformations using transfer manager. This works for me now, but I am wondering how I might go about solving this license problem. It is my belief that a demo version of SQL server 7.0 might have existed on this machine long before I loaded my installation. If this is the case, how can I straighten out the registry to fix my licensing problem?
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 ?
I have an SMS 2.0 site set up on one server and SQL 7.0 installed on another server. I have 288 users and have 288 SMS client license and one SMS server license. My question is do I need to have client access licenses for my 288 users for SQL or is the SQL 7.0 licenses included in the SMS package as long as I only use SQL for SMS?
Also does anyone know if SQL 7.0 ask for the number of license that I have during the installation process?
I would appreciate any input anyone may have on this.
I know that PerSeat is each individual computer that accesses SQL Server and PerServer is the number of concurrent connections to the server. Is Client Access Licenses the same as PerSeat?
At installation I erred in specifying per seat licensing when the server I'm working on is actually a per processor license. Can I change this or must I reinstall SQL 2K?
At installation I erred in specifying per seat licensing when the server I'm working on is actually a per processor license. Can I change this or must I reinstall SQL 2K?
I have three heavy duty servers with 32-bit dual P4 CPUs, 4GB RAM, SCSI boot drive, fibrechannel RAID (40+ spindle).
I want to purchase SQL Server licenses for these machines. SQL Server 2000 standard edition seems perfect except it only supports 2GB of RAM and from my understanding, to utiliize the /3GB switch in boot.ini, you need to use Enterprise Edition. You use AWE if you have more than 4GB (which we currently don't).
Is there any way to get standard edition to use a full 3GB? Anyone know what kind of upgrade path will be provided from SQL Server 2000 to SQL Server 2005 licenses? Will SQL Server 2005 Standard Edition utilize 3-4GB of RAM?
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?
We recently purchased Stockamp's Clinic Ontrac system. The system has a built in crystal reports viewer module with capability to add our own reports... The backend of the product is SQL Server. To create a report you have to potentially create a stored procedure - if parameter is needed - and a crystal report. Stockamp is requesting that we have written approval of these reports as well as any ad-hoc reports and queries that we run before we run them in the production environment.
I'm used to large vendors (those that understand a database is only as good as the data you get out of it) and I've never seen a license agreement like this before. Is this common?