May 14, 2003 at 8:42 am
I am seeing tons of events in the Application log that say "Event log - 17052 : This SQL Server has been optimized for 8 concurrent queries. This limit has been exceeded by 2 queries and performance may be adversely affected. "
This only started happening a few days ago and I have noticed a degradation in performance.
Any ideas on what may be causing this or how to remedy?
Thanks!
May 14, 2003 at 9:02 am
Which version of SQL Server and service pack you are running?
May 14, 2003 at 9:04 am
Microsoft SQL Server 2000 8.00.760 (SP3)
May 14, 2003 at 9:37 am
Is this MSDE? Can you give the whole output of SELECT @@version?
Steve Jones
May 14, 2003 at 10:03 am
Sure can!
Microsoft SQL Server 2000 - 8.00.760 (Intel X86) Dec 17 2002 14:22:05 Copyright (c) 1988-2003 Microsoft Corporation Personal Edition on Windows NT 5.0 (Build 2195: Service Pack 3)
May 14, 2003 at 11:30 am
This is personal, i.e. a desktop edition. It is not for lots of people to connect to and run queries. It's mainly for developers working on their machine.
You need to install the standard or enterprise edition if you need more connections running at once.
Steve Jones
May 14, 2003 at 3:56 pm
Thanks for the suggestion! I am looking into what it will take for us to get Standard Edition installed.
Thanks again!!
January 7, 2008 at 11:40 am
I am getting the limitation as well with the version Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005 23:18:38 Copyright (c) 1988-2003 Microsoft Corporation Personal Edition on Windows NT 5.2 (Build 3790: Service Pack 2).
Should I install the Enterprise edition as well?
Performance on my machine and others are poor. It takes me 1 and a half minutes after starting my VB application, which connects to the SQL server.
January 8, 2008 at 5:28 am
A production server should ideally have the Enterprise edition of SQL Server installed. The Personal edition is primarily used for development work.
January 8, 2008 at 8:50 am
I thought personal edition wasn't licensed for server installs. I'd highly recommend you move to standard ro enterprise. detach the databases, script the logins (sp_help_revlogin) and then uninstall personal.
January 8, 2008 at 9:14 am
Are there procedures to follow when uninstalling the Personal edition and then installing the Enterprise edition?
January 8, 2008 at 9:24 am
You might try googling for a more comprehensive step-by-step instructions, but two things that you might come across:
1. If you try installing EE and find that it only allows you to install it as an instance, then you will need to edit the registry;
2. When intalling EE, please make sure that the correct collation is selected, otherwise you will need to rebuild master;
Paul
January 8, 2008 at 2:26 pm
We have a disk in house that says MS SQL Server 2000 Standard Edition (Reporting Services) - is this the correct version of the Standard Edition?
August 21, 2008 at 12:50 am
hello
i have Sql enterprise v8.0 and i have same problem.
yesterday ,the sql server didn`t respond and all my program stoped.
in the event viewer this error genereted.
This SQL Server has been optimized for 8 concurrent queries. This limit has been exceeded by 91eries and performance may be adversely affected. "
please help.
December 22, 2008 at 1:01 am
@SSChampion
Well i am a .NET developer any i am testing my application on SQL Server 2000 PE, i am also facing the same problem of concurrent queries. I have read the article on msdn regarding WorkLoad Governor as well. What i have been able to understand is that there is only a delay before each logical read/write. What i want to ask is that is there any chance of queries to be missing in this case? Means, when WorkLoad Governor is activated in case of more than 8 concurrent operations, Doest it mean that any query at that time will be missed or would not work ? Please help me out so that i could configure my applications accordingly. Any useful suggestion for handling this problem for the sake of testing would be highly appreciated.
Best Regards,
Viewing 15 posts - 1 through 15 (of 15 total)
You must be logged in to reply to this topic. Login to reply