If I install an instance of SQL Server on a box with 4 processors but specify in the licensing part of the installation procedure that it's a '2 processor license', does that really mean that SQL Server will only use 2 of the 4 processors? I ask because, having done this, if I check the SQL Server instance's properties, on the Processors tab, there are 4 processors ticked - giving the impression that 4 processors are being used by this SQL Server instance. Can anyone throw some light on this?
Another question... If I wish to reconfigure the same SQL Server instance from a 2 to a 4 processor 'per processor' license, how can this be done?
Does it mean "per hard drive" or "per CPU"(Pentium III, Pentium IV, etc.)? I'm a bit confused about it after reading a lot of books and article talking about processor license. Thanks in advance....
I recently completed developping my own e-Commerce model using SQL Server 2000 on Windows XP Pro .
However, now that I have it running smoothly, I would like to transfer the files to a dual Xeon 1.7 Ghz system with Windows Server 2003 with SQL Server installed for commercial use. I looked at the prices, and I was shocked to see a processor license for SQL server to be $5,000 to $20,000!
License Prices
I have a few questions comparing the free MSDE to actually purchasing a server license:
1. I undestand that MSDE limits the concurrent queries to 25 at a time... is that sufficient for a site that has say 500 visitors a day, who make 10-20 queries each? What about 1000 or 5000 visitors?
2. When the MSDE query manager detects too many queries, does it queue queries to resolve sequentially automatically? Or, does it just FAIL if there are too many queries? I'd hope that it would queue the query so that I don't have to go through my source and re-program each query to re-try in this case.
3. Is the 2GB database size limit of any concern on an ongoing basis? Seems to me that is more than enough as long as I erase some tables every few years.
If anyone has had experience with either/or system, I appreciate your advice.
We have an active database that sits on SQL Server 2000 that currently has per seat license...but now want to switch to per processor. If I go to ControlSQL Server 2000 License Set up...it doe not give me the option to choose per processor.
Do I need to un-install/re-install SQL Server 2000 and choose the per processor choice and then re-attach our database ?
I currently have a single proc server in production and want to maintain a spare server that is dual-proc.
Is there a technical problem installing a single license SQL 2000 Standard on a dual-proc server? WIll it allow it or is it actually just a legal licensing requirement?
I need to upgrade a solution from SQL Express Advanced to Workgroup Edition because of the 4GB size limit. I'm planning on deploying the solution in an secure web enviroment were only authenticated users will be able to access the database. The actual username's and passwords would be stored in an Express database. Therefore since only named users would be accessing the database server web app, can I use the CAL license model??
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.
I've just updated my databases to V7.0 from 6.5. I am having some issues with CPU utilization after rebuilding the databases. I rebuilt the databases from scripts after modifying the scripts to deal with any SQL issues between the versions.
Symptoms:
When a bunch of stored procedures are executed the % Processor Time his 100% on a single processor system, the Processor Queue Length hits 13, the Batch Request/Sec starts at 20 and rises to 47 before dropping off, Context Switches go from 370/sec to about 833/sec before dropping off and there is an increase in page faulting.
My testing was done on a single processor but my real system is dual-300+ with 128Mb RAM. The database is only 40Mb and after running the index wizard there were no changes advised.
After reading a lot in help areas for MS and here I am not sure if this has to do with how SQL Server runs now (i.e. system configuration) or if it is a query issue with parallelism. I'm assuming query parallelism since the performance spikes occur when stored procedures are run. On a single processor is there a way to address this. Then, hopefully, I can deal with the real multiprocessor system.
Every once in a while (every couple weeks or so) one of our SQL Server 2005 servers will have its performance take a dive. Response time on applications will slow way down. In checking €˜Task Manager€™ the CPU utilization will be up to 50 to 70 percent for the SQL server service. We have tried looking at €˜Perf Mon€™ there doesn€™t seem to be any consistent performance item that is out of whack. On occasion, it may appear to be a lot of paging going on, but I don€™t know what application is causing it. We€™ve looked at SP_who2 to see if there are any blocks, but there do not appear to be any. Though on occasion we will see a €˜Killed/roll-back€™ entry on €˜SP_who2€™ that has a lot of CPU cycles that, at least at one point in time, had a lot of counts against it.
In looking at a trace that we have set up, we don€™t see anything glaring that is held up or even a recurring theme (application) on the list that would point to a problem.
We find that by restarting the SQL Server service, this resolves the issue for another couple of weeks.
Is there something that I can look at that would tell me at least, what PC name is doing all of the IO against the database. I could then at least call the user and say €˜Hey, what are you doing€™ so that we can start to narrow down what is going on.
Regarding Standard vs Enterprise processor usage, I have read the SQL2K5 edition comparison articles that MS puts out, but I recently viewed a webcast that gave me cause for concern.
There was a webcast called "Selecting the Right SQL Server 2005 Edition", hosted by Michael Raheem, where he stated that although Standard edition allowed 4 processors (based on sockets, not cores) some index operations only leveraged one core at a time. So even if you have, let's say, 4 dual core CPUs (= 8 processor cores), only one core at a time will be used, and the rest will be idle during that operation.
Can anyone give a better idea of which operations are full multi-core in SQL Standard. Michael mentions indexing - does that mean strictly explicit reindexing operations which are part of a maintenance routine, or does that apply to index operations during normal inserts and/or updates?
We will be using this to run a backend for a commercial website, and we need to be sure whether we can get by with Standard or we need to make the investment in Enterprise.
Hi everyone, Primary platform is 2005 under 64-bit.
I'm trying to figure out what does 'Processor Affinity' and 'I/O Affinity' means when you're viewing server properties. We've got eight processors. Thanks for your comments,
I was browsing Microsoft's SQL Server site, looking forsome details about SQL Server 2005. Didn't find whatI was looking for...I'm thinking about moving an existing SQL Server 2000workload to a new box, using SQL Server 2005, andmaybe the 64-bit version.My questions are:1. What is the current target date for release of SQL Server 2005?Will 64-bit ship when 32-bit ships?2. Will 64-bit SQL Server 2005 require a special versionof Windows Server 2003 (e.g. Windows Server 2003 Enterprise x64)?Will it work with both Intel and AMD processors?3. How many CPUs, and how much memory, will be supported bySQL Server 2005, 32-bit and 64-bit, on each OS that can runSQL Server 2005.I'm looking for a chart here, something like the chart onpage 117 of Kalen Delaney's "Inside SQL Server 2000" book.SQL Server 2005 SQL Server 2005Feature Enterprise 32-bit Enterprise 64-bit------------------- ----------------- -----------------CPUs supportedWin Srvr 2003:Win Srvr 2003 Adv:Win Srvr 2003 Ent x64:Physical memorysupportedWin Srvr 2003:Win Srvr 2003 Adv:Win Srvr 2003 Ent x64:Has Microsoft published this info, and I just can find it?
We have recently tested upgrading our web service from sql 2000 to 2005 sp1. The upgrade went smoothly enough, however we now have the problem of the sqlserver.exe process taking 90-100 % of the processors time, but using only 100 MB of memory.
We have 6GB available and we are running the enterprise editions of Windows 2003 and SQL 2005.
Machine specs,
DL380 G2, 2 X 2.8 Ghz Zeon, 6GB ram, Raid 5, database partition of 140 GB, Log partition of 35 GB.
Db is 25 GB, Log is 12 GB. Largest table has 32 million rows.
We are seeing that the %Processor Time for the sqlservr process in Perfmon is over 100%. I am trying to understand how can the percentage of use be over 100%, and why it is over 100%. Someone told me that if the machine has multiple processors, that it will be over 100%. If that is the case, how can I determine what the maximum and normal values are? If I have 4 processors, does that mean 400% is the max? Does not make sense since it is suppose to be a percentage value...
Could someone explain to me how the CPU Utilization value is being measured, and if it is going over 100%, why that is and how I can determine what the threshold should be for monitoring?
This is weird situation for me as i can access my database server from 32- bit processor and its working fine but when i try to connect through 64 bit processor it throws the following error : Please help. I am using enterprise library january 2006 to access database.
An Error has occured while stablishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow Remote Connections . (provider : Named Pipes provider,error: 40 - Could not open a connection to SQL Server)
Hi everybody, I have a mirroring set up for around 30 databases in a 64 bit - 2 powerfull servers scenario - wih latest sp2 + hotfix. Mirroring works perfectly most of the times but when the principal is getting busy during the busy period of the day all of a sudden the processor on the mirror jumps to 100% and stays there for a long time - there are no live databases on the mirror server - all the databases are in mirrored mode. The principal server processor is less than 5% all the time. The network load between the principal and the mirror is also in normal limits. The principal server is dedicated to SQL but the mirror has other things too but the other processes use up maximum 15-20% of the CPU and when I stop SQL Server in one of those moments when the CPU jumps to 100% everything comes back to normal so it's clear that the issue is SQL on the mirror. Any ideas would be greatly appreciated.
I am looking at running SQL Server 2005 Standard Edition in a clustered environment (2 nodes) and am not sure if the 4 processor limit applies to the number of processors per node or the number of processors it will run on in the entire cluster. Could someone please clarify this for me?
"Error: 8624, Severity: 16, State: 1 Internal Query Processor Error: The query processor could not produce a query plan. For more information, contact Customer Support Services."
I have traced this to an insert statement that executes as part of a stored procedure.
INSERT INTO ledger (journal__id, account__id,account_recv_info__id,amount)
There is also an auto-increment column called id. There are FK contraints on all of the columns ending in "__id". I have found that if I remove the contraint on account__id the procedure will execute without error. None of the other constraints seem to make a difference. Of course I don't want to remove this key because it is important to the database integrity and should not be causing problems, but apparently it confuses the optimizer.
Also, the strange thing is that I can get the procedure to execute without error when I run it directly through management studio, but I receive the error when executing from .NET code or anything using ODBC (Access).
Hi all,I am performing a consolidation of all SQL servers in my environment. Ihave run the tool to find out what level patching they have and whatedition they are running on, but is there a tool so I can scan thenetwork and find out what licensing they are setup for (processor vs.seat)?Even if I have to enumerate each one, one at a time I would be OK withthat. I just don't want to have to login to each server and go toControl Panel and click on the Licensing.Command line is super-duper.Thanks,Josh
Hi, We have MSDN subscription and got VS2005 and SQLServer2005. Our developer develops applications bey using them. One of the application that he has runs periodically and export data from SQLServer2005 to xml files in development machine. We are wondering if we need to buy SQLServer 2005 license for this process. Thanks for your help.
I have a unique problem while connecting to oracle source with a 64 bit processor. I can connect to the oracle from the command prompt in the 64 bit processor but not from SSIS.
The acutal problem is, when check the properties of the connection manager and provide a provider for oracle, and then provide username and password and click on test connection. I get the following error:
"Test Connection failed because of an error in initializing provider.ORA-06413: Connection not open"
Hello.After searching Microsoft's website for hours and confusing myself morethan I was before I started...Can anyone explain to me what the current state of affairs is for SQL2000 licensing?In particular with a server that has multiple processors and multipleinstances of SQL Server 2000 running - for both Standard and EnterpriseEditions of SQL Server 2000.Please help!Regards,Taz
Today many applications (SAP, SIEBEL, MANUGISTICS, PEOPLESOFT, and soon) does not have a client direct access to connect to the database.They use an Application Server that has only one connection to thedatabase and the users get connected to this application server.THE QUESTION: How to control SQL Server User License in this new model,automatically?You cannot enable SQL Server Audit because users are not connecteddirectly to the database.You cannot use Identity Management applications because they do notwork on NOT Enterprise Business software.How to do that if you have hundred of applications and database?Regards,Marcio
We have a .NET Remoting application whose "server instance" connects to SQL Server Express and send data via remoting to its client application. There is no need for other direct access to SQL Server except for the "server instance". Now my software vender advices us to upgrade to SQL Server WorkGroup edition and now we are facing the question which license to buy. Could you advice us?
