We are looking to purchase a new SQL2000 server.... Tada.... Right then, for around about the same money, we could have either 2 x PIII 1Ghz Xeon with 256Kb cache, or 2 x PIII 700Mhz Xeon with 1Mb cache.... Which choice is best for SQL Server 2000???
"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).
How should I know if I need to add new processor to my Server?
During Submission of our Records every 24th day of the month the cpu usage of the server is steady 100% can you please help me what alternative can I do? or how can i check if need to add new processor.
I have a rather intensive load on a server that has a data mapping application on the same server(I know this is a no no but I didn't have a say). It seems to be maxing the CPU. Is there a way on a dual or quad processor machine to tell SQL Server to only use one of the processors?
I was wondering, is there a way to allocate processors to SQL2000. I have a server that has 4 processors, I would like to leave one just for the operating system and have SQL2000 use the other 3. Is this possible and do you think it would be recomended to do this? Or should i just leave the 4 processors for everything?
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....
Has anyone ever upgraded the processors in their SQL Servers? Like shut it down, swaped out the processors with new ones, and turned it back on. Assuming the OS boots fine, is there any issues with SQL Server now its suddenly running on new hardware?
I have to assume that this is not that uncommon of an activity, and the OS and SQL Server should be fine.
Basically we are contemplating upgrading our quad processor (Xeon Cranford's) with four dual cores.
I have an SQL2000 server running on a 4-cpu 4 GB Win2003 system withhyperthreading. The batch is running on only one virtual processor. Iwould like to utilize all the processors in parallell in order tospeed up the batch. How ?
In the processor licensing mode a license is required for each physicalor virtual processor like explained inhttp://www.microsoft.com/sql/howtobuy/default.mspx->But what about dual core processor?->And what about clustering? (if a user install 2 server in cluster mode)tnx
I know this won't be a lot to go on but, we has a quad processor box that is doing a lot of sql crunching. When we turn off three of the processors it runs the SQL queries faster. The requests are comming from COM objects. CPU, Memory, page faults, all that stuff is fine. Also SQL dosen't appear to be using all the processors as only 1 has any amount of usage?. Any suggestions of where to start would be most appreaciated.
Has anyone seen a problem where a SQL Server Application works on a server with a single Processor, However when placed on a box with multi-processors it fails. You do not receive any errors but the data set that is returned is not correct. When reviewing this problem on a test machine that only is a single processor we can not duplicate it. The Production Box is Multi Processor 2 pentium pro 200's with SQL Server 7.0 and no Service Packs. My Question is has any one ever seen this problem, and would installing the SP correct it, I plan on installing the SP's but I wonder if this could be the cause of the problem.
Hi, I have a new problem .I have a DB on server which is using only one processor and it keeps using up all memory on server. Any thoughts appreciated! TIA PD
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.
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?
We are in process of moving to 64 bit HP servers with sql2005 standard edition. We were just wondering which is better option, to get a server with 2 dual core processor or to get a srver with just 4 processor? How does SQL2005 handle the hypertheading of dual processor?
I have noticed that when using SQL Query Analyzer some of my queries will use 100% CPU on my PC and next to nothing on the SQL server, while other Queries require 100% CPU on SQL server and do next to nothing on my PC. Does anyone know what determines this??
Right now I can produce this by executing two very similar T-SQL selects. The one that runs on the server only has one additional join - a very simply join at that. If I can change my SQL to make it run client side in some situations, that would be VERY HELPFUL!
(1) When I was monitoring the SystemProcessor Queue locally ( Via a term server login onto the box ) I would see a queue of 3-4. If I monitor the same parameter from a remote PC, I see a Processor Queue of 1 - why? The box had 1 GB RAM ( SQL used 500 MB and had 250 MB free according to Task manager ).
(2) I have another almost identical box that has same CPU but twice ammount of RAM ( 2 GB ) but has SystemProcessor Queue of almost 0 - why?
I have a data mining app that does a series of select statements (no inserts). I'm noticing an odd occurance where if I start up 4 copies of the app on a quad core machine - sql takes full advantage of the 4 cores for a few minutes and then drops to 75% utilization - the other 25% is on the idle process. Two of the apps appear to be sharing a single proc of sql as each of their throughputs is cut by 50%. If I then start a 5th copy of the app, the machine is brought to full 100% utilization - two of the apps continue to appear to share a proc. SQL is set up to use all procs and I have even tried select the priority boost to no effect.
Any ideas how to ensure full sql utilization with the same number of apps as cores?
Hi, Ive been told this, but I hope it is NOT true. I have an sqlserver2000 installation running on a server that has four processors.It is on a active network but is not the domain controller soessentially it is fully dedicated to servicing the needs of sqlserver, (a bit of browsing, a bit of ms Office, but almost whollydedicated to sqlserver. Now, the big question, why, when the serverproperties have been set to utilize all four processors, can any onejob never get more than 25% of cpu time? I can launch multipleinstance of QA and run the same job on each one and that will utilisemore and more cpu time, but if you launch multile QA windows fromwithin one insance of QA, you can NEVER get more than 25% CPUutilisation. Now i have to run a job (FTS is a good example,re-indexing lots of db's another, or even a huge query with multipleufd's on computed cols which I hoped would grab lots of CPU time thatthey need, but no. So do I have to live with this or can I tell eitherwindows or sql server to grab more cpu when it want to ie use my spareCPU capacity more efficiently or am i working on a misguided premiseand 25% per job is your lot?DMAC
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.
Is SQL Everywhere supporting for Windows CE 4.2, Windows CE 5.0? What processors are supported by SQL Everywhere? Now we are using RC1 version SQL everywhere and when Release builds will be available? What is the purpose of the following SQL everywhere runtime binary dlls. · Sqlceca30.dll · Sqlcecompact30.dll · Sqlceer30en.dll · Sqlceme30.dll · Sqlceoledb30.dll · Sqlceqp30.dll · Sqlcese30.dll · System.Data.SqlServerCe.dll Thanks, Rajendran.
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.
I was hoping someone out there can give me some direction on some performance issues I've been having with SQL Server 2005. I have two SQL Servers instances configured almost identically (or so it seems) on two different machines.
I have a certain data process initiated from a database aplication that is giving me two different results depending on which sever processes it. One of my servers is taking considerable more processor time and effort than the other running at 100% utilization for a long period of time. I have double checked the settings on both SQL Server instances and there are very few differences. The Maximum worker threads on the poor one is set to 1024 while the better server is set to automatic (0). That is the only differnce I have found in the settings of these two servers and it's my understanding that I should not see a huge performance difference due to this setting.
I'm a bit at my wits end here and really need some more ideas at what other factors that I am not taking into account could effect Processor utilization.
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.
I have a server with little control over most of the codeset and db design. Recently I have seen both the Processor - %Processor time and Processor - % User time go fom about 6.3 to about 24.3. The system queue length has also gone from about .2 to 1.1. In my humble opinion both of the are signs of a problem coming (luckily the cache hit ratio is still sitting at about 99%). I have been running profiler to catch the things that take more that 4500 MS, and I can probably tie the 2 together. Any opinions, or real world comparisons appreciated
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 ?
Howdy all. I have a query with bizarre results in Query Analyzer.
Box1; 4 x 3.0 processors, 4 gigs of RAM. Results never come back. Box2; 8 x 3.0 processors, 16 gigs of RAM. Results never come back.
Both of the above boxes are extremely under utilized. The absolute max amount of CPU being used is 25%. Box1 had 1 gig free RAM and Box2 had 7 gigs free RAM.
Box3; 1 x 3.0 processor, 1 gig of RAM. Results in 15 seconds. Box4, all the same as box 3.
I took a backup of the DB and restored it from box to box to box, so I know everything is identical.
I once had a deadlock issue where I had to use the maxDop hint and tried that here, but it didn't help.