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?
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
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?
I'm getting some conflicting information , regarding sql 2005 Standard Edition licensing for multi instancing.
If you have multiple instances of SQL 2005 Standard Edition on one Server, do you need to pay a server license for every Instance or just the one Server license?
Jack Vamvas -------------------- Search IT jobs from multiple sources- http://www.ITjobfeed.com
I hope this is in the right forum, I'm new to MSDN. I'm also not an expert in SQL, so please bear with me as I was unable to find an answer by searching the archives.
We have a single SQL 2005 Standard installation with 30 user CALs on a Server2003R2 box. We have another Server 2003 box in a remote but connected location that we previously used for backup replication. What we'd like to do is use some of the replication features in SQL 2005 to replicate the data over every night to the other box, onto which we would install another copy of SQL 2005. This would not be a server accessed by clients, but simply a "live backup", that in the event of a catastrophic failure, could be manually set up to operate as a SQL server in place of the failed primary server. I don't need any kind of automatic "failover", just the ability to replicate the data over to the other system so I have two SQL Servers that synchronize from one to the other overnight.
I was told that I wouldn't need to buy the user CALs again, that the 30 user cals would translate over if the primary server fails and has to be replaced by the cloned server. But what do I buy for the SQL server itself? A boxed version is a bit pricy and comes with 5 CALs which apparently I wouldn't need. Then I noticed that on softwaremedia.com the open license version, which can be bought a la carte, lists a requirement of buying at least 5 cals or a processor license. What exactly do I need to do this, and how can I get it for the least amount of further spending?
I handle all licensing for our companies. I am trying to completely understand the licensing and want to insure if I approve the installation of Mgmt Studio 2005, that it is covered by SQL Developer licenses?
Hi Experts, Can you tell me the procedure how to install SQL Server 2005 Standard Edition with CAL licensing? This is very very urgent, Your help would be appreciated..
I have two question with respect to the developer edition licensing in SQL Server 2000 and 2005:
Question 1 I wanted to install a developer edition on a Development/Test Server. The server needs to be accessed by our development and Testing team of a team of 20 from their workstations. Is that possible?
Question 2 And if so what are the different licensing options that I can choose from considering that I don't want to install a developer edition of sql server on each workstation? The developer edition will be installed on the Dev/Test Server and the workstations will connect to the server using NT or Standard authentication.
I have one server hosting an ASP.NET application. It will be running 2005 Standard Edition.
I don't really understand which licensing model I need. Obviously processor licensing would work, but at a hefty price!
The web application and SQL Server are on the same machine, and no other machines will be querying the database. The only 'users' are the people who visit the website (both internal and external users).
Can someone help me properly determine the most cost efficient licening model to use?
I attended one of the SQL Server 2005 "Ready to Launch" parties a couple of years ago and was given a complimentary SQL Server Standard Edition CAL along with a copy of the SQL Server 2005 Standard setup DVD.
As there's no mention in the "Ready to Launch" pack of an included Server license I was wondering whether it is possible to install a copy of SQL Server 2005 on a standalone server and use the single CAL in a Production environment without having to purchase a Server license? The pack does include a Product Key - is this the Server license?
I have a VERY Legitmate use to install sql 4 workgroups on a pc without licensing it. I am making a disk image for MANY pcs to be imaged and load licensing after the imaging is completed.
I have been able to do this with Windows XP Professional, MS Office 2003 and a couple non-Ms programs. The information for MS software even came from their KB, so I know what I am doing is legit. I just can't find any information on doing this for my sql app.
Currently Project managing deployment of a lightwieght asp.net web app, and have a web server in a dmz and a database app server behind corporate firewall. The app is to be used by external internet users and is accessed through the web apps authentication. Currently have sql 2005 standard processor licence on the db server.
At present RS is deployed on the main db app server however it is not accessible to the external world as corporate IT advise this is a security risk. Fair enough. They advise I need ot install RS and sql licence on web server to get this to work.
However will I now need to buy a processor licence to enable RS to run on the web server? there was an interesting thread posted below on the deployment of RS. I think if you install Report Manager on separate server (the dmz web server) then you do not need to purchase more SQL licenses? the EULA indicated this but its not crystal clear.
The report manager is a asp.net web app just 'ike the main application. Is it not feasible to install report manager on the web app and then have this talk back to the report server on the main db application?
is Report Server installed with Report Manager regardless, and even if you deploy it separately you still have to pay!
I have a rather complicated SQL Licensing question which i am looking for a simplified answer to. My current production environment consists of a dual CPU W2K3 SQL 2000 ent. as the primary transactional server and a quad itanium W2K3 running 64bit SQL 2000 ent as a backup reporting server. I am currently working on a project that will expose these servers to users outside of our firewall (read only non-transactional) and our desire is not to upgrade to SQL 2005 at this time. In additon, the primary server will be accessed from 7am to 9pm and then a switch over to the backup from 9pm to 11pm as the primary will be unavilable due to maintenance. If I interpret SQL 2005 Licensing correctly we would need a per-processor liscense, either standard or enterprise depending on the features utilized. Since we are only doing log shipping from the primary to secondary server my assumption is to purchase SQL 2005 Standard per-processor licensing for both servers?
Hello all, Never had to set up a server before and am bewildered by the licensing speak. I'm going to have 1 small server (probably with 1 quad core processor) with 1 instance of SQL server running on it. The same server will host an intranet site through which all users will access the data. What kind of licensing set up is required for this?
We have installed SQL Server 2005 Standard Edition 64-bit on our Windows 2003 server. Now we have the server and CAL license in hand and want to add those licenses to SQL 2005. Tried using Control Panel License but SQL 2005 is not there. Can someone help us, how we can add the SQL Server and xx number of CAL licenses to SQL 2005. Thanks.
I have a client that has a licensed SQL 2005 environment running on a commercial site. I need to install SQL 2000 as well to support a piece of software that does not run on SQL 2005. The client believes that their license covers them to run both versions of the software - is this correct?
If so, they no longer have the install set for SQL 2000 so is there somewhere I can get this from? I work for a Microsoft partner so we have our MSDN version of SQL 2000 but I suspect that would not work with the clients key?
Unfortunately the client is in a different country so it's not easy to just try it and see.
I am having a nightmare getting an answer about what type of licensing I will need for the standard addition of SQL Server 2005 for my asp.net application and wonder if anyone has any advice. As I see it its very simple, I have a web app that makes a connection to SQL via a connection string using a single username and password, no impersonation just straight SQL authentication. For this simple scenario I figured I would need to get a SQL 2005 license and then 1 Client access license (CAL), this being a nice affordable way of doing things BUT I am being told by different sources, that I may need to license on a per processor basis as any user of my web application, anonymous or otherwise needs a client access license and given that I don’t know how many users are going to access my website I would need to go for the larger outlay and purchase two standard processor license (my sql server is a dual processor machine). Can anyone tell me if this is the case, is a connection from a ASP.Net website to a SQL server for my website visitors regarded as a new client and therefore needs a client access license or the large investment of a per processor license? I would stick with SQL Express but at 4gigs max it won’t do the job. Thanks in advance.
A rather dumb question but I've installed an evaluation copy of SQL 2005 on my machine and a colleague would like the Analysis Services Data Mining capability on his machine (without the eval SQL Server).
Is there a license associated with such an installation when we buy 2005 or does it fall under client components which can be installed on any number of users machines?
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 all, 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.
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