Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

SQL Server Developer vs Enterprise vs Standard Editions Expand / Collapse
Author
Message
Posted Tuesday, February 22, 2005 3:28 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, May 2, 2005 10:54 AM
Points: 5, Visits: 1

All,

I have a couple of questions about SQL Server 2000 editions.

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!)?

Any help on these questions would be greatly appreciated.

Thanks,
Jason

Post #163344
Posted Tuesday, February 22, 2005 5:05 PM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Wednesday, September 3, 2014 4:59 PM
Points: 2,693, Visits: 1,204

SQL Server Developer Edition is equivalent to Enterprise Edition.

For details on the different editions take a look at this document from the resource kit,
http://www.microsoft.com/sql/techinfo/planning/SQLReskChooseEd.asp

 



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

Australian SQL Server User Groups - My profile
Phills Philosophies
Murrumbeena Cricket Club
Post #163362
Posted Tuesday, February 22, 2005 7:35 PM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Monday, April 29, 2013 11:00 PM
Points: 210, Visits: 29

Hai,

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
Post #163376
Posted Wednesday, February 23, 2005 12:56 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Tuesday, August 5, 2014 9:26 AM
Points: 10, Visits: 220
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..
Post #163406
Posted Wednesday, February 23, 2005 3:46 PM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Wednesday, September 3, 2014 4:59 PM
Points: 2,693, Visits: 1,204

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 helps
Phill Carter
--------------------
Colt 45 - the original point and click interface

Australian SQL Server User Groups - My profile
Phills Philosophies
Murrumbeena Cricket Club
Post #163615
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse