I have two production SQL Servers and a separate server as a
distributor (merge replication). The two production servers are
licensed by device cals. Does the distribution server require the same
cal licenses as the production ones or can I save on cals by assuming
that only the agents will connect to this server?
If I create a Window's application that uses a MS Sql Server DB created with the express edition, do I need to get permission or submit royalties for distribution of my application? If so, where can I find the required info? I have been Googling without success and want to understand what is involved.
My projects are mostly for fun and my own amazement at this point, but I thinking about creating something that may actually become a product and need some guidance before I get much further along with it.
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
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.
I have set up replication on two SQL Servers (6.5), SP5a, on NT 4.0 (SP3). The Distribution Task on the Publisher is failing with the following error:
08001[Microsoft][ODBC SQL Server Driver][dbnmpntw]Specified SQL Server not found.
I am using standard security in a workgroup environment. I have my trusted connection setup and I am using named pipes. I had this process working on our test servers but when I tried to implement it into production I received the above message. Please give me some ideas or things to try. What source can I use to look up the 08001 error?
We are attempting to rollout a name and address system to 10,000 users who will use an application connected to an MSDE database.
We are using transactional replication to distribute data updates to them. Clients are connecting via the On-Idle feature of Synchronization Manager to grab transactions.
Server spec: Network card: 1GB Processors: 2* Xeon 3.2Ghz Server spec: DL380 2Gb memory Concurrent connections set to: 600 Disc: RAID 10 with 6400 controller
We are not using hyper-threading.
So far we have rolled the system out to 3500 subscribers, 500 per day.
Each day a subsciber will receive at least 400 transactions and 5000 commands.
Latency is 6 seconds, delivery rate 180 commands per second at less busy times. Latency is 14 seconds, delivery rate 127 commands a second at busy times.
I have seen it get as slow as 0.04 commands a seconds at busy times.
The server becomes incredibly slow when there are more than 50 concurrent connections.
We are seeing 100 CPU for most of the day as clients connect to the distributor at various times. Lunchtime is particularly busy when people go to lunch, leaving their machines idle. We see lots of "time-outs" and "unable to connect to distributor" messages on the replication monitor during peak times.
What can we do to improve the performance of the distribution server?
Are we being over-ambitious by selection SQL Replication for this scenario?
Is there a way to move the Distribution database (that is currently on the publisher server) to a different server without having to reync the subscriptions.
Hi, what is the distribution fee for SQL Server 2005 Desktop Engine distribution? Where can I find this information? I don't need it for development only for distribution.
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!!!