1) I have a dual processor development db server with SQL Server 2000 Developer Edition installed. It seems SQL Server does not utilize both processors. Is it possible for the developer version to utilize more than one CPU?

2) Is the Developer Edition of SQL Server 2000 equivalent to the Enterprise Edition or the Standard Edition? What is the main difference between the Standard Edition and the Enterprise Edition (other than price!)?

By default, SQL Server 7.0 and 2000 are set to use "Use All Available CPUs" on a server. If this is not your current setting, then this has been changed by someone.

Essentially, this setting tells SQL Server whether or not to try and attempt to execute queries in parallel using multiple processors. If the default "Use All Available CPUs" option is selected, then SQL Server will attempt to run queries in parallel, using multiple CPUs. This can sometimes result in dramatic performance differences in a query's performance. But if this option is turned off, then SQL Server will only use one CPU to execute a query, which can be much slower.

Keep in mind that if SQL Server is set to use parallelism, that it may not always use it. If the server is very busy, it may not be used, but when the server is less busy, it may be used. This means that sometimes the view will be fast, and other times, slow (depending if parallelism is being used or not).

Also, be sure that you have the latest Service Pack on your SQL Server

Helen--------------------------------Are you a born again. He is Jehova Jirah unto me

I have sql 7 dev. edition and also have never seen both processors used...All settings have both processors turned on.If anybody has the answer I would shure appreciate it..Have wanted an answer to this question for a long time..I see nothing from Microsoft about this limitation..

As Helen mentioned, just because you have two CPU doesn't mean that they will be used by SQL Server every time. If the DB engine determines that it can accomplish the task using one CPU, then there's no need for it to split the task across the two CPUs.

One thing you might try is to run a union query on one of the larger tables in the database. Generally the query optimiser will split the union into to seperate queries that run on each CPU.

Hope this helpsPhill Carter--------------------Colt 45 - the original point and click interface